Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-5324

FIWARE.Request.Tech.IoT.IDAS.OMA LWM2M IoT Agent questions

        Details

        • Type: extRequest
        • Status: Closed
        • Priority: Major
        • Resolution: Done
        • Fix Version/s: 2021
        • Component/s: FIWARE-TECH-HELP
        • Labels:
          None

          Description

          Greetings,

          Hello, and let me first introduce myself.
          I'm Danijel Hodzic that has recently become FIWARE Lab user.
          My startup team is called Smaczygote and we are invited to present our
          proposal and demo application at ICT 2015 from 20 to 22nd October, as part
          of the FRACTALS Smart Urban Farming Challenge.

          As we have little experience with FIWARE platform usage at the moment, we
          would like to get some advise and guidelines for decisions that we have to
          make, because we have no much more time.

          The Problem:
          We want to connect some cc2538 contiki motes with Fiware. Up to now we have:

          • instantiate VM based on orion-psb-image-R4.2 in our project, and
            Orion Context Broker is up and running
          • run our CoAP example on devices and tested visibility of our resources
            with Firefox Copper CU user-agent.

          Now we are interested in simplest way for creating of IoT Agent and
          configuration of it northbound and southbound interfaces.
          As we understood there is already OMA Lightweighted M2M IoT agent, and it
          is functioning as LWM2M Server and it can be easily configured to
          communicate with context broker.

          Q1: Is it good idea to deploy* lightweightedm2m-iotagent* from github to
          the same VM where orion cb is resided ?
          Q2: Is there example or concrete exercise where we can see how to
          assembly *lightweightedm2m-iotagent *and *orion cb *connection ?
          Q3: Regarding southbound interface, we have to implement LWM2M Client on
          top of CoAP. Is it true that, in order to enable this LWM2M client-server
          communication we have firstly to provide ipv6/ipv4 tunneling for our
          boarder-router connected to laptop to be able to communicate with our
          orion/iotagent VM with IPv4 public address ?
          Q4: Is there any exercises link about CoAP/OMA LWM2M configuration and
          southbound API usage examples ?

          Thank you,
          Best regards,
          M.S.E.E. Danijel Hodzic

          Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
          Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-lab-help mailing list
          Fiware-lab-help@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-lab-help
          [Created via e-mail received from: Danijel Hodzic <danijel.hodzic@smaczygote.com>]

            Issue Links

            relates to

            extRequest - Request from external stakeholder received in the help desk HELC-1136 FIWARE.Request.Coach.FRACTALS.OMA.LWM2M.IoT.Agent.questions

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              ichulani ilknur chulani added a comment -

              Hi Carlos,

              Could you help with these IoT Questions please? thanks..

              ilknur

              Show
              ichulani ilknur chulani added a comment - Hi Carlos, Could you help with these IoT Questions please? thanks.. ilknur
              Hide
              Permalink
              ralli Carlos Ralli Ucendo added a comment -

              Hi Danijel,

              Q1. It is a good idea. We work with this configuration for our public instance described at:
              http://catalogue.fiware.org/enablers/backend-device-management-idas/instances

              Q2.
              https://github.com/telefonicaid/lightweightm2m-iotagent/blob/master/docs/deviceProvisioning.md

              Q3. Hi, this really depends on your device network architecture. There are several possibilities.
              For instance, if you are using our sever in FIWARE Lab cloud there are IPv4 and IPv6 endpoints (130.206.80.48, 2001:720:1514:80::48).

              If your device network is IPv6-only (e.g. 6lowpan) then the easiest is to configure an IPv6 tunnel from your boder router to the IPv6-Internet (e.g. https://tunnelbroker.net/). Then your border-router will reach (and be reachable from) our lwm2m server.

              If you have a local lwm2m server then it is up to you to choose v4 or v6 communication but it should be the same in the lwm2m server and lwm2m clients (unless you configure a NAT64 in the border-router).

              Q4. All the examples that we have today are at Q2 link. We are thinking to work on the specific client-server interaction (with TShark snapshots for instance) but we it is still not in our roadmap.

              It would be great if you can contribute to the FIWARE-IoT Ready program (Open Hardware section) if you manage to develop Contikli libraries to connect to our LWM2M IoT Agent.
              Link: https://www.fiware.org/iot-ready-open-hardware/
              If you get there, send us your contrib request at:
              fiware-iot-ready@lists.fiware.org

              Show
              ralli Carlos Ralli Ucendo added a comment - Hi Danijel, Q1. It is a good idea. We work with this configuration for our public instance described at: http://catalogue.fiware.org/enablers/backend-device-management-idas/instances Q2. https://github.com/telefonicaid/lightweightm2m-iotagent/blob/master/docs/deviceProvisioning.md Q3. Hi, this really depends on your device network architecture. There are several possibilities. For instance, if you are using our sever in FIWARE Lab cloud there are IPv4 and IPv6 endpoints (130.206.80.48, 2001:720:1514:80::48). If your device network is IPv6-only (e.g. 6lowpan) then the easiest is to configure an IPv6 tunnel from your boder router to the IPv6-Internet (e.g. https://tunnelbroker.net/ ). Then your border-router will reach (and be reachable from) our lwm2m server. If you have a local lwm2m server then it is up to you to choose v4 or v6 communication but it should be the same in the lwm2m server and lwm2m clients (unless you configure a NAT64 in the border-router). Q4. All the examples that we have today are at Q2 link. We are thinking to work on the specific client-server interaction (with TShark snapshots for instance) but we it is still not in our roadmap. It would be great if you can contribute to the FIWARE-IoT Ready program (Open Hardware section) if you manage to develop Contikli libraries to connect to our LWM2M IoT Agent. Link: https://www.fiware.org/iot-ready-open-hardware/ If you get there, send us your contrib request at: fiware-iot-ready@lists.fiware.org

                People

                • Assignee:
                  ralli Carlos Ralli Ucendo
                  Reporter:
                  fw.ext.user FW External User
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: