M2M / Internet of Things Towards M2M/IoT architecture - Global SDOs activities. Sivabalan Arumugam NEC India Pvt Ltd

Transcription

1 M2M / Internet of Things Towards M2M/IoT architecture - Global SDOs activities Sivabalan Arumugam NEC India Pvt Ltd

2 Outline Introduction M2M Services across Industry Verticals Why M2M standards? What improvements can be expected by standards? M2M SDOs and Industrial Groups GISFI IOT Working group GISFI IoT Light Weight Framework Summary Page 2

3 M2M/IoT Introduction Definition: defined as a dynamic global network infrastructure with self configuring capabilities based on standard and interoperable communication protocols where physical and virtual things have identities, physical attributes, and virtual personalities and use intelligent interfaces, and are seamlessly integrated into the information network ETSI GISFI View: IoT can be viewed as a global infrastructure for the information society, by interconnecting (physical and virtual) things based on, interoperable information and communication technologies towards providing advanced information services. Page 3

4 IoT/M2M - expectations Convergence Anything Any device Connectivity Any place Any where Communication Anytime Any context Internet of Things Any path Any Network Computing Anyone Anybody Content Any Service Any Business Collections Importance 6C: Convergence, Computing, Connectivity, Content, Communication, Collections Page 4

5 M2M Services across Industry Verticals(1/2) Manufacturing Industrial Automation Factory Line Equipment operation Usage Tracking E-Health Remote Physician Consultation Body sensor and Diagnostic reporting Remote diagnostics Security Home and Enterprise Security Alerts and remote access Video surveillance Utility Smart Metering Wind power panel health monitoring and control Transport/Logistic Fleet Management Sale force tracking Consumer Application Home automation Financial and Retails POS NFC Page 5

6 M2M Services across Industry Verticals(2/2) 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 APIs 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. Page 6

7 Why M2M standards? Enable the vision of a horizontal service layer Page 7

8 What improvements can be expected by standards? To enable plug and play M2M services Business Application Service providers should only need to think about their service - not to implement tasks that are common to most M2M services. Common tasks can be delegated to the M2M Service enablement (connectivity, security, AAA, lifecycle management, deployment support, subscription management, maintenance, ) Page 8

9 M2M SDOs and Industrial Groups M2M/ IoT Architecture can be grouped: - Sensors based Device layer (ETSI M2M) - Mobile based Device layer (3GPP MTC, OMA) - Target device independent (One M2M, GISFI) Page 9

10 onem2m Partnership Project onem2m is a Partnership Project, established (mid 2012 by the 7 worldwide telecom SDOs) in order to cooperate in the production of globally applicable, access-independent M2M Service Layer specifications, including Technical Specifications and Reports related to M2M Solutions Currently 265 Participating Partners and Members Dec First release of Minimally deployable solution Source: onem2m-tp r03-consolidated_workplan_summary Page 10

11 OneM2M relationship with selected other SDOs ETSI TC M2M Has finished M2M Release 1 Try to re-use as much as possible in onem2m 3GPP Working on MTC features since over 3 years Interworking with onem2m needed BBF Re-using device management capabilities in onem2m Page 11

12 Other Global Initiative ITU-T (global): Joint Coordination Activity on Internet of Things (JCA-IoT): Identification (e.g. identifiers like E.164, reader/writer like RFID interrogator, tags like RFID tag, barcode tag..), ubiquitous sensor network (USN). Focus Group on M2M Service Layer: identify Requirements, APIs and protocols, initially focussing on ehealth (co-operation with WHO, Continua) Internet of Things Global Standards Initiative (IoT-GSI): single location for information on and development of IoT standards GSMA (global) Connected living program (CLP) is identifying requirements for mobile network support for several market sectors automobile, healthcare, education, and smart city OMA DM work on lightweight M2M (global): Specifically looking at constrained devices (low energy consumption, inexpensive..) optimize M2M service implementation by using light weight protocol in service layer. Non-RESTful, IP and None-IP transport: Wireless (SMS, USSD, CSD), simple security This activity in OMA is mainly driven by Chinese operators and vendors Page 12

13 GISFI IOT Working group GISFI Internet of Thing WG started in Dec 2009 Current Chair: TCS Vice-chair: Ericsson WG Strategy towards IoT Framework : Three Goals To develop application independent Generic IOT Framework with well-defined Reference Architecture To achieve interoperability between the various devices/application developed in multi-vendor scenario To achieve cost advantage and pass this advantage to the user group for its mass scale deployment and applicability Page 13

14 GISFI IoT WG - Documents Usecase Documents 1. GISFI_IoT_ : TR Agriculture Application Usecase 2. GISFI_IoT_ : TR on mhealth Use Cases, 3. GISFI_IoT_ TR on Food Supply Chain Management (FSCM) Use Cases 4. GISFI_IoT_ : TR on Surveillance Security System Use cases 5. GISFI_IoT_ : TR on Landslide Detection Use-case, 6. GISFI_IoT_ : TR on e-health Use Case, 7. GISFI_IoT_ : TR on Smart City Usecase Requirement Documents 1. GISFI_IoT_ : TR on IoT Service Capabilities 2. GISFI_IoT_ : TR on Privacy Requirements of User Data in Smart Grids 3. GISFI_IoT_ : TR on Naming and Addressing in IoT, IOT Architecture Document 1. GISFI_IoT_ : TR on Internet of Things Reference Architecture, 2. GISFI_IoT_ : TR on Indian relevance to Healthcare Service Delivery mechanism based on Generic IOT Framework 3. GISFI_IoT_ : Healthcare Service Delivery mechanism based on Generic IOT Framework 4. GISFI_IoT201309xxx: Technical Specification IOT Light Weight Architecture (Draft) Page 14

15 GISFI IoT Light Weight Framework Applications I3 Service Platform I2 IoT Core Network Lightweight Restful architecture, with Web services, Lightweight authentication and secured communication channel Gateway I1 Sensor / Devices Lightweight communication across devices, lightweight device management, Lightweight authentication and secured communication channel Focus to standardize the Interface I1, I2, and I3 Page 15

16 Summary OneM2M first release of minimally deployable solution by 4Q 2013 Next release of 3GPP expected to Interworking with onem2m GISFI Technical Specification of Lightweight IoT expected by Dec 2013 Collaborative effort of different application sector participation in standardisation can produce generic IoT architecture. Page 16