Search

Help

Page 1 of 5. Showing 46 results (0.005 seconds)

  1. IoT Agents

    Summary The IoT agents where developed for all kind of storeless data processing, from simple data annotation or aggregation to complex data machine learning techniques. The agents fulfill the task of a LinkSmart® Processor and a bit of a Message Handler (see LinkSmart® Specification), and they are ideal
    LinkSmart® IoT AgentsNov 15, 2017
  2. Component Diagram

    The relationship between components of Historical Datastore (HDS) is illustrated in the diagram below: image201777162223.png Core The core component … Client, and to register the service in one or more Service Catalog. This component also takes care of the graceful shutdown of all components and service
  3. IoT Agent Architecture (under construction)

    asynchronous messages to which the IoT Learning Agent (LA) or LAs are subscribed. On the other hand, the Models subscribe to the data, provided by the clients … are established using Paho clients. While the logical connections between the components and the Broker/s is managed by StaticBroker. This means, there are as many
    LinkSmart® IoT AgentsOct 26, 2017
  4. Component Diagrams

    Resource Catalog The relationship between the components of Resource Catalog, the Service Catalog, and an authentication server is illustrated in the diagram below: image2017101316311.png Service Catalog Diagram below shows components of the Service Catalog and their relationship with an authentication server
    LinkSmart® LocalConnectOct 13, 2017
  5. IoT Data-Processing Agent API (under revision)

    file (see ). File based API The file base API or BootstrappingFeeder was developed to allow having preloaded events and statements on the agent. For deploy … ! MQTT API The agent it always listening a topic for new statement (see ) in an incoming "control" broker, by default the is "statement/add" and "tcp://localhost
    LinkSmart® IoT AgentsOct 26, 2017
  6. IoT agents configuration

    The agents can be configured either via environmental variables or by a configuration file provided as an argument at starting time. Both configurations by file or by environmental variables use the same configuration settings. Configuration by file At the moment of starting the agent, the configuration file complete
    LinkSmart® IoT AgentsOct 26, 2017
  7. IoT Data Processing agent Deployment

    Configuration Note For more configuration settings please see: IoT agents configuration Docker Run Agent with existing broker Dependencies Docker MQTT Broker docker run e connectionbrokermqtthostname=mymqtthostname p 8319:8319 docker.linksmart.eu/agent:latest Run Agent without existing broker Dependencies Docker
    LinkSmart® IoT AgentsOct 26, 2017
  8. IoT Data-Processing Agent Results (under revision)

    using 1 core as base, while DFM used 2 cores as base. Interpretation The test was performed until one of the three sides reached its limit. In this test … over the load used in this experiment. Scalability perspective The test shows that the effects of a heavy load in the system affect different on other components
    LinkSmart® IoT AgentsOct 26, 2017
  9. IoT Agents Use Cases (under construction)

    the Agent execution environment. Operation Type Type of the request. Create Creates one statement and exist so lo the request finished or is deleted. Update … to be persisted. The stream is stored in some persistent system. Extern All request that produces any side effect outside the Agent execution environment. These use
    LinkSmart® IoT AgentsNov 20, 2017
  10. IoT Data-Processing agent Statement (under revision)

    The DP Statement payload This type of events encapsulate a DP statement used to deploy the query statement on agent. It contains 10 properties of which only 2 … on the API is being used. The ID is unique identifier in an agent. If the the ID is not provided, then is generated by hashing (SHA256) the Statement value, this means
    LinkSmart® IoT AgentsOct 26, 2017