FIWARE NGSI Overview Juanjo Hierro FIWARE Chief Architect

FI-WARE NGSI Overview Juanjo Hierro, FI-WARE Chief Architect http: //www. fi-ware. eu June 2012 The FI-WARE Project – Core Platform of the Future Internet

Index 01 02 03 Basic concepts APIs NGSI in the FI-WARE Architecture The FI-WARE Project – Core Platform of the Future Internet

01 Basic concepts The FI-WARE Project – Core Platform of the Future Internet

Context § OMA NGSI Context Management is about management of Context data (aka Context Information) § Context Information is always relevant to “entities”, although entities can be anything (applications, users, things, …) Context Broker The FI-WARE Project – Core Platform of the Future Internet 3 Applications

Context Elements (1/2) § Context Information in OMA NGSI is represented through data structures called context elements which have associated: • An Entity. Id and Entity. Type, uniquely identifying the entity to which context data refers. • A sequence of one or more data element attributes (<name, type, value> triplets) • Optional meta-data linked to attributes (also <name, type, value> triplets) § As an example, we may consider the context element reporting info on: • attributes “speed”, “geolocation”, “current established route” of a “car”, or • attributes “last message geolocation”, “last message contents” of an “user” § The Entity. Id is a string, and can be used to designate “anything”, not necessarely “things” in the “real world” but also application entities Context Element Meta-data Context Element attributes “has” • Entity. Id • Entity. Type 1 n The FI-WARE Project – Core Platform of the Future Internet • Name • Type • Value 4 “has” 1 n • Name • Type • Value

Context Elements (2/2) § There may be as many kinds of Context Elements as combinations of attributes linked to an entity: • Typically a context element is generated whenever an query (update) on values of a list of attributes linked to an entity is requested (occurs) • Only queried/updated attributes are communicated, so the amount of information that is transmitted is minimized § Example: • Cars may have attributes “brand”, “model”, “license plate”, “established route”, “geolocation”, “current speed”, “gas level” • The first time existence of the car is recorded, a context element bringing values of attributes “brand”, “model”, “license plate” is generated • Any time a route is established using the cars’ navigator, a context element bringing updated values of “established route”, “gas level” and “geo-location” is generated whenever a route is established • A context element bringing updated values of “geo-location”, “current speed” and “gas level” is generated every x minutes § Occurrences of context elements are referred as “events” in FI-WARE The FI-WARE Project – Core Platform of the Future Internet 5

Conceptual model: advantages §Not linked to a particular data/context representation formalism: • Neither for transferring • Nor storing §Can work with a standard Io. T formats (Sensor. ML) but at the same time allows to overcome the limitations derived from the adoption of a single standard format §The flexible nature of data structures linked to context elements enable an optimized communication (only information about queried or updated attributes is transferred) The FI-WARE Project – Core Platform of the Future Internet 6

02 APIs The FI-WARE Project – Core Platform of the Future Internet

OMA NGSI and FI-WARE APIs §NGSI Context Management specs have been published by OMA but FI-WARE will not stick to what has been published: • Ready to change whatever makes the API more usable and useful • Ready to incorporate extensions to make the API more powerful yet simple • Ready to fast-track incorporated changes in OMA §That’s why we distinguish between “OMA NGSI” and “FI-WARE NGSI” §We may consider potential extensions dealing with stream-based communication in the future, for example The FI-WARE Project – Core Platform of the Future Internet 8

Basic entities and operations (1) § Context Producers publish data/context elements by invoking update. Context operation on a Context (Publish/Subscribe) Broker. the § Context data is kept persistent by Context Brokers and ready to be queried while not exceeding a given expiration time. This is a distinguishing feature of the OMA Context Management model as compared to some Event Brokering standards. § You can think in the Context Broker as a kind of virtual Repository/DB where producers insert context information and consumers query for it § Context Consumers can retrieve data/context elements by invoking the query. Context operation on a Context Broker update. Context Producer query. Context (Publish/Subscribe) Broker The FI-WARE Project – Core Platform of the Future Internet 9 Context Consumer

Basic entities and operations (2) § Some Context Producers may also export a query. Context operation Context Brokers may invoke at any given time to query on values of a designated set of attributes linked to a given set of entities. They are called Context Providers. § Because Context Providers exporting the query. Context operation are typically unknown “a priori”, Context Brokers export a register. Context operation which enable to register what Context Producers may be queried § Note that the Application which subscribes a particular Context Producer may or may not be the/a Context Producer itself Application register. Context (producer URI, registration data, duration, registration_id) query. Context Provider query. Context (Publish/Subscribe) Broker The FI-WARE Project – Core Platform of the Future Internet 10 Context Consumer

Basic entities and operations (3) § Some Context Consumers can be subscribed to reception of data/context elements which comply with certain conditions, using the subscribe. Context operation a Context. Broker exports. Such subscriptions may have a duration. § Subscribed consumers spontaneously receive data/context elements compliant with that subscription through the notify. Context operation they export § Note that the Application which subscribes a particular Context Consumer may or may not be the/a Context Consumer itself Application subscription_id = subscribe. Context (consumer, expr, duration) notify. Context (subscription_id, data/context) Context (Publish/Subscribe) Broker The FI-WARE Project – Core Platform of the Future Internet Context Consumer 11

About queries, registrations and subscriptions § Queries, registrations and subscriptions requests are formulated on: • List of entity ids (these ids may include patters) • List of attributes or “attribute domains” (identifiers used to denote a group of related attributes) § Besides, queries and subscriptions requests can be formulated so that certain restrictions, established as conditions upon values of given attributes or metadata, have to be met. The FI-WARE Project – Core Platform of the Future Internet 12

Context Broker Federation (1) §A Context Broker may be subscribed as Context Consumer on another Context Broker Application subscr_id_1 = subscribe. Context (consumer 1, expr 1, duration 1 update. Context Producer query. Context notify. Context Broker 2 Context Consumer 1 query notify. Context Consumer 2 subscr_id_2 = subscribe. Context (Context Broker GE 2, expr 2, duration 2) Context Broker 1 Application The FI-WARE Project – Core Platform of the Future Internet 13

Context Broker Federation (2) § A Context Broker may be subscribed as Context Producer on another Context Broker Application subscription_id_1 = subscribe (consumer 1, expr 1, duration 1) update. Context Producer query. Context notify. Context Broker 2 Context Consumer 1 query. Context Consumer 2 register. Context (Context Broker GE 2, what, duration 2) Context Broker 1 Application The FI-WARE Project – Core Platform of the Future Internet 14

Handling multiple subscriptions § A single Context Broker GE may handle several subscriptions § A Context Consumer may be subscribed through more than one subscription § A Context Consumer may consume events through subscriptions or making explicit queries Context Broker GE Context Consumers subscriptions query Context Producers update notify subscription ports update query The FI-WARE Project – Core Platform of the Future Internet Producers port 15 notify

Extended operations (1) § Context Brokers export the discover. Context operation enabling applications to discover entities or even attributes and attribute domains that have been registered in the system register. Context Application 1 discover. Context (Publish/Subscribe) Broker The FI-WARE Project – Core Platform of the Future Internet 16 Application 2

Extended operations (2) § Some applications can be subscribed to registration of entities or availability of attributes and attribute domains which comply with certain conditions, using the subscribe. Context. Availability operation a Context. Broker may export. Such subscriptions may have a duration. § Subscribed applications spontaneously receive updates on new entities, attributes or attribute domains compliant with that subscription through the notify. Context. Availability operation they export § Note that the subscriber and subscribed applications may not be the same application 1 subscription_id = subscribe. Context. Availability (application 2, expr, duration) notify. Context. Availability (subscription_id, updates) Context Broker The FI-WARE Project – Core Platform of the Future Internet application 2 17

Some hints about OMA NGSI specs § Operations are grouped into two major interfaces (not clear why • NGSI-10 › › update. Context › › › register. Context › notify. Context. Availability query. Context subscribe. Context / unsubscribe. Context / update. Context. Subscription notify. Context • NGSI-9 discover. Context. Availability subscribe. Context. Availability / update. Context. Availability. Subscription The FI-WARE Project – Core Platform of the Future Internet unsubscribe. Context. Availability 18 /

03 NGSI in the FI-WARE Architecture The FI-WARE Project – Core Platform of the Future Internet

FI-WARE Context/Data Management Platform Applications Processing/Analysis Algorithms FI-WARE NGSI-9/10 Pub/Sub Context Broker (Gathering / Publication) Data generated either by CEP or Big. Data is published Gathered data injected for CEP-like processing Distributed Context Sources Gathered data is injected for processing/ana lysis Big. Data Analysis/Processing (COSMOS = SAMSON + Hadoop) Complex Event Processing CEP (IBM’s PROTON) Context/Data Management Platform The FI-WARE Project – Core Platform of the Future Internet Processed data is injected for processing/ana lysis 20

FI-WARE NGSI for Io. T Applications FI-WARE NGSI-9/10 (entities: things, sensors, other) Pub/Sub Broker GE Io. T-enabled Context Broker Things Management GE Device-level Management API FI-WARE NGSI-9/10 (entities: sensors) NGSI Io. T Adapter Device Management GE Backend Native NGSI Io. T Agent The FI-WARE Project – Core Platform of the Future Internet

FI-WARE NGSI for Io. T Applications FI-WARE NGSI-9/10 (entities: things, sensors, other) Pub/Sub Broker GE Io. T-enabled Context Broker Things Management GE (entities: sensors) Device-level Management API FI-WARE NGSI-9/10 § The NGSI Io. T Adapter can register sensors by invoking the register. Context operation § The NGSI Io. T Adapter exports a query. Context operation that enable to query the value of a variable measured through a sensor (or several variables on several sensors) § Spontaneous updates from sensors are mapped into an update. Context operation invocation that NGSI Io. T Adapter invokes on the Io. T-enabled Context Broker § The Io. T-enabled Context Broker knows how to translate a) queries on attributes of things into queries on sensor variables, b) updates on sensor variables into updates on attributes of things The FI-WARE Project – Core Platform of the Future Internet NGSI Io. T Adapter Device Management GE Backend

FI-WARE NGSI for Io. T Applications FI-WARE NGSI-9/10 (entities: things, sensors, other) Pub/Sub Broker GE Io. T-enabled Context Broker Things Management GE Device-level Management API FI-WARE NGSI-9/10 (entities: sensors) Components implementing OGC SWE interfaces Backend Native NGSI Io. T Agent NGSI Io. T Adapter Native NGSI Io. T Agent The FI-WARE Project – Core Platform of the Future Internet Backend

Thank You !! The FI-WARE Project – Core Platform of the Future Internet