Future Internet and Internet of Things standardisation. Status and challenges.

1. Future Internet and Internet of Things standardisation. Status and challenges. Inge Grønbæk, Group Industrial Development, 01.02.2012

2. Example verticals (1 of 2)[Millions of objects by 2014 – Indicative example] Surveillance applications, alarms, object / people tracking [14] Security Fleet management, emission control, toll payment,road safety (e.g. eCall stow pipe) [95] [95] Transportation e-Health, and personal security Heath care Smart Metering and Grid [34]such as oil, water, electricity, heat, and others Utilities Production chain monitoring and automation Manufacturing 2

3. Example verticals (2 of 2) Freight supply and distribution monitoring, Vending Machines Supply andProvisioning Home / building / campus automation FacilityManagement … Multitude of new M2M applications based on standardized Service Capabilities and API [Ericsson CEO vision of 50 Billion Connected Objects by 2020] Future 3

4. Vertical fragmentation • Fragmented industry verticals: • most industries are solving their M2M needs on their own; • often converging upon similar architectures and elements; • the M2M “wheel” is reinvented from industry to industry. • Customized solutions abound: • since solutions are on an industry-by-industry basis, each solution requires its own design, production, and implementation cycle; • unique solutions often result in sole-sourcing of customized hardware; • software design is limited to a small group of developers who understand the architecture and API’s for a particular industry or platform, thus leading to high development costs and high costs for support. • Lack of scale for components: • economies of scale are difficult to achieve in any given industry since solutions are so varied and unique.

5. Needs to invert the stove pipes applications share common Service Capability Layer existing proprietaryvertical applications… Business Business Business Application1 Application 2 Application N API Service Capability Layer Network Infrastructure Converged Network ( mobile infrastructure IP ) Gateways / Concentrators M2M Device M2M Device M2M Device

6. Merits of Service Capabilities and API • Service Capabilities provide functions that are to be shared by different applications in an interoperable manner. • Service Capabilities expose functionalities through open interfaces (e.g. an API). • This will support interoperable ubiquitous services, however, area-specific data-models may be required (e.g. for Smart Metering /AMR). • Service Capabilities simplify and optimize applications development and deployment and hide technology specifics. • Service Capabilities may be M2M specific or generic, i.e. providing support to other than M2M applications (e.g. the capabilities of the OneAPI adopted by GSMA/WAC).

7. Standard is needed • M2M is here, and has massive potential for growth to be unleashed by standards. • M2M first step towards future Internet of things (IoT) and will support Smart Metering/Grids. • Market value increases with the “square” of interoperable/ accessible services. • Operators and vendors see ETSI as a good place to do the work, however, progress requires wider consensus. (IETF, OMA and BBF contributes parts)

8. M2M Standards Development Organizations (SDOs) and Industrial Groups ISO/IEC JTC1 SGSN IUT-T NGN ESMIG Metering EPCGlobal GS1 CENELEC Smart Metering CEN Smart Metering Utilities Metering HGI Home Gateway Initiative OASIS ANSI TIA/TR50, ATIS ETSI M2M/ITS/… W3C WOSA MSTF IETF 6LowPAN Phy-Mac Over IPV6 KNX CCSA TC 10 TTA BBF IPSO IPV6 Hardware and Protocols W-Mbus TTC IETF ROLL Routing over Low Power Lossy Networks GSMA EMP, ESIM 3GPP SA1, SA2, SA3, ,… CDG SIG ZigBee Alliance. ZB Application Profiles IEEE 802.xx.x OMA Arc TISPAN

9. M2M status 01.09.2011 M2M standards consolidation into a Partnership Program (M2MPP) • At ETSI GA#57 a wide membership proposal (basically the “Industry Group”), for consolidation was approved. • SDOs (ARIB, ATIS, CCSA, ETSI, TIA, TTA, and TTC) agrees to consolidate M2M standardization by 2012. • Verticals need to be engaged.  • The initial scope is to define a network agnostic service Capability Layer (SCL) and APIs. • SDOs are permitted to participate in ETSI TC M2M on an interim basis, until the Global Initiative is successfully created. • http://www.etsi.org/WebSite/NewsandEvents/2012_01_M2M_Global_Initiative.aspx

10. TIMELINE (Source Huawei)

11. M2MPP objectives • Develop one globally agreed M2M specification with initial focus on Service Layer. • Interface this Service Layer to higher layer applications and underlying network transport capabilities through a standardized adaptation layer, if necessary. • Consolidate current M2M Service Layer standards activities into the M2MPP. • Partner/Collaborate with wireless and wireline SDOs and fora responsible for developing standards for Core and Access Networks (e.g. 3GPP). • Partner/Collaborate with SDOs and fora in charge of developing the vertical markets (i.e., domain-specific) aspects of M2M applications. • Partner/Collaborate with SDOs and fora in charge of developing auxiliary specifications (e.g., OMA, BBF Device Management and Device APIs, W3C for Device APIs). • Develop specifications that will help drive the industry towards a goal of lower operating expenses, lower capital expenses, faster time-to-market, and mass-market economies of scale.

12. ITU-T M2M Service Layer Focus Group established in Jan. 2012 • M2M is included under the larger umbrella of the “Internet of Things” (IoT). • The group will study and evaluate the M2M landscape and M2M work currently being undertaken by regional and national standards development organizations (SDOs), with a view to identifying a common set of requirements. • The Focus Group will initially focus on the APIs and protocols to support e-health applications and services. • The Focus Group will work closely with all ITU-T Study Groups and with other relevant SDOs, forums/consortia, regulators, policy makers, industry and academia. Within the ITU, the group will work particularly closely with the Internet of Things Global Standards Initiative (IoT-GSI).http://www.itu.int/en/ITU-T/gsi/iot/Pages/default.aspx.

13. IETF/CoRE • The IETF work of the 6LoWPAN, ROLL and CORE Working Groups (WGs) is of particular relevance for IoT/M2M. • The CoRE WG is providing a framework for resource-oriented (i.e. RESTful) applications intended to run on constrained IP networks. • the CoRE WG has defined a Constrained Application Protocol CoAP for the manipulation of Resources on a Device. The protocol supports the communications aspects of the M2M service layer. • CoAP and related protocols will continue to be developed by the IETF. • CoAP is adopted by ETSI M2M. • The CoRE infrastructure includes a Link format (discovery mechanism), an event subscription mechanism and a scalable device proxy. Devices are viewed as RESTFul resources and can directly be interacted with using HTTP or CoAP protocol operations (PUT, GET, POST, DELETE, etc.).

14. Telenor current market initiatives • Telenor Traxion • Telcage • Telespor Managed Services for dedicated verticals Service Providers / System Integrators Auto/Transport Point of sales Energy Security Asset mgmt New Verticals Vertical 1 Vertical 2 Vertical 3 Vertical 4 Vertical 5 Vertical 6 Vertical 7 Automotive Energy Security Point of sales Asset mgmt New Verticals Service Enablement Auto/Transport Point of sales Energy Security Asset mgmt New Verticals Automotive Security Energy Automotive Energy Security Point of sales Medical Asset mgmt New Verticals Asset Mngmt Point of Sales New Verticals Customers Connectivity