Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Shyam Krishnamoorthy

Calvin Yue-Ren Kuo

James Christopher Sorenson

Jonathan I Turow

Alan Conrad Rawcliffe

Marco Argenti

William Alexander Stevenson

Mark Edward Rafn

Rajaprabhu Thiruchi Loganathan

Nishanth Shankaran

Clint Joseph Sbisa

Rajat Arya

Dong Shou

Richard David Young

Jerry Paul Hook

Samuel John Young

Kyle Michael Roche

Rameez Loladia

Christoph Saalfeld

Alexandra Elizabeth Baoboe Lee

Tristam Kyle MacDonald

Nihal Chand Jain

Bryant Cutler

Jerry Alan Johnson

Lorenzo Tessiore

Gary Keith Wicker

Justin Robert Knoepfler

Frank Lovecchio

Qing Ju

Ling Tony Chen

Bradley Jeffery Behm

Paul Stephen Hellyar

J Clinton Paul Fowler

James Nicholas Helm

Lomash Kumar

Daniel M C Caiafa

Dan E Walther

Aditya Bhalla

Simon P Attwell

Robert P Cochran

Daniel E Walther

Daniel S Holt

Dan Griffin

Michael Roberts Courage

Ming Yue

Lucio Di Jasio

Joseph Harry Julicher

Jacobus Albertus Van Eeden

Richard Barry

James Christopher Iii Sorenson

A method and system for establishing two-way trust between a short-range communication device and a hub device. The method includes: obtaining, from a hub device, a digitally signed request for determining whether the hub device is a trusted communication device for a short-range communication device and a cryptographic key generated by the short-range communication device; generating a response to the request; encrypting the response to the request by using the cryptographic key provided by the short-range communication device, so that the encrypted response can be decrypted only by the short-range communication device; and providing the encrypted response to the hub device. The short-range communication device may decrypt the response and determine whether the hub device is the trusted communication device based on information indicated in the response.

Dynamic establishment of trust between locally connected devices

A connection management device may be used to with a common API to allow a host device of a client to securely connect to a remote provider network. The host device may only be able to use a connection management device by using a defined set of commands of a common API. A hardware root of trust may be pre-provisioned with security data (e.g., client certificate, encryption keys). A connection command may be used that is not specific to any particular communication protocol (e.g., WiFi, cellular, wired protocol). In response to receiving the connection command from a host device, the connection management device may perform commands specific to the communication protocol of the connection management device to connect to a remote provider network, use the security data for authentication, and establish a connection in accordance with the communication protocol based on the authentication.

Connection management device and common API

A technology is provided for delivering a data object to a device. Data delivery instructions to distribute a data object to a device may be received at a delivery service and indicate a storage location of the data object, a messaging topic, and a size of data receivable by the device. The data object is then divided into blocks corresponding to the size of data receivable by the device. A messaging topic is identified to which the device is subscribed via a messaging service. The blocks are sent to the device using the messaging topic and a network protocol available to the device.

Receiving a data object at a device

A computing environment is disclosed that receives from devices requests directed toward services accessible in the environment, and that forwards communications from services in the environment to devices registered with the environment. During a registration process at the environment, devices are assigned a device identifier that is used to identify and authenticate each particular device and requests communicated from and to the device via the environment. The computing environment maintains state information for each device that has been registered with the system. As the device interacts with the system, the state information is updated to reflect the changes in the device. When requests to perform functions are received from devices, the computing environment determines for the particular device and the particular function requested what processing needs to be performed by the environment in response to the request.

Device state management

A technology is described for a device shadowing service that manages device states. An example method may include receiving a state change message associated with a device that a subcomponent of the device has assumed a first state. In response to the state change message, a subcomponent representation associated with a device representation may be updated to indicate the first state received, where the device representation represents the device and the subcomponent representation represent the subcomponent of the device. Thereafter, a request may be received for the first state of the subcomponent of the device. The first state indicated by the subcomponent representation associated with the device representation may be determined, and the first state may be returned in response to the request.

Device subcomponent representations

Technology for publish-subscribe message updates is provided. In one example, a publish-subscribe messaging method may include receiving a message from a publisher. The message may include a tuple defining message data and a source identifier identifying a data source to update the message. The publication may be queued in a queue for publication to a subscriber. Updated message data may be retrieved from the data source identified in the tuple when the message reaches an update point of the queue. The updated message data may be inserted in the message to generate an updated message which may be published to the subscriber.

Publish-subscribe message updates

At a computing device, contents of one or more transaction records are obtained from a record-keeping network at which a decentralized consensus-based protocol is used to store transaction records of administrator changes of various devices. Using the contents of the obtained records, an administrator of the computing device is identified, as well as a network endpoint of the administrator. A set of instructions is obtained from the endpoint and executed.

Decentralized techniques for managing device administration rights

A technology is described for managing dynamic groups of devices using device representations. An example method may include receiving a request for a dynamic group of device representations. In response to the request, a membership parameter used to identify member device representations included in the dynamic group of device representations may be obtained. Device representations may be queried using the membership parameter to identify member device representations that have a state that corresponds to the membership parameter, and the dynamic group of device representations may be generated to include identifiers for the member device representations.

Dynamic grouping of device representations

A technology is described for operating a device shadowing service that calculates an aggregated group state for a group of device representations. An example method may include receiving device states for devices represented using a group of device representations, where the devices connect over a network to a device shadowing service configured to manage the device states. In response to an event, device representations included in the group of device representations may be identified. Device states indicated by the device representations may be obtained and an aggregated group state for the group of device representations may be calculated using the device states indicated by the device representations.

Aggregated group state for a group of device representations

Device communication environment

A technology is provided for delivering a data object to device. Data delivery instructions to distribute a data object to a device may be received at a delivery service and include a storage location of the data object, a messaging topic, and a size of data receivable by the device. The data object is then divided into blocks corresponding to the size of data receivable by the device. A messaging topic is identified to which the device is subscribed via a messaging service. The blocks are sent to the device using the messaging topic and a network protocol installed on the device.

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

Growing community of inventors

Redmond, WA, United States of America

Shyam Krishnamoorthy