editor's blog
Subscribe Now

IoT Standards: a oneM2M Follow-UP

A couple months ago I did a survey of Internet of Things (IoT) standards – or, more accurately, activities moving in the direction of standards, since it’s kind of early days yet.

And in it, I was a bit harsh with one standard… oneM2M. I found it dense and somewhat hard to penetrate, with language that didn’t seem clear or well-explained. The status at the time – and currently (for a bit longer) was as a candidate release, taking input.

To their credit, they accepted my cantankerous grumblings as input. I had a conversation with their Work Programme Management Ad-Hoc Group Chairman Nicolas Damour, at his suggestion, and we talked about some of the specific questions I had raised in my coverage. The general take-away was that the language could be made a bit more expansive for readers not from narrow domains.

Doing this can actually be tricky, since standards tend to have two kinds of content:

  • “Normative” content: this is the standard itself, the rules. It says what you “must” and “will” and ‘”shall” and “may” do. Changes to this must be well thought out and voted on. You can’t make changes willy-nilly.
  • “Informative” content: this is background material intended to give context or examples or perhaps even discuss the thinking that went into the standard: why was one approach approved over another? It’s much easier to make changes here. And if there’s any confusion between what the informative and normative sections say? The normative language always trumps.

A glossary is one good example of informative content, and we agreed that it was a reasonable place to make some clarifications. There might even be room for some glosses concerning how some tough decisions were arrived at. Overall, it was a productive conversation – showing a flexibility that’s not always a hallmark of standards organizations. (After several years of hard-fought work, it’s understandable that a group might resist a bit when outsiders propose last-minute changes… I didn’t perceive this during our talk.)

There were two specific things that I raised in my coverage.

  • One was the missing definition of a “reference point.” It turns out that, for people in the telecom world, this is a familiar term, codified by the ITU. It’s what the rest of us might call an “interface.” Problem is, the word “interface” means a lot of different things, so in ITU-land, it refers to an API or a specific physical interface. A reference point indicates an interface between systems, but in a more generic way, and one that could admit multiple protocols. Perhaps “boundary” is a better word than “interface.”
  • I questioned the definitions of “field” vs. “infrastructure” domains. In retrospect, this seems clearer: the field refers to deployed devices, and infrastructure means the Cloud or servers. The reason this seems clear now is because I’ve been specifically thinking about that with respect to “IoT Ring Theory.” Before that, it wasn’t so clear. To me, anyway.

They’re taking input through the end of the year, so you still have time to review and make suggestions. You can find the latest candidate release here (via FTP).

 

Note: there’s a page on the website with an earlier release that says that comments had to be in by Nov. 1, not by the end of the year… but I checked in, and that was for an earlier round of comments. You can still provide input. There’s also an explanatory webcast here.  

Leave a Reply

featured blogs
Oct 28, 2021
Spectre 21.1 ISR2 and Virtuoso IC6.1.8 ISR21 introduce the new Voltus TM -XFi Custom Power Integrity Solution, a new transistor-level electromigration and IR drop (EMIR) solution that provides a... [[ Click on the title to access the full blog on the Cadence Community site. ...
Oct 27, 2021
ASIC hardware verification is a complex process; explore key challenges and bug hunting, debug, and SoC verification solutions to satisfy sign-off requirements. The post The Quest for Bugs: The Key Challenges appeared first on From Silicon To Software....
Oct 20, 2021
I've seen a lot of things in my time, but I don't think I was ready to see a robot that can walk, fly, ride a skateboard, and balance on a slackline....
Oct 4, 2021
The latest version of Intel® Quartus® Prime software version 21.3 has been released. It introduces many new intuitive features and improvements that make it easier to design with Intel® FPGAs, including the new Intel® Agilex'„¢ FPGAs. These new features and improvements...

featured video

Maxim Integrated is now part of Analog Devices

Sponsored by Maxim Integrated (now part of Analog Devices)

What if the march of progress suddenly broke into a full-in sprint?

See What If: analog.com/Maxim

featured paper

The ABCs of Glitch-Free Voltage Supervisors

Sponsored by Maxim Integrated (now part of Analog Devices)

Reset glitches can trigger a false signal to the processor or critical load during power-up. This application note discusses the various aspects and benefits of a glitch-free supervisor.

Click to read more

featured chalk talk

Flexible Power for a Smart World

Sponsored by Mouser Electronics and CUI Inc.

Safety, EMC compliance, your project schedule, and your BOM cost are all important factors when you are considering what power supply you will need for your next design. You also need to think about form factor, which capacitor will work best, and more. But if you’re not a power supply expert, this can get overwhelming in a hurry. In this episode of Chalk Talk, Amelia Dalton chats with Ron Stull from CUI Inc. about CUI PBO Single Output Board Mount AC-DC Power Supplies, what this ??ac/dc core brings to the table in terms of form factor, reliability and performance, and why this kind of solution may give you the flexibility you need to optimize your next design.

Click here for more information about CUI Inc PBO Single Output Board Mount AC-DC Power Supplies