US 9,792,165 B2Granted

Binding smart objects

AssigneesKoninklijke KPN N.V., Imec Vzw, Universiteit Gent

InventorsJeroen Hoebeke, Girum Teklemariam, Floris Van Den Abeele

Life of this patent

Estimating the term…

Loading patent…

Abstract

A method for binding a first and second devices is disclosed. The method is implemented using the architectural principles of REST, which allows a binding initiator to directly contact the first device and instruct the device of actions to be taken. Specifically, the binding initiator may contact the first device by providing a first REST request to the device, the request specifying that the first device is to monitor a state of a particular REST resource identified by the request and is to trigger the second device to perform a specified action when the state of that REST resource satisfies a particular condition. Using REST further allows the first device to directly contact the second device and instruct the second device to perform the specified action. Since the first device is now able to directly contact the second device, these two devices may be considered to be bound.

Claims12

Dependent claims

A method comprising:

receiving, at a sensor device, from a binding initiator, a first Representational State Transfer (REST) request for a first REST resource hosted by the sensor device, the first REST request comprising at least an identification of an action to be executed on an actuator device and an identification of a condition of a state of the first REST resource for executing the action on the actuator device;
storing, in a binding table of the sensor device, the identification of the action to be executed on the actuator device and the identification of the condition for executing the action on the actuator device as information related to the first REST resource;
monitoring, by the sensor device, the state of the first REST resource to determine whether the state satisfies the condition identified in the first REST request;
after determining that the state of the first REST resource satisfies the condition, providing, from the sensor device to the actuator device, a trigger for the actuator device to execute the action identified in the first REST request, wherein the trigger is provided in a form of a second REST request;
receiving, at the sensor device, from either the binding initiator or a further device, a third REST request comprising an indication that the sensor device should no longer provide the trigger to the actuator device to execute the action identified in the first REST request;
and
removing the identification of the action to be executed on the actuator device and the identification of the condition for executing the action on the actuator device from the binding table.

4 more elements

A sensor device comprising:

a receiver configured for receiving, from a binding initiator, a first Representational State Transfer (RESTS request for a first REST resource hosted by the sensor device, the first REST request comprising at least an identification of an action to be executed on an actuator device and an identification of a condition for executing the action on the actuator device;
and
a processor configured for:
storing, in a binding table of the sensor device, the identification of the action to be executed on the actuator device and the identification of the condition for executing the action on the actuator device as information related to the first REST resource,
monitoring a state of the first REST resource to determine whether the state satisfies the condition identified in the first REST request, and
after determining that the state of the first REST resource satisfies the condition, providing to the actuator device a trigger for the actuator device to execute the action identified in the first REST request, wherein the trigger is provided in a form of a second REST request;
the receiver further configured for receiving, from either the binding initiator or a further device, a third REST request comprising an indication that the sensor device should no longer provide the trigger to the actuator device to execute the action identified in the first REST request;
and
the processor further configured for removing the identification of the action to be executed on the actuator device and the identification of the condition for executing the action on the actuator device from the binding table.

6 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/107,428Filed 23 Dec 2014
Priority: EP 1319938823 Dec 2013
Published: US 2017/0017533 A119 Jan 2017
Granted: 17 Oct 2017
Term ends: Not estimatedThe source records don’t support an estimate.

Classification4 codes

G06F 9/547
Interprogram communication: remote procedure calls [RPC]; Web services
H04L 12/2809
Exchanging configuration information on appliance services in a home automation network: indicating that an appliance service is present in a home…
G06F
Computing and data processing
H04L
Digital communication