Internet of Everything: On the importance of the right Standard. Nicolas Graube, June, 2015

Transcription

1 Internet of Everything: On the importance of the right Standard. Nicolas Graube, June, 2015

2 The Argument IoT/IoE is viewed as a source of enormous growth The nature of the growth shall be refined is it silicon sale? is it communication volume? is it data intelligence? is it business transformation Practically, IoT/IoE are immensely diverse eco-systems due to the nascent markets. One essential question is to determine where the value is and what prevents its realisation 2

3 The Solution Evidently the solution is in Standardisation! But what exactly should be standardized? Thing Communication Data very unlikely, diversity is the part of the essence! Each embodiment has tentatively selected its most appropriate path one solution will not fit most. Arguably, this is the where the value could be unprecedented access to information its processing is transformational Focus on the area of Growth the value is NOT in the things, the value is in the transformational nature introduced by the things presence, information and control. 3

4 Difficulties at the transport IoT Standardisation cannot be ONLY about transport Arguably, transport and communication must be addressed Arguably, seeking an universal answer is too ambitious Diversity of embodiments makes standardisation hard Diversity exists out of necessity, not through adversity Risk of standardisation to the least common denominator Sensible to standardise within equivalence classes formed through existing Silos. Unnecessary to attempt to address cross silos at the transport level. IP universality is acceptable for high level and abstracted areas, but difficult at the thing. IP at the thing could be a step too far. 4

5 Importance of the Data From Digital Ubiquity (Marco Iansiti and Karim R. Lakhani) Harvard Business Review Nov/2014 General Electric s transformation through its introduction of industrial internet. Collecting information from its sensor, providing real-time analytics, fed back to its customers From an equipment vendor to equipment management May be less equipment sales, but closer and longer relations with its customers (resulting in $800M incremental income in 2013, $1B expected for 2014 and 2015). New outcomes-based business model Going further with partnership sharing the data 5

6 Importance of the Data Arguably, it is the availability of the data and its associated semantic which has allowed GE s transformation. Data Analysis has to be enabled across a variety of providers: Universal description of the data, resilient to changes Data transported is both informational and operational Data semantic allows for Predictive Analysis leading to some actions determined through the operational nature/capabilities of the sources We are arguing that IoE is not about summing but about integrating demanding precise interpretation knowledge: Big Data = data Better Data = data Standardisation has to pay particular importance to this point 6

7 IoE through a Data Focussed View IoE are about producing data and possibly collecting actions In isolation data models can be fixed, semantic is implied Going beyond the IoE silos ontologies must be clarified 7

8 Data with ontologies allows silos crossing IoE are producing data Data must be made available and readily interpretable (ontologies) Actions can results from these interpretations Abstraction allows for cross-domains activities, thus breaking silos. Treatment of ontologies as data makes the model future proof! 8

9 Ideal Enabling across silos what is happening within each silos, without disrupting them Standardisation of a semantic expression of IoE capabilities and information Promotes the existence of convergence platform External perception of (real) things through these convergence points 9

10 onem2m: A promising Standard onem2m ( : more than 210 partners and members Goal of onem2m: Develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. (Source: onem2m: about onem2m) 10

11 onem2m: Abstract Architecture Conceptually a silo is abstracted through the triplet (AE,CSE,NSE) Silos interactions managed through Mca/Mcc communications NSE (transport) unchanged, only Mcn has to be defined. 11

12 onem2m: Abstract Architecture The CSE is implemented as a set of CSFs (Common Service Functions) Current specifications are concerned with services that CSFs provide to higher layers or between CSEs inter-csf functionality is not specified. A Resource is a uniquely addressable entity in the RESTful architecture (Referenced by a URI) Has Attributes (metadata), which may be rw, ro, or wo. Resources can be Announced to other CSEs (so that they can be accessed via them without requiring a search across all CSEs. Ontology is missing from 1.0 to be addressed from 2.0 TR-0007-V

13 AllJoyn and onem2m Potential bi-directional ontological bridge AJ App 1 AJ App 2 AJ Network Connector Apps Service Exposing App mirror App A mirror App B Connector Apps AJ Gateway Agent with onem2m AE=IPE & CSE onem2m Exposure AE 12 onem2m AE A onem2m AE B Rsc srv 1 Rsc srv 2 onem2m CSE 1 AJ Gateway Agent with onem2m AE=IPE & CSE onem2m IN CSE 3 Annc Rsc Annc 1 Rsc 2 Annc Rsc A Annc Rsc B onem2m AE X onem2m AE Y onem2m AE Z AJ App A AJ App B AJ Network Service Exposing App mirror App 1 mirror App 2 onem2m Exposure AE AB onem2m AE 1 onem2m AE 2 Rsc srv A Rsc srv B onem2m CSE 1 onem2m Network AE Consume AJ service AJ s AE NSE CSE Provide AJ service Source: onem2m AllJoyn Inter-networking discussions TP WG2 ARC Josef Blanz, Phil Hawkes, Qualcomm Inc. 13

14 CSRmesh and onem2m Transport based on Ble Advertising Self contained semantics through Models Gateway Agent normalisation point (NSE) 14

15 What are we requiring? Standardisation is required for: Information available, structure and meaning Abstraction layer above convergence layer Expression of feedback loop Conservation of integrity and privacy, security through control of access to capabilities. Definition of exposed entities, including their capabilities Ability to address individual elements (no requirement for elements to be concrete, only what each layer is prepared to expose) Ability to uses entity capabilities for generic Command & Control Exposure of entities ontologies, offering data and ontologies manipulations Future proofing through ontologies. IoE/IoT/M2M has many justified varieties of transport, each fit for purpose, convergence seems an unnecessary challenge. 15

16 Copyright Confidential Cambridge Silicon Radio Limited