to Serve the Internet of Things: the oneM2M Initiative David Foote CTO, Hitachi CTA ATIS Board of Directors Vice-Chair, oneM2M Steering Committee [email protected] 1
to Serve
the Internet of Things:
the oneM2M Initiative
David Foote CTO, Hitachi CTA ATIS Board of Directors Vice-Chair, oneM2M Steering Committee [email protected]
1
Hitachi Corporate Overview
16%
8% 11%
10%
7%
13%
7% 8%
9% 4%
7%
Information & Telecommunication Systems ($19.9B) Social Infrastructure & Industrial Systems
Digital Media & Consumer Products High Functional Materials
& Components
Other
Financial Services
Automotive Systems
Power Systems
Electronic Systems & Equipment
Construction Machinery
Components & Devices
Hitachi, Ltd Revenues: US $112.2B Employees: 360,000 #3 Rank, Fortune Global 500
Electrical/Electronics companies #40 Rank Overall
US Patents Awarded 1465 patents in 2011, Rank #10
Global employees: 71,000
Major Customers & Partners:
2
Hitachi and M2M
Hitachi is an M2M “User” – Example: Hitachi Construction Machinery uses embedded devices, GPS, cellular and
analytics to track construction machinery assets, monitor usage, etc.
Hitachi is an M2M industry segment “Vertical Supplier” for the Smart Grid, eHealth, Connected Car/Telematics, Smart City, etc. (many others) – Hitachi Power provides generation, smart grid distribution and control systems – Hitachi Medical provides imaging, diagnostic, analysis, bioinformatics, HIS systems – Hitachi Automotive and Clarion provide automotive control systems and IVI systems
Hitachi is an M2M “System Integrator”
– Hitachi Consulting provides SI design, implementation and project management
Hitachi provides M2M “IT Infrastructure”
– Hitachi Data Systems provides storage, servers, virtualization, etc.
Hitachi provides “Telecom Systems” for Service Provider’s M2M Offerings – Hitachi Telecom provides LTE packet core, gateways and management systems for
SPs plus middleware enabling multiple M2M “applications” on the same embedded device/gateway while abstracting complexities like Zwave, ZigBee, 6LoWPAN, etc.
– x
Unusual, if not unique, in its scope related to M2M (just a few examples are highlighted)
3
ATIS in Brief
• Defines technology solutions and standards to support the timely roll-out of new products and services.
Thirty years of industry leadership
Diverse membership: wireline , wireless, cable and broadband service providers, telecom equipment and consumer electronics vendors, software developers, digital rights management firms, government and public safety agencies, etc.
• ~50 member C-level Board defines the strategic vision and priorities
Most senior of all industry organizations; access to business, technical, operations
• CIO Council (SPs only): defines IT priorities recognizing the value of integration and evolution of network and IT; CIO direction distinguishes ATIS from other organizations
• Represents North American positions into ITU (via State Department)
• Standards and solutions covers all aspects of the technology lifecycle
From innovation and solution design, to business use case formulation, to requirements, specifications, standards, interoperability testing, software tool kits, best practices, data collections, user guidelines and more . . .
200+ member companies 500+ subject matter experts
4
ICT Ecosystem Coverage
M2M inter-related new initiatives
BIG DATA & ANALYTICS
MOBILE DEVICE INTEGRITY
OVER-THE-TOP
NETWORK VIRTUALIZATION
DYNAMIC NET MANAGEMENT
(incl WiFi)
M2
M V
alu
e C
hai
n
Module Machine Network Middleware System Integrator
Service Provider
End
User
Application Developers
System Integrators
Network Equipment Providers
Service Providers
Middleware Providers
Machine & Device Manufacturers
Devices
Trust & Identity
Cyber Security
AT
IS
Init
iati
ve
s
M2M Value Chain and ATIS
6
M2M Focus Group
• Machine-to-Machine Focus Group (M2M FG) addresses M2M generally, and Smart Grid, Connected Vehicle, eHealth specifically:
– In-depth Use Case definition and analysis to identify common requirements/specifications
– Architectural definition for M2M Service Platform • common Service Layer “elements” that enhance value of M2M
services/apps
• ATIS’ Wireless Technologies and Systems Committee (WTSC) also addressing mobile healthcare:
– Protocols and enhancements to wireless networks and the IP Multimedia Subsystem (IMS) to transport medical data securely.
7 7
ATIS M2M Activities
Proprietary approaches to M2M cannot scale…
A Common Service layer will leverage core network
capabilities and enable Service Providers to enhance
the overall M2M ecosystem.
Strategic M2M Opportunity
8
• Many industries are addressing M2M solutions and applications. • Current solutions are unique to each industry, and often even unique
across companies/systems in the same industry --- custom hardware and software.
• Result: longer time to market; greater development costs and operational expenses; and frequently inflexible, custom, tightly-coupled solutions.
• M2M services often rely upon telecom Service Providers for connectivity between the myriad of devices in the field and the M2M application servers
• SPs are optimizing networks to effectively meet industry needs for M2M communications; developing standards for these optimizations
• Common cost-efficient, easily and widely available M2M Service Layer, readily embedded within various hardware and software
9 9
M2M Opportunity: Leads to oneM2M
• “Global Initiative” to consolidate Service Provider related standards for M2M started in May 2011 by seven leading regional telecom Standards Development Organizations (SDOs): ARIB and TTC (Japan), ATIS and TIA (North America), CCSA (China), ETSI (Europe), TTA (Korea)
• First meeting held in Seoul (July 2011). Subsequent meetings in Washington, DC (August), Berlin (December) and Tokyo (March 2012) with bi-weekly teleconferences on average between each meeting.
• Formal signing of a Partnership Agreement by seven SDOs and first meeting of the oneM2M Steering Committee held in Bellevue, Washington on July 24 – 26, 2012
• First meeting of Technical Plenary held in Nice, France on Sept 24 – 28
• Next Technical Plenary meeting in Beijing, China on December 10 – 14
• Target release of first specification(s): 4Q 2013
oneM2M Chronology
10
• Develop one globally agreed specification with initial focus on a common Service Layer for Service Provider’s networks to provide services to customers and users of M2M applications
• Consolidate current M2M Service Layer standards activities into oneM2M
• Identify a common Service Layer architecture and identify gaps where existing standards do not fulfill the requirements and provide or initiate the creation of specifications to fill these gaps
• Collaborate with wireless and wireline SDOs and fora responsible for developing standards for Core and Access Networks
• Collaborate with SDOs and fora in charge of developing standards for the industry segments (i.e., domain-specific) aspects of M2M applications
• 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
Goals of oneM2M
11
Benefits of oneM2M
Common service layer
valued in excess of $10
billion*
Leverage functions and/or capabilities
common across multiple M2M applications
Enable supplier interoperability
Monetize new services
Reduce overall operating and
capital expenses
Improve time-to-market
Enable mass-market economies
of scale
Deliver a high-quality user experience
Integration of services and
applications across industry segments
(reduce fragmentation)
* Beecham
12
• Use cases and requirements for a common set of Service Layer capabilities.
• Service Layer aspects with high-level and detailed service architecture -- access agnostic view of end-to-end services:
– Protocols/APIs/standard objects based on architecture (open interfaces, protocols);
– Security and privacy aspects (authentication, encryption, integrity verification);
– Reachability and discovery of applications;
– Interoperability, including test and conformance specifications;
– Collection of data for charging aspects (used for billing and statistical purposes);
– Identification and naming of devices and applications;
– Information models and data management; and
– Management aspects (including remote management of entities)
• Terminal/module issues , device abstraction, other issues not yet agreed to be included in the scope of work or may be for future work.
Scope of oneM2M
13
Common Service Layer characteristics across all industry segments:
• Provisioning
• Device management
• Configuration management
• Firmware management
• Device application software
management
• Authentication and registration
• Device triggering
• Device communication
• Services (ex: location, messaging, etc.)
• Group management for
communication
• QoS/SLAs
• Policy management
• Data processing and storage
• Notifications
• Diagnostics
• API management
• Billing
Service Layer: Characteristics
14
Co
mm
on
fe
atu
res
for
in
du
stry
seg
me
nts
Common M2M Service Layer
WAN Technologies
M2M Applications
SEN/LAN Technologies
WAN Transport Network
M2M SEN / LAN
M2M Platform
Gateway/APIs
M2M Devices
End to End M2M Service
Access Network
Gateway/APIs Gateway/APIs
An M2M Generic Architecture
15
• Organizations
– ICT/Telecom SDOs
– Others standards and specifications setting organizations (especially industry segments)
– Industry groups
– Associations
– Specific technology organizations
• Individual Companies
– Service Providers (e.g., M2M SPs, Telecom SPs, Service Layer SPs)
– M2M service users (e.g., Utilities, Transportation, Health/Medical, Industrial, Retail, etc.)
– Vendors (e.g., M2M Application Providers)
• Regional/National Governmental Entities
• Participation needs to:
– Be open and well balanced
– Provide opportunities for various levels of participation
– Accommodate companies and organizations
Target Participation of oneM2M
16
David Foote CTO, Hitachi CTA ATIS Board of Directors Vice-Chair, oneM2M Steering Committee
17