280 likes | 290 Views
Report from GSC M2M Standardization Task Force (MSTF). Dr. Jeffrey Smith CTO, Numerex. GSC MSTF 2011 Resolution (GSC16-Res30). To continue the GSC M2M Standardization Task Force (MSTF) to facilitate global coordination and harmonization
E N D
Report from GSC M2M Standardization Task Force (MSTF) Dr. Jeffrey Smith CTO, Numerex
GSC MSTF 2011 Resolution (GSC16-Res30) • To continue the GSC M2M Standardization Task Force (MSTF) to facilitate global coordination and harmonization • To openly share relevant M2M material through liaisons, meetings, etc. • To outline the worldwide M2M activity map and make recommendations on current and future activities • To encourage broad participation in the MSTF by GSC members and beyond • To invite MSTF to report to GSC -17 on its activities and recommendations • That Jeff Smith (jsmith@numerex.com) will be the chair of MSTF until GSC-17
May 7, 2013: GSC MSTF Meeting at the Georgia Tech Research Institute in Atlanta, Georgia, USA (http://www.tiaonline.org/standards/collaborative-activities/past-gsc-mstf-events) • Focus on Open Source and other Internet of Things and M2M technology initiatives • Represented (Presentations):ITU-T JCA-IoT, GSI, FG-M2M, oneM2M, Weightless SIG, Open Geospatial Consortium (OGC), Open Source Internet of Things, Eclipse, OASIS, Open WSN Project (UC Berkeley) • Represented (Attendance): Cisco, AT&T, Verizon, IBM, Georgia Institute of Technology, Numerex, Symantec, Georgia State University, Hitachi, ILS technology, Interdigital, MSys Technologies, ETRI, etc. Highlight of 2013 Activities
Key Points • Whatever Internet of Things (IOT) is, it is big • Massive global market for machine communications • M2M industry is fragmented – silos and verticals; need to address with a horizontal view in mind • Need improved wireless network that can provide good coverage, extended battery life and low cost modules • If overlapping standards, then need to explore how to harmonize those standards • Enable developers to adopt the technology by use of open development tools/open source • World has changed and traditional operators have to work and talk with the developers
Conclusions • Extensive work in M2M being undertaken in many SDOs and other forums and organizations including the Open Source Community • Scope of work very similar among many organizations – to develop specifications to address M2M from a horizontal perspective and to support the various vertical applications • Need strong relationship and cooperative liaisons among organizations to reduce duplication and avoid fragmentation of standards • Focus of MSTF is to facilitate cooperation and information exchange among traditional SDOs and beyond such as the Open Sources Community
Strategic Direction • Position GSC MSTF as a forum the purpose of which is to strengthen the work of international bodies focusing on IoT and M2M standards. • Become a global source of valuable information coming from an eclectic range of sources, both traditional and non-traditional players in the M2M standards arena (vertical market groups, Open Source, other technology groups, fora and associations). • Reconfirm the GSC MSTF as a neutral venue where ideas on M2M can be debated and exchanged outside a formal standardization process framework.
Challenges • Handle the big number of vertical market-related SDOs, associations and other groups addressing various technologies supporting M2M • Develop effective collaboration and harmonization between SDOs, governments, regulatory bodies, and various industry groups such as the Open Source Community • Eliminate fragmentation, overlap and duplication
Next Steps / Actions • Review GSC MSTF charter for rules and procedures regarding information sharing • Create and maintain list of GSC MSTF individual participants • Organize 2 GSC MSTF meetings before GSC-18
Proposed Resolution • Refresh the GSC MSTF charter and amend GSC16-Res30 resolution accordingly to be submitted to GSC during GSC17. Amended resolution may include: • Reinforce the GSC MSTF as a neutral platform for organizations working in IoT and M2M to come together to share information and explore ways for future harmonization of standards • Renewal of Jeff Smith as chair of GSC MSTF until GSC-18 • Identification of TIA as home base of GSC MSTF until GSC-18
MSTF Atlanta (*) Highlights (1) • Stefano Polidori, introduced ITU JCA-IoT, IoT-GSI and FG-M2M • Jun Seob Lee, ITU JCA-IoT and IoT-GSI • MSTF has participated in meetings • IoT standards roadmap and work plan • ITU-T Y.2060 (Overview of Internet of Things) • Reference Model/Ecosystem • Definition of IoT • Ongoing IoT work items: SG13 and SG16 - Common requirements, IoT functional framework, capabilities and functional architecture of gateway for IoT applications, requirements and capabilities of device management, others. (*) Meeting was held at the Georgia Tech Research Institute on May 7, 2013 in Atlanta, GA, USA. Presentations available at: http://www.tiaonline.org/standards/collaborative-activities/past-gsc-mstf-events
MSTF Atlanta Highlights (2) • Marco Carugi, ITU Focus Group on M2M Service Layer (FG-M2M) • Established in 2012, with key goal the study of requirements and specifications for a common M2M Service Layer • Initial focus: e-health • Remote patient monitoring and assisted living • Include vertical market stakeholders not part of traditional ITU- T membership; collaborating with e-health communities • Structure • Formed working groups for use cases and service models, requirements and architectural framework, and API and protocols • Cross working group activities– e-health standardization activities and gap analysis, e-health ecosystem • Capabilities of M2M service layer are a subset of the capabilities of IoT • 5 deliverables currently under work • e-health standardization activities and gap analysis; collection of specs per relevant SDO, gap analysis started in January 2013 and template liaised with other SDOs for input.
MSTF Atlanta Highlights (3) • Joachim Koss– oneM2M • Organization • Partnership Project established on July 24, 2012 • globally applicable • access independent M2M service layer technical specifications and reports • Open to all market segments • Participation: 7 PT1, 1(+8) PT2, 241 members, 2 associate members • Introduced scope and structure • Target to have first release by end of 2013 • Will reuse as much as operationally and technically viable specs from member organizations • M2M Service Layer • Software layer between M2M applications and communication HW/SW that provides data transport • Support common functions needed by different applications
MSTF Atlanta Highlights (4) • Joachim Koss – oneM2M • Benefits • Lower fragmentation, • Cost savings by lowering CAPEX and OPEX for M2M services, • Faster time to market (address use cases and markets where cost was prohibitive so far) • M2M users to focus on their core business and not worry about solving M2M communications and challenges • Service Functions • Bootstrapping and security procedures • Integration of Device Management • Data exchange procedures • Other advantages • Reduces complexity • Use of same technology in other verticals • Provides interoperability • Too Premature to provide ability to use Open Source
MSTF Atlanta Highlights (5) • Dr. William Web, Weightless SIG • Whatever IoT is, it is big • 3 functions need to be performed : Collect information, send information to central processing point, processing of information • Sensors need wireless networks • Really low cost point for sensors ($2-$3) • Global reach (economies of scale because of low cost) • Need improved wireless network that can provide good coverage, extended battery life and low cost modules • And wireless networks need spectrum that is globally harmonized, low cost, <1Ghz, and plentiful • Only TV whitespace appears to meet these criteria • Almost every country uses UHF band for TV • Will access change to whitespace spectrum (fees, less spectrum, more congestion)
MSTF Atlanta Highlights (6) • Dr. William Web, Weightless SIG • Designing for IoT and white space but brings some ramifications • Ubiquitous coverage implies a cellular architecture • Deep indoor coverage with low transmit power need spreading to extend range • Lower transmit powers at the device imply narrowband uplink to balance the link budget • White space operation implies TDD • Unlicensed operation brings interference risk requiring frequency hopping to mitigate • Tight emission limits require single-carrier modulation to enable rapid roll-off • Large number of terminals requires careful network scheduling • Need global open standard • http://www.weightless.org
MSTF Atlanta Highlights (7) • Dr. William Web, Weightless SIG • Summary • Massive global market for machine communications • Not met to date because of lack of suitable radio spectrum • Radios need spectrum and white space provides a near perfect solution • Weightless is custom-designed for this space and is now being standardized • Issues • small sensors big antenna • relation to work in IEEE 802 • impact of battery life, latency/frame rates, synchronization
MSTF Atlanta Highlights (8) • Dr. Steve Liang, Open Geospatial Consortium (OGC) • 500 members, consensus process, develop publicly available encoding and interface standards that geo- enable the web, wireless, location based services and mainstream IT • Standards (GML, KML, O&M, SensorML, WMS, WMTS, SOS, WFS) • 80% of all information is geospatial • Region centric, feature-centric, human-centric, device-centric • OGC standards relevant to IoT • GML (need location,semantics and geometry, especially important for smart buildings) • Indoor GML –enables indoor applications e.g. emergency control, visually handicapped guidance, indoor robots • IoT location information should use geospatial standards
MSTF Atlanta Highlights (9) • Dr. Steve Liang, Open Geospatial Consortium (OGC) • Need for interoperability of standards • More innovative applications by mashing up the IoT data infrastructure • If overlapping standards, then need to explore how to harmonize those standards • Internet of Things will be everywhere • To make IoT information useful location is critical • Use geospatial standards to describe IoT location information • Many IoT devices and applications will be indoor • http://www.opengeospatial.org
MSTF Atlanta Highlights (10) • Michael Koster, Open Source Internet of Things (OSIOT) • IOT value proposition • The network effect (more connections, greater the value) • Incremental value (conversion of capital assets to managed resources) • M2M and IoT – the Big picture • M2M – connectivity, protocols and APIs and vertical integration • IoT – interoperability, APIs and Data Models, Horizontal Integration • IOT is built on M2M
MSTF Atlanta Highlights (11) • Michael Koster, OSIOT • IOT is built on M2M • IoT is more than standardized M2M • Adds data model layer • Open internet protocols and RESTful APIs • Event Driven Architecture • Platforms are both vertical and horizontal • For IoT • Horizontal platform • Interoperability of data models • Bottom up practical standard • Build as an industry working together
MSTF Atlanta Highlights (12) • Michael Koster, OSIOT • IOT standards include M2M • Add a layer of discovery, interoperability, and autonomy • Need to work across diverse M2M systems • Provide a common application services layer • Provide a common resource abstraction layer (don’t need to know what M2M platform/system is being used, use data streams)
MSTF Atlanta Highlights (13) • Michael Koster, OSIOT • Open Source = Multiple Sources • Let’s Build Standards Together • OSIOT: focus on developing an Open Source horizontal platform for the Internet of Things • Founded in Santa Clara, CA on Oct. 29, 2012
MSTF Atlanta Highlights (14) • Mike Millinkovich, Eclipse • 190 members • Every piece of software needs to be embedded in a commercial product • Three Tenets • Meritocracy- demonstrate you have the merit to write code • Transparency • Openness –open to all into the project if they demonstrate merit
MSTF Atlanta Highlights (15) • Mike Millinkovich, Eclipse • The market is fragmented • M2M development is complex • Current options are closed • Enable developers to adopt the technology by use of open development tools • Focus on Framework, protocols, tools • Developers are the new kingmakers • What does open really mean • http://www.eclipse.org
MSTF Atlanta Highlights (16) • Mike Millinkovich, Eclipse • Hard battle between existing M2M players and Open Source • World has changed and traditional operators have to work and talk with the developers.
MSTF Atlanta Highlights (17) • Dr. Laurent Liscia, Peter Niblett, OASIS • How do we get the data from the sensors to the analysis • MQTT Technical Committee: developed a lightweight protocol with predictable bi-directional message delivery • An open approach to connectivity for Mobile, M2M and IoT
MSTF Atlanta Highlights (18) • Dr. Xavier Vilajosana, OpenWSN Project, UC Berkeley • Open WSN (Wireless Sensor Networks) developed very robust protocol • Open Source • Addresses lower layers (physical, MAC, etc.) • OpenWSN is one of the answers for a trillion WSN • Supported by available commercial hardware • Standards based (IEEE, IETF)