The document discusses Orion Context Broker, an implementation of a context information broker within the FI-WARE platform. It implements the OMA NGSI9/10 specification for managing context information and availability. Orion acts as both a Pub/Sub Context Broker generic enabler and Configuration Management generic enabler, allowing context producers to publish context data and consumers to retrieve it via operations like updateContext, queryContext, and subscribeContext. Context brokers can also federate by subscribing and registering with each other.
A brief description to FIWARE Ecosystem and detailed one of the FIWARE IoT framework. Introduction to Orion Context Broker, IoT Agent - Ultralight 2.0 and Short Term Historic - Comet.
FIWARE: Managing Context Information at large scaleFermin Galan
This presentation describes how context management is implemented in FIWARE platform, base don Orion Context Broker GEri. Both basic usage of Context Broker and advanced topics are included.
Context-aware application development with FIWARE #CPBR8Fermin Galan
Context-aware application development with FIWARE, used in the #CPBR8 workshop. It includes basic and advanced Orion topics, along with usage examples.
We present various approaches to providing an API as part of an IoT product and discuss certain business models for monetizing it.
Centaur Technologies develops and markets end-to-end solutions for the Internet of Things, focused on the Industrial and Enterprise sectors.
FIWARE NGSI: Managing Context Information at Large ScaleFIWARE
FIWARE NGSI: Managing Context Information at Large Scale, by Fermín Galán.
Orion Context Broker developing team. 1st FIWARE Summit, Málaga, Dec. 13-15, 2016.
Building nTier Applications with Entity Framework Services (Part 2)David McCarter
Learn how to build real world nTier applications with the new Entity Framework and related services. This second part to the series will focus on using the Entity Framework in an nTier/ SOA world by separating out the different layers using T4 templates and using the new WCF Data Services to easily expose entity models via REST and to Silverlight clients.
Topics of this presentation:
- Fundamental concepts and principles.
- General architecture guidance.
- IoT applications component design.
- Cross-cutting issues.
This presentation by Andrii Antilikatorov (Consultant, Engineering, GlobalLogic) was delivered at GlobalLogic Kharkiv .NET TechTalk #1 on May 24, 2019.
Building nTier Applications with Entity Framework Services (Part 2)David McCarter
Learn how to build real world nTier applications with the new Entity Framework and related services. Make sure to attend Part 1. This second part to the series will focus on using the Entity Framework in an nTier/ SOA world by separating out the different layers using T4 templates and using the new WCF Data Services to easily expose entity models via REST and to Silverlight clients. Lots of code!
Azure Digital Twins is a platform as a service (PaaS) offering that enables the creation of knowledge graphs based on digital models of entire environments. These environments could be buildings, factories, farms, energy networks, railways, stadiums, and more—even entire cities. These digital models can be used to gain insights that drive better products, optimized operations, reduced costs, and breakthrough customer experiences.
After nearly two years, Azure Digital Twins has been rewritten and it's off to a great start. In this session, we will see what it is for, see where it has changed, and see how to use it in our IoT strategy.
Towards Digital Twin standards following an open source approachFIWARE
Digital Twins are gaining momentum when designing smart solutions in different application domains. However, there is a lack of open standards that warrant interoperability and portability of solutions, avoiding vendor lock-in.
During the presentation, we will review major developments in this area, focused on the adoption of a standard API for accessing Digital Twin Data and Smart Data Models. We will review how a Digital Twin approach enables data integration at different levels: architecting vertical smart solutions, within smart organizations and across organizations. At all levels interfacing with IoT, BigData, AI/ML, Blockchain, or Robotics technologies.
A brief description to FIWARE Ecosystem and detailed one of the FIWARE IoT framework. Introduction to Orion Context Broker, IoT Agent - Ultralight 2.0 and Short Term Historic - Comet.
FIWARE: Managing Context Information at large scaleFermin Galan
This presentation describes how context management is implemented in FIWARE platform, base don Orion Context Broker GEri. Both basic usage of Context Broker and advanced topics are included.
Context-aware application development with FIWARE #CPBR8Fermin Galan
Context-aware application development with FIWARE, used in the #CPBR8 workshop. It includes basic and advanced Orion topics, along with usage examples.
We present various approaches to providing an API as part of an IoT product and discuss certain business models for monetizing it.
Centaur Technologies develops and markets end-to-end solutions for the Internet of Things, focused on the Industrial and Enterprise sectors.
FIWARE NGSI: Managing Context Information at Large ScaleFIWARE
FIWARE NGSI: Managing Context Information at Large Scale, by Fermín Galán.
Orion Context Broker developing team. 1st FIWARE Summit, Málaga, Dec. 13-15, 2016.
Building nTier Applications with Entity Framework Services (Part 2)David McCarter
Learn how to build real world nTier applications with the new Entity Framework and related services. This second part to the series will focus on using the Entity Framework in an nTier/ SOA world by separating out the different layers using T4 templates and using the new WCF Data Services to easily expose entity models via REST and to Silverlight clients.
Topics of this presentation:
- Fundamental concepts and principles.
- General architecture guidance.
- IoT applications component design.
- Cross-cutting issues.
This presentation by Andrii Antilikatorov (Consultant, Engineering, GlobalLogic) was delivered at GlobalLogic Kharkiv .NET TechTalk #1 on May 24, 2019.
Building nTier Applications with Entity Framework Services (Part 2)David McCarter
Learn how to build real world nTier applications with the new Entity Framework and related services. Make sure to attend Part 1. This second part to the series will focus on using the Entity Framework in an nTier/ SOA world by separating out the different layers using T4 templates and using the new WCF Data Services to easily expose entity models via REST and to Silverlight clients. Lots of code!
Azure Digital Twins is a platform as a service (PaaS) offering that enables the creation of knowledge graphs based on digital models of entire environments. These environments could be buildings, factories, farms, energy networks, railways, stadiums, and more—even entire cities. These digital models can be used to gain insights that drive better products, optimized operations, reduced costs, and breakthrough customer experiences.
After nearly two years, Azure Digital Twins has been rewritten and it's off to a great start. In this session, we will see what it is for, see where it has changed, and see how to use it in our IoT strategy.
Towards Digital Twin standards following an open source approachFIWARE
Digital Twins are gaining momentum when designing smart solutions in different application domains. However, there is a lack of open standards that warrant interoperability and portability of solutions, avoiding vendor lock-in.
During the presentation, we will review major developments in this area, focused on the adoption of a standard API for accessing Digital Twin Data and Smart Data Models. We will review how a Digital Twin approach enables data integration at different levels: architecting vertical smart solutions, within smart organizations and across organizations. At all levels interfacing with IoT, BigData, AI/ML, Blockchain, or Robotics technologies.
Fiware: the pillar of the Future Internet (Overview)Juanjo Hierro
Overview of the FIWARE program (http://fiware.org) devoted to create an open and sustainable ecosystem around the FIWARE platform. FIWARE provides OpenStack-based Cloud Hosting capabilities plus a rich library of Generic Enablers exporting standard APIs that ease development of Future Internet applications. You can experiment for free with the FIWARE technologies on the FIWARE Lab (http://lab.fiware.org), the meeting point where innovation takes place ... and don't miss the opportunity to get part of the 80 Million euros granted by the EC to those startups and SMEs that will materialize their innovative ideas using FIWARE !!
This approach will help to change the traditional approach of point-to-point communication in Manufacturing Execution Systems (MES) to using BizTalk server as a middleware to Integrate several systems
IoT Physical Servers and Cloud Offerings.pdfGVNSK Sravya
Introduction to Cloud Storage models
• Communication APIs
• Webserver-Web server for IoT
• Cloud for IoT
• Python web application framework
• Designing a RESTful web API.
Web based investment management system with multiple API integrations for managing Financial portfolios and statistics along with profit and loss management for investors
The platform architecture developed by the CPaaS.io project - both the overall system architecture as well as the two implementation architectures, one based on FIWARE and the other on u2 - as presented at the first year review meeting in Tokyo on October 5, 2017.
Disclaimer:
This document has been produced in the context of the CPaaS.io project which is jointly funded by the European Commission (grant agreement n° 723076) and NICT from Japan (management number 18302). All information provided in this document is provided "as is" and no guarantee or warranty is given that the information is fit for any particular purpose. The user thereof uses the information at its sole risk and liability. For the avoidance of all doubts, the European Commission and NICT have no liability in respect of this document, which is merely representing the view of the project consortium. This document is subject to change without notice.
Issuetrak API
An overview of methodology and processes within the Issuetrak API.
This document provides insight into the technical design goals and technical implementation within the upcoming Issuetrak API to provide stakeholders with background to evaluate the utility of the Issuetrak API especially when employed for enterprise-level data operations targeting the Issuetrak product platform.
Subscription based control system to automate management of events for robotsdbpublications
In Industrial Robots, a human machine interfaces (HMI) provide means to command and control robots for various purposes. Generally, this is implemented in a reactive manner by using polling (or pull) methodology to manage the events. This methodology restricts the possibilities of automation for reacting to events thus requires a human operator to poll and react to the events based on the skill of the human operator. This sometimes causes non-optimal or wrong responses. This paper proposes a design methodology to dynamically tap the events using a subscription based control system for event based management of robots. This design enables the client to be light-weight, cost effective and makes the responses more reliable. The paper also scrutinizes the alternative design options using semantic web for multirobot coordinative activities.
Industry 4.0: Building the Unified Namespace with Confluent, HiveMQ and Spark...confluent
Our talk will explore the transformative impact of integrating Confluent, HiveMQ, and SparkPlug in Industry 4.0, emphasizing the creation of a Unified Namespace.
In addition to the creation of a Unified Namespace, our webinar will also delve into Stream Governance and Scaling, highlighting how these aspects are crucial for managing complex data flows and ensuring robust, scalable IIoT-Platforms.
You will learn how to ensure data accuracy and reliability, expand your data processing capabilities, and optimize your data management processes.
Don't miss out on this opportunity to learn from industry experts and take your business to the next level.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf
Orion context broker webminar 2013 06-19
1. The FI-WARE Project – Core Platform of the
Future Internet
Orion Context Broker Webminar
Fermín Galán (fermin@tid.es), Francisco Romero (frb@tid.es)
June 2013
http://www.fi-ware.eu
2. The FI-WARE Project – Core Platform of the
Future Internet
IndexIndexIndexIndex
Introduction
Basic concepts
NGSI API
Orion Broker in the FI-WARE Architecture
Demo
01
02
03
04
05
4. The FI-WARE Project – Core Platform of the
Future Internet
Introduction
Orion Context Broker is an implementation of a context information
broker with persistent storage that can play the role of two Generic
Enablers (GE) within the FI-WARE platform
• Pub/Sub Context Broker GE
• Configuration Management GE
It implements OMA NGSI9/10 specification
• NGSI9 is about context information availability (i.e. sources of context
information) management
• NGSI10 is about context information itself
Orion Context Broker running as Pub/Sub Broker GE
• It implements both NGSI9 and NGSI10
Orion Context Broker running as Configuration Management GE
• It implements only NGSI9
• It implements registration forwarding
3
6. 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, …)
Orion Context Broker intermediates between context producers and context
consumers
5
Context
Broker
Applications
7. The FI-WARE Project – Core Platform of the
Future Internet
Context Elements (1/2)
Context Information in OMA NGSI is represented through data structures
called context elements which have associated:
• An EntityId and EntityType, 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 EntityId is a string, and can be used to designate “anything”, not
necessarely “things” in the “real world” but also application entities
6
Meta-data
• Name
• Type
• Value
Context Element attributes
• Name
• Type
• Value
Context Element
• EntityId
• EntityType
1 n 1 n
“has” “has”
8. The FI-WARE Project – Core Platform of the
Future Internet
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”, “geo-
location”, “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
7
9. The FI-WARE Project – Core Platform of the
Future Internet
Conceptual model: advantages
Not linked to a particular data/context representation formalism:
• Neither for transferring
• Nor storing
Can work with a standard IoT formats (SensorML) 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)
8
11. 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
(convenience operations)
• 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
10
12. The FI-WARE Project – Core Platform of the
Future Internet
Basic entities and operations (1)
Context Producers publish data/context elements by invoking the
updateContext operation on a Context (Publish/Subscribe) Broker.
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
queryContext operation on a Context Broker
11
Context Consumer
queryContext
Context Producer Context (Publish/Subscribe)
Broker
updateContext
13. The FI-WARE Project – Core Platform of the
Future Internet
Basic entities and operations (2)
Some Context Consumers can be subscribed to reception of data/context
elements which comply with certain conditions, using the subscribeContext
operation a ContextBroker exports. Such subscriptions may have a duration.
Subscribed consumers spontaneously receive data/context elements compliant
with that subscription through the notifyContext operation they export
Note that the Application which subscribes a particular Context Consumer may
or may not be the/a Context Consumer itself
12
Application
subscription_id = subscribeContext (consumer, expr, duration)
Context ConsumerContext (Publish/Subscribe) Broker
notifyContext (subscription_id, data/context)
14. The FI-WARE Project – Core Platform of the
Future Internet
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.
13
15. The FI-WARE Project – Core Platform of the
Future Internet
Context Broker Federation (1)
A Context Broker may be subscribed as Context Consumer on another
Context Broker
14
Application
sub_id_1 = subscribeContext (consumer1, expr1, duration1)
Context Consumer 1Context
Broker 2
notifyContext
Context Producer
Context Consumer 2
query
notifyContext
Application
sub_id_2 = subscribeContext (Context Broker GE 2, expr2, duration2)
Context
Broker 1
updateContext
queryContext
n2u
updateContext
directly,
In Release 3, CB will be able to
consume notifyContext directly,
making n2u unneeded
16. The FI-WARE Project – Core Platform of the
Future Internet
Context Broker Federation (2)
A Context Broker may be subscribed as Context Producer on another Context
Broker
15
Application
sub_id_1 = subscribeContext (consumer1, expr1, duration1)
Context
Broker 2
notifyContext
Context Producer
query
queryContext
Application
registerContext (Context Broker GE 2, what, duration2)
Context
Broker 1
updateContext
queryContext
Context Consumer 2
Context Consumer 1
17. The FI-WARE Project – Core Platform of the
Future Internet
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
16
Context Broker GE
Context
Producers
Context
Consumers
Producers port
subscription ports
subscriptions
update
query
notify
notify
update
query
18. The FI-WARE Project – Core Platform of the
Future Internet
Extended operations (1)
Context Brokers export the discoverContext operation enabling applications to
discover entities or even attributes and attribute domains that have been
registered in the system
17
Application 2
discoverContext
Application 1 Context (Publish/Subscribe)
Broker
registerContext
19. The FI-WARE Project – Core Platform of the
Future Internet
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
subscribeContextAvailability operation a ContextBroker 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
notifyContextAvailability operation they export
Note that the subscriber and subscribed applications may not be the same
18
application1
subscription_id = subscribeContextAvailability (application2, expr, duration)
application2Context Broker
notifyContextAvailability (subscription_id, updates)
20. The FI-WARE Project – Core Platform of the
Future Internet
Some hints about OMA NGSI specs
Operations are grouped into two major interfaces (not clear why ☺
• NGSI-10
› updateContext
› queryContext
› subscribeContext / unsubscribeContext / updateContextSubscription
› notifyContext
• NGSI-9
› registerContext
› discoverContextAvailability
› subscribeContextAvailability / unsubscribeContextAvailability /
updateContextAvailabilitySubscription
› notifyContextAvailability
19
21. The FI-WARE Project – Core Platform of the
Future Internet
04
Orion Broker in the FI-WARE
Architecture
22. The FI-WARE Project – Core Platform of the
Future Internet
FI-WARE NGSI for IoT
NGSI IoT
Adapter
Native NGSI
IoT Agent
Native NGSI
IoT Agent
Backend
Applications
FI-WARE NGSI-9/10
(entities: sensors)
(entities: things, sensors, other)
FI-WARE NGSI-9/10
Pub/Sub Broker GE
Backend
Device Management GE
IoT Broker ConfMan
23. The FI-WARE Project – Core Platform of the
Future Internet
FI-WARE Context/Data Management Platform
22
Context/Data Management Platform
Applications
FI-WARE NGSI-9/10
Processing/Analysis
Algorithms
Gathered data
is injected for
processing/ana
lysis
Distributed
Context Sources
Complex Event Processing -
CEP
(IBM’s PROTON)
BigData Analysis/Processing
(COSMOS)
Pub/Sub Context Broker
(Gathering / Publication)
Processed data is
injected for
processing/analysis
Data generated either
by CEP or BigData is
published
Gathered data
injected for CEP-like
processing
24. The FI-WARE Project – Core Platform of the
Future Internet
Context-based application (FI-WARE Live Demo App)
23
Pub/Sub Context
Broker
Wirecloud
(App Front End)
CEP
Location
NGSI IoT
Adapter
Device Management GE
Nodes, AMMS, Regulators,
Issues, Vans, Technitians
… SmartSantander
App Backend
25. The FI-WARE Project – Core Platform of the
Future Internet
Context Broker versions
Two versions
• R1:
› The one currently available
› Uses MySQL as persistence layer
› Mono-thread
› Uses a different name (“SAMSON Broker”)
• R2:
› Available by end of June
› Uses MongoDB as persistence layer
› Multi-thread
24
27. The FI-WARE Project – Core Platform of the
Future Internet
Demo environment
26
Port Listener
NGSI
queries
responses
data
10.95.26.5510.95.249.25
tcp/44444
tcp/1026
tcp/27017
Client
28. The FI-WARE Project – Core Platform of the
Future Internet
Additional Orion Context Broker Resources
Download from (PPP member only by the moment)
• https://forge.fi-ware.eu/frs/?group_id=23
Page in the FI-WARE catalog
• http://catalogue.fi-ware.eu/enablers/publishsubscribe-context-broker-samson-broker
FIWARE NGSI
• NGSI9: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI-
9_Open_RESTful_API_Specification_%28PRELIMINARY%29
• NGSI10: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_NGSI-
10_Open_RESTful_API_Specification_%28PRELIMINARY%29
Manuals
• Installation and Administration Guide: http://forge.fi-
ware.eu/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_GE_-_SAMSON_Broker_-
_Installation_and_Administration_Guide
• Users and Programmers Guide: http://forge.fi-
ware.eu/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_GE_-_SAMSON_Broker_-
_User_and_Programmer_Guide
27
30. The FI-WARE Project – Core Platform of the
Future Internet
Basic entities and operations (extra)
Some Context Producers may also export a queryContext 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 queryContext operation are
typically unknown “a priori”, Context Brokers export a registerContext
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
29
Application
registerContext (producer URI,
registration data, duration, registration_id)
Context Provider Context (Publish/Subscribe) Broker
queryContext
Context Consumer
queryContext
Not yet in Release 2. Planned for Release 3