MANAGING INTERACTION CONSTRAINTS
First Claim
1. A machine-implemented method for operating an electronic device to configure a subject device, the method comprising steps of:
- receiving an intent from a subject device, wherein the received intent comprises an action identifier identifying an action the subject device wishes to perform;
receiving action data about the received intent from an intent store, wherein the action data comprises an action associated with each action identifier, and at least one constraint associated with the action;
generating invocation data to perform the action, wherein the invocation data comprises the action, and zero or more parameters; and
passing the invocation data to an endpoint.
1 Assignment
0 Petitions
Accused Products
Abstract
A method for operating an electronic device to configure a subject device, the method comprising steps of: receiving an intent from a subject device, wherein the received intent comprises an action identifier identifying an action the subject device wishes to perform; receiving action data about the received intent from an intent store, wherein the action data comprises an action associated with each action identifier, and at least one constraint associated with the action; and generating invocation data to perform the action, wherein the invocation data comprises the action identifier, and zero or more parameters.
-
Citations
20 Claims
-
1. A machine-implemented method for operating an electronic device to configure a subject device, the method comprising steps of:
-
receiving an intent from a subject device, wherein the received intent comprises an action identifier identifying an action the subject device wishes to perform; receiving action data about the received intent from an intent store, wherein the action data comprises an action associated with each action identifier, and at least one constraint associated with the action; generating invocation data to perform the action, wherein the invocation data comprises the action, and zero or more parameters; and passing the invocation data to an endpoint. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
-
16. An electronic device for configuring a subject device, the electronic device comprising a communication module configured to:
-
receive an intent broadcast by a subject device, wherein the received intent comprises an action identifier identifying an action the subject device wishes to perform; receive action data about the received intent from an intent store, wherein the intent store comprises an action associated with each action identifier, and at least one constraint associated with each action; generate invocation data to perform the action, wherein the invocation data comprises the action, and zero or more parameters; and pass the invocation data to an endpoint.
-
-
17. An intent registry comprising:
-
a data store for storing a plurality of action data, wherein each of the action data comprises an action associated with a pre-registered action identifier, and at least one constraint associated with the action; and a communication module configured to; receive a request for action data, wherein the request specifies an action identifier; retrieve the action data for the specified action identifier from the data store; and pass the retrieved action data. - View Dependent Claims (18, 19, 20)
-
Specification