Earlier this week I was able to visit ILS Technology for a discussion on where the market may be heading. Earlier, I met with a large enterprise R&D subject matter expert and then had a phone call with a test lab CEO.
With each of these discussions, standards played the biggest role, and it was interesting to hear all of the perspectives.
Let me tell you what the concerns are and then we can talk about rationale behind the perspectives.
The First concern expressed is the output of the product. OneM2M has generated a lot of awareness, but at the end of the day, what are their goals? As a carrier-driven body and the home of IMS, it’s likely that they are looking to deal with the sticky common issues first for carriers - which means network management or as it’s referred to in the industry “FCAPS” (which are the initials for Fault, Configuration, Accounting, Provisioning and Security). My personal view is that Accounting and Provisioning are going to dominate a lot of the work initially. Which makes it easier for device deployment, but does not necessarily give guidance to the various vertical markets.
In contrast, TR-50 has been focused on giving a standard that makes it easier for the device and sensor companies to know how to interface to the service layer. Fred Yentz, ILS Technologies President and his team were very pleased with the spec and the fact that they were near compliant already with their systems.
Now that TR-50 is connected to the OneM2M folks, it will be interesting to see if the standard gets adopted universally or gets submarined in committees.
Which brings me to the last discussion of the day I had with the test lab company. For them, every standard they test is about a $100,000 implementation, so they want to know that the standards they are implementing are going to be the dominating standards.
Is it time to hop on board with TR-50? I am hoping the answer is yes, but waiting a few weeks for the next oneM2M meeting is probably a good move.
Edited by Stefania Viscusi