Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: None
    • Labels:
      None

      Description

      Created question in FIWARE Q/A platform on 13-06-2019 at 20:06
      Please, ANSWER this question AT https://ask.fiware.org/question/1076/device-provisioning/

      Question:
      Device provisioning

      Description:
      Hi,

      I have newbie question, it is related to device provisioning. We have an IoT device that sends a message with information including provisioning information.
      Let say that this device is used to make a connected Wastebin.

      So I assume that the provisioning in this case includes both to map the protocol attributes (sent by device) to attributes in a Device Entity as well as to an Asset entity, in this case a Waste Container entity.

      I mean for example hardware version, Device ID, serial number, device location would be related to the Device entity. But other attributes such as filling level, temperature, wastekind etc would be mapped to the Waste Container entity. So my question may be very trivial, but how is that mapping done when we have a "connected" Asset that then inludes at least two entities (Waste Container and Device). I would assume that the device message is received and the device ID is used to find the Device entity and the Device entity in turn has some reference to an Asset entity. And then protocol attributes could be mapped to both the Device and to the Asset entity referred to by the Device. But I do not know.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        59m 58s 1 Backlog Manager 17/Jun/19 8:05 PM
        In Progress In Progress Answered Answered
        59m 59s 1 Backlog Manager 17/Jun/19 9:05 PM
        Answered Answered Closed Closed
        135d 12h 45m 1 Fernando Lopez 31/Oct/19 8:51 AM

          People

          • Assignee:
            jmcantera Jose Manuel Cantera
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: