Entity Creation For Constrained Devices

• US 20150358430A1
• Filed: 12/27/2013
• Published: 12/10/2015
• Est. Priority Date: 12/28/2012
• Status: Active Grant

• Current Assignee: IMEC International, Koninklijke KPN NV, Universiteit Gent Vzw, Universiteit Van Gent
• Original Assignee: iMinds, Koninklijke KPN NV, University of Kent
• Inventors: Ishaq, Isam, Hoebeke, Jeroen
• Granted Patent: US 9,866,651 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/303 Terminal profiles

Abstract

A method for creating a profile for accessing or manipulating resources across a plurality of nodes in a network is disclosed. An entity manager receives a request from a client to create a profile, and preferably validates the request. The entity manager generates said profile and the profile is addressable by a profile identifier. A client may use the profile to interact with the resources across the plurality of nodes using the profile identifier.

Claims

1. A method for creating a profile for accessing resources across a plurality of nodes in a network, each node associated with a node identifier, at least one resource, and/or at least one capability, the method comprising:

receiving, from a client at an entity manager, at least one first request to create the profile, said at least one first request comprising the node identifiers;

generating the profile, said profile comprising a list of node identifiers associated with the plurality of nodes, wherein the profile is addressable by a profile identifier.

2. The method according to claim 1, further comprising:

verifying, by the entity manager, that the node identifiers in the at least one first request correspond to existing nodes in the network.

3. The method according to claim 1, further comprising:

determining a first set of at least one resource associated with a first one of the plurality of nodes;

determining a second set of at least one resource associated with a second one of the plurality of nodes;

determining at least one common resource present in the first set and the second set;

associating the profile with the at least one common resource.

4. The method according to claim 1, further comprising:

determining a third set of at least one capability associated with a first one of the plurality of nodes;

determining a fourth set of at least one capability associated with the second one of the plurality of nodes;

determining at least one common capability present in and/or at least partly supported by both the third set and the fourth set;

associating the profile with the at least one common capability.

5. The method according to claim 1, wherein the at least one first request (1) further comprises an operation or (2) is associated with an operation by default at the entity manager, said method further comprising:

verifying that the nodes are able to support the operation based on the at least one resource and/or the at least one capability associated with the plurality of nodes;

if the nodes are able to support the operation, associating the profile with the operation.

6. The method according to claim 1, wherein:

the at least one first request further comprises at least one resource associated with each of the node identifiers in the at least one first request;

the at least one resource associated with each of the node identifiers is the same, or alternatively, different for each of the node identifiers;

optionally, the method further comprising verifying that the at least one resource associated with each of the node identifiers exist on the nodes identified by the node identifiers.

7. The method according to claim 5, further comprising:

determining at least one corresponding request for performing at least a part of the operation;

optionally, translating the operation into the at least one corresponding request based on a rules database associating operations with corresponding requests for performing the associated operations;

optionally, verifying that the plurality of nodes support the at least one corresponding request based on the at least one resource and/or the at least one capability associated with the plurality of nodes.

8. The method according to claim 7, further comprising:

receiving, at the entity manager, a second request comprising the profile identifier from the client and optionally an instruction for the entity to perform the operation;

transmitting the at least one of the corresponding request associated with the operation to at least some of the nodes;

receiving at least one response to the at least one corresponding request from the at least some of the nodes;

deriving a second response in accordance with the operation by processing the at least one response from the at least some of the nodes;

transmitting the second response to the client.

9. The method according to claim 8, wherein transmitting at least one corresponding request comprises transmitting at least one corresponding request to only a subset of the nodes to perform at least part of the requested operation.

10. The method according to claim 1, wherein the at least one first request to create the profile, said at least one first request (1) comprises an operation or (2) is associated with an operation by default, and said operation associated with at least one corresponding request, and said at least one first request further comprises at least one of the following parameters for parameterizing the operation:

a first parameter for indicating whether the at least one corresponding request is confirmable or non-confirmable;

a second parameter for indicating a number or all of the nodes to which the at least one corresponding request is transmitted;

a third parameter for indicating a minimum number or all of the nodes from which a response to the at least one corresponding request must be received before responding to a request to perform the operation.

11. The method according to claim 8, wherein deriving the second response comprises at least one of:

compiling all of the at least one response to a list and the second response comprises said list;

determining a minimum value from the at least one response and the second response comprises said minimum value;

determining a maximum value from the at least one response and the second response comprises said maximum value;

determining an average value from the at least one response and the second response comprises said average value; and

determining a sum of values from the at least one response and the second response comprises said sum of values.

12. The method according to claim 1, further comprising:

receiving a third request at the entity manager, said third request comprising the profile identifier and a change to the profile;

updating the profile at the entity manager based on the change to the profile.

13. The method according to claim 1,

(1) wherein the at least one first request further comprises the profile identifier to be attributed to the profile and the method further comprises associating the profile identifier with the profile;

or

(2) the method further comprises generating the profile identifier, associating the profile identifier with the profile, and transmitting the profile identifier to the client.

14. The method according to claim 1, wherein at least one of the plurality of nodes comprises a constrained device, and optionally, at least one of the plurality of nodes is communicably connected to the entity manager over a low power and lossy network.

15. The method according to claim 1, further comprising, transmitting a first response from the entity manager to the client, said response indicating that the profile has been created at the entity manager.

16. An entity manager for creating a profile for a group of nodes in a network, each node associated with a node identifier, at least one resource, and/or at least one capability, the entity manager comprising:

a receiver for receiving, at an entity manager, a at least one first request to create the profile from a client, said at least one first request comprising the node identifiers;

a profile manager for generating the profile, said profile comprising the list of node identifiers, wherein the profile is addressable by a profile identifier;

a transmitter for optionally transmitting a first response from the entity manager to the client, said response indicating that the profile has been created at the entity manager;

wherein the entity manager preferably is configured to implement the method of claim 2.

17. A system comprising a plurality of nodes in a network and the entity manager of claim 16 for creating a profile for accessing resources across the plurality of nodes, said entity manager communicably connected to the plurality of nodes.

18. A computer program product, implemented on computer-readable non-transitory storage medium, the computer program product configured for, when run on a computer, executing the method steps according to claim 1.