Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #28450

Re: "Device-to-smartphone" and "smartphone-to-device" technologies

Show all headers | View raw

Il 12/12/2018 07:34, Mikko OH2HVJ ha scritto:
> pozz <pozzugno@gmail.com> writes:
> 
>> As a developer, I can think to rent a physical server (the
>> infrastructer) from service providers and: install an OS (maybe a
>> Linux variant), install a HTTP server (for smartphone requests), write
>> and run server-side scripts to process smartphone requests, install a
>> custom software that communicated with the embedded devices.
>> Wait wait, but I don't have the skills to create and maintain a
>> serious, reliable and secure server that is reachable in
>> Internet. Does it mean we need another guy in our team?
> 
> Yes, this is an experise area that in production quality requires
> specific skills. My field is building this kind of systems from sensor
> hardware to cloud and applications. I've done all of the parts to some
> level to understand the basic challenges, but I don't even dream of
> building a production quality system by myself.
> 
> I've worked with few developers that have been able to grasp embedded
> and serverside, but this is quite rare and few.
> 
> Doing IoT securely is then an another matter - I've had the luck of
> working with the best in this field and picked up enough from them to
> know what are the main limitations and how difficult this is to do well.
> 
> As a minimum team for doing something you're describing, I'd pick a few
> talented persons with skills in:
> -Electronics/FW to get the HW done
> -Design/mechanical, especially if it has to look nicer than typical
> industrial stuff
> -Cloud/server/mobile developer.
> 
> With these you could start, but to do something bigger you need to go
> deeper in each part. As an example, mobile developers come mostly in two
> flavours: iOS and Android. And then there's the possible web
> interface. And I've only ever seen one single developer being able to
> work well on web UI and protocol between device and cloud.
> 
> So yes, you'll need an another person.
> 
>> Another possibility is to rent (and pay for) a cloud service that let
>> the smartphone to "chat" with the device. MQTT broker? PubNub? Amazon
>> Web Services (AWS)? I don't know.
> 
> Check out the Google Cloud, Amazon AWS and Microsoft Azure IoT
> architectures to get an idea. There's a lot of buzzword compliance (AI,
> ML, IoT..), but by checking those three you can get the basic idea on
> how it's usually done. There are a lot of product/application specific
> stuff you'll need in addition, but you can start with any of those.
> 
>> I also read about serverless solutions where you wrote the program and
>> "launch it in Internet", without knowing the server where it really
>> runs (you usually pay for processing time). In this case I needn't to
>> have good skills to create and maintain a real server.
> 
> Serverless is really nice approach for cloud, but finding true
> experience in that field is difficult.
> 
> If I were to create a small scale mobile-controlled IoT device, I would pick
> -Linux SOM or ESP32 (if you've got mains power - battery is more difficult!)

Do you think a simple Cortex-M3 running FreeRTOS/superloop with lwip 
TCP/IP stack is not sufficient? This hw actually runs a HTTP server 
without big issues.

> -Some of the commercial cloud stacks 

Any real suggestions? I tried to read Amazon Web Services and Google 
Cloud Platform, but sincerely I lost the way.

> or my own MQTTS/AMQPS server with my own server.

Do you mean a MQTT broker? So you imagine that the app on the smartphone 
is a MQTT client, as the device?

> -Firmware updates from the server (PKI signed with offline keys!)

Yes.

> -Web UI with some node.js based stack

Web UI running in the app of the smartphone?

> -Mobile app to connect through the cloud - there are tools that allow
>   reusing web development - not the best ones, but possible.

Yes. The mobile app should connect to the cloud through MQTT or similar 
protocols, right?

> -Pay at least some thought on how your system will be attacked and how
>   to mitigate
> 
> Some thoughts - now need to get back to work..

Thank you very much for your post. Those are precious info.

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

"Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-09 23:49 +0100
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-10 12:04 +0200
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 11:33 +0100
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-10 14:09 +0200
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 14:51 +0100
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-10 22:50 +0200
            Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-11 14:27 +0100
              Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-11 16:50 +0200
                Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-11 23:34 +0100
                Re: "Device-to-smartphone" and "smartphone-to-device" technologies Dimiter_Popoff <dp@tgi-sci.com> - 2018-12-12 02:26 +0200
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Theo <theom+news@chiark.greenend.org.uk> - 2018-12-10 14:34 +0000
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 23:05 +0100
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Theo <theom+news@chiark.greenend.org.uk> - 2018-12-11 11:58 +0000
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-11 14:36 +0100
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies lasselangwadtchristensen@gmail.com - 2018-12-10 13:17 -0800
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-10 23:05 +0100
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Robert Wessel <robertwessel2@yahoo.com> - 2018-12-10 20:18 -0600
  Re: "Device-to-smartphone" and "smartphone-to-device" technologies Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2018-12-12 08:34 +0200
    Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-13 13:51 +0100
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Rob Gaddi <rgaddi@highlandtechnology.invalid> - 2018-12-13 10:09 -0800
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-13 18:59 +0000
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Rob Gaddi <rgaddi@highlandtechnology.invalid> - 2018-12-13 11:17 -0800
            [OT] Gopher Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2018-12-13 21:00 +0100
            Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-13 20:37 +0000
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Clifford Heath <no.spam@please.net> - 2018-12-14 08:12 +1100
            Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-13 21:46 +0000
        Re: "Device-to-smartphone" and "smartphone-to-device" technologies pozz <pozzugno@gmail.com> - 2018-12-14 09:17 +0100
          Re: "Device-to-smartphone" and "smartphone-to-device" technologies Grant Edwards <invalid@invalid.invalid> - 2018-12-14 15:18 +0000
      Re: "Device-to-smartphone" and "smartphone-to-device" technologies Mikko OH2HVJ <mikko.syrjalahti@nospam.fi> - 2018-12-15 18:20 +0200

csiph-web