Sensor data handling for cloud-platform infrastructure layouts

• US 10,355,941 B2
• Filed: 05/15/2018
• Issued: 07/16/2019
• Est. Priority Date: 09/04/2014
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Tung, Teresa Sheausan, Gomadam, Karthik, Xie, Qing
• Primary Examiner(s): Ibrahim, Mohamed
• Application Number:
  US15/980,730
• Publication Number:
  US 20180270120A1
• Time in Patent Office: 427 Days
• Field of Search: None
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

A system maintains, generates, and manages infrastructure layouts. The infrastructure layouts include structural relationships for the handling of received sensor data. The infrastructure layouts may be traversed to determine datastore options for the sensor data and contextual information that may be used to enrich the received sensor data.

Claims

1. A product including:

machine readable media other than a transitory signal; and

instructions stored on the machine readable media, the instructions configured to, when executed, cause a machine to;

establish a communication link over a network;

obtain, via the communication link, sensor data from a sensor;

apply an extension to a knowledge layout, the extension including a subclass that includes a sensor type of the sensor, the extension defining;

a first path from a sensor node for the sensor to an analytics type node; and

a second path from the sensor node to a sensor data kind node;

access the sensor node for the sensor;

traverse the first path of the extension from the sensor node to the analytics type node to determine an analytics type instance for the sensor;

traverse the second path of the extension from the sensor node to the sensor data kind node to determine a sensor data kind instance for the sensor, the sensor data kind instance having a pre-defined associated property defining a preferred datastore class for the sensor data kind instance;

generate enriched sensor data by addition of metadata to the sensor data, the metadata indicating the analytics type instance and the sensor data kind instance for the sensor;

establish a datastore class consistent with the preferred datastore class by accessing the pre-defined associated property for the sensor data kind instance;

responsive to the datastore class, instantiate reserved storage for the enriched sensor data; and

store the enriched sensor data within the reserved storage.

2. The product of claim 1, where the knowledge layout is configured to define:

a received technical service provided by the sensor data; and

a dependency for a northbound technical service fulfilled by the received technical service.

3. The product of claim 2, where the instructions are further configured to cause the machine to:

traverse a third path to generate a workflow, the workflow including a deployment script to implement the received technical service; and

execute the deployment script by deploying a web resource to implement the received technical service to fulfill the northbound technical service within a deployed instance of the knowledge layout.

4. The product of claim 1, where the second path includes a sensor data node between the sensor node and the sensor data kind node.

5. The product of claim 4, where the second path is configured to define:

a first relationship between the sensor node and the sensor data node; and

a second relationship between the sensor data node and the sensor data kind node.

6. The product of claim 1, where:

the network includes an Internet-based network; and

the sensor includes an Internet-connected Internet of Things (loT) sensor.

7. The product of claim 1, where the reserved storage includes a Cassandra datastore, a Dynamo datastore, or both.

8. The product of claim 1, where the instructions are further configured to cause the machine to determine that the sensor data kind instance includes time series data.

9. The product of claim 1, where the instructions are further configured to cause the machine to apply the extension to the knowledge layout by determination of at least a portion of the first path through inheritance from a parent class of the subclass.

10. The product of claim 1, where the instructions are further configured to cause the machine to apply the extension to the knowledge layout by overwriting a selected instance of a parent class of the subclass with a specific instance of the subclass.

11. A method including:

establishing a communication link over a network;

obtaining, via the communication link, sensor data from a sensor;

applying an extension to a knowledge layout, the extension including a subclass that includes a sensor type of the sensor, the extension defining one or more paths extending from;

a sensor node for the sensor to an analytics type node; and

the sensor node to a sensor data kind node;

accessing the sensor node for the sensor;

traversing the one or more paths of the extension from the sensor node to the analytics type node to determine an analytics type instance for the sensor;

traversing the one or more paths of the extension from the sensor node to the sensor data kind node to determine a sensor data kind instance for the sensor, the sensor data kind instance having a pre-defined associated property defining a preferred datastore class for the sensor data kind instance;

generating enriched sensor data by adding metadata to the sensor data, the metadata indicating the analytics type instance and sensor data kind instance for the sensor;

establishing a datastore class consistent with the preferred datastore class by accessing the pre-defined associated property for the sensor data kind instance;

responsive to the datastore class, instantiating reserved storage for the enriched sensor data; and

storing the enriched sensor data within the reserved storage.

12. The method of claim 11, where:

the network includes an Internet-based network; and

the sensor includes an Internet-connected Internet of Things (loT) sensor.

13. The method of claim 11, where applying the extension to the knowledge layout includes determining at least a portion of the first path through inheritance from a parent class of the subclass.

14. The method of claim 11, where applying the extension to the knowledge layout includes overwriting a selected instance of a parent class of the subclass with a specific instance of the subclass.

15. The method of claim 11, where the knowledge layout is configured to define:

a received technical service provided by the sensor data; and

a dependency for a northbound technical service fulfilled by the received technical service.

16. The method of claim 15, further including:

traversing a third path to generate a workflow, the workflow including a deployment script to implement the received technical service; and

executing the deployment script by deploying a web resource to implement the received technical service to fulfill the northbound technical service within a deployed instance of the knowledge layout.

17. The method of claim 11, where traversing the one or more paths from the sensor node to the sensor data kind node includes traversing a sensor data node between the sensor node and the sensor data kind node.

18. A system including:

network interface circuitry configured to;

establish a communication link over a network; and

obtain, via the communication link, sensor data from a sensor; and

processing circuitry configured to;

apply an extension to a knowledge layout, the extension including a subclass that includes a sensor type of the sensor, the extension defining connections;

extending from a sensor node for the sensor to an analytics type node; and

extending from the the sensor node to a sensor data kind node;

access the sensor node for the sensor;

traverse the connections of the extension from the sensor node to the analytics type node to discover an analytics type instance for the sensor;

traverse the connections of the extension from the sensor node to the sensor data kind node to determine a sensor data kind instance for the sensor, the sensor data kind instance having a pre-defined associated property defining a preferred datastore class for the sensor data kind instance;

generate enriched sensor data by adding metadata to the sensor data, the metadata indicating the analytics type instance and sensor data kind instance for the sensor data;

establish a datastore class consistent with the preferred datastore class by accessing the pre-defined associated property for the sensor data kind instance;

responsive to the datastore class, instantiate reserved storage for the enriched sensor data; and

store the enriched sensor data within the reserved storage.

19. The system of claim 18, where the knowledge layout is configured to define:

a received technical service provided by the sensor data; and

a dependency for a northbound technical service fulfilled by the received technical service.

20. The system of claim 19, where processing circuitry is further configured to:

traverse a third path to generate a workflow, the workflow including a deployment script to implement the received technical service; and

execute the deployment script by deploying a web resource to implement the received technical service to fulfill the northbound technical service within a deployed instance of the knowledge layout.