The FIWARE Summit held in Vienna on June 12-13, 2023, focused on the evolution of NGSI-LD standards and their application in digital twins and smart cities. Discussions included the NGSI-LD roadmap, uptake of new features like linked entity retrieval, and the significance of distributed operations for integrating real-world assets. Key stakeholders from various regions showcased collaborations aimed at enhancing interoperability in digital ecosystems.

1. Vienna, Austria
12-13 June, 2023
#FIWARESummit
From Data
to Value
OPEN SOURCE
OPEN STANDARDS
OPEN COMMUNITY
NGSI-LD Roadmap and
New Features

2. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Table of Content
▪ NGSI Evolution – from OMA NGSI to NGSI-LD in ETSI ISG CIM
▪ ETSI ISG CIM/NGSI-LD Roadmap
▪ NGSI-LD Uptake
▪ New NGSI-LD Features and Relevance for Digital Twins
• Distributed Operation Support [v1.6.1, v1.7.1]
□ central, distributed, federated system architectures
□ flexible registrations (operations supported, registration modes)
• NGSI-LD Graph Retrieval (to support Industry 4.0 AAS model) [v1.8.1]
2

3. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
NGSI-LD – Evolution and specification in ETSI ISG CIM
• European Telecommunications Standards Institute (ETSI)
• ETSI produces globally-applicable standards for Information and Communications Technologies (ICT)
• It is officially recognized by the European Commission as a European Standards Organization
• Industry Specification Groups (ISG) allow participation of non-ETSI-members
• ETSI ISG for cross-cutting Context Information Management (ETSI ISG CIM)
• Established in 2017 – extended until 2025
• Currently about 30 supporting organizations
• Evolution of NGSI Context Interfaces NGSI-LD
• Current Specification: NGSI-LDv1.7.1 (June 2023):
https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf
Context API
in Open Mobile
Alliance (OMA)
2010 OMA NGSI
FIWARE project develops binding
and evolves OMA NGSI
(not standardized)
2012-2016: NGSI v1/v2
Evolution as ETSI
ISG CIM specification
based on JSON-LD
2019: NGSI-LD
3

4. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
NGSI-LD Roadmap (streams)
GR-007 V1.2
NGSI-LD SECURITY
GR-002 V1.1
NGSI-LD Use Cases
GR-002 Use
Cases v1.2
2019-2022 2023 2024
GS-009 NGSI-LD API v1.7
INFO
MODEL
API
&
ARCH
INTER-
WORKING
GS-006 V1.1
NGSI-LD INFO MODEL
NGSI-LD Status Document
GR-007 V1.1
NGSI-LD SECURITY
GS-006 NGSI-LD INFO
MODEL v1.2
GR-024 NGSI-LD
ARCHITECTURE
GR-017 V1.1
Digital Twins
GS-009 V1.6
NGSI-LD API
GR-021 V1.1 External Info Models
GR-038 NGSI-LD & YANG
GR-023 NGSI-LD
Adoptions
GR-022 V1.1 NGSI-LD /
oneM2M Interworking Proxy
GR-020 V1.1 SmartCity
Guidelines
GS-019 V1.1 Provenance
GR-018 V1.1
Trust Chains
USAGE
Security
API
Info Model
Concepts
Technology
Usage
Testing
GR-030 Validation of NGSI-LD test platform
GR-029
Architecture
GR-010 Interworking
GS-012v2
Test Suite v2
Test Suite v1
GS-009 NGSI-LD API v1.8
GS-013v2 GS-014v2GS-015v2
GS-027 GS-028
NGSI-LD Status Document
GS-008 NGSI-LD
Primer 1.2
publishing date
expected publishing date

5. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
NGSI-LD Uptake and Collaborations
▪ NGSI-LD Uptake and Collaborations
Europe
Connecting Europe
Facility (CEF)
Context Broker
 NGSI-LD
Worldwide
Open Agile Smart
Cities (OASC)
Minimum Interoperability
Mechanism  NGSI-LD
India
India Urban Data
Exchange (IUDX)
IUDX Resource Server
 NGSI-LD
South Korea
CityHub Platform
Data Service Broker
 NGSI-LD
Japan
Smart City SIP
Interface Option
 NGSI-LD
Worldwide
Smart Data Models
Collaboration
FIWARE/tmforum/OASC, defining
NGSI(-LD) data models
Worldwide
FIWARE
Evolution towards NGSI-LD as
successor of NGSIv2 core API!

6. New NGSI-LD Features
Current Version NGSI-LD v1.7.1:
https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf
Draft Version for Public Comments NGSI-LD v1.8.1:
https://docbox.etsi.org/ISG/CIM/Open/drafts/ETSI_GS_CIM_009_NGSI-LD_API_DRAFTv1.8-for-PUBLIC-
COMMENT.pdf

7. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Architectures: standardized multi-architecture support
Context
Source
Context
Producer
Context
Source
Context
Consumer
Context
Consumer
Context
Consumer
Query
Subscribe/
Notify
Query
Subscribe/
Notify
Discover
Subscribe/
Notify
Discovery
Register
Discover
Subscribe/
Notify
Discovery
Registry
Server
Broker
Context
Producer
Create
Update
Delete
Enables Evolution
of Deployments
e.g. Smart
City/Smart Country
 future-proof
Central
Deployment
Distributed
Deployment
Federated
Deployment
7

8. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Broker
Federation
Broker
Broker
Broker Broker
Federation: Applications get
transparent access to underlying
information sources
NGSI-LD Federation
8

9. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Distributed Operation – Registrations [NGSI-LDv1.6.1]
• Not all registered NGSI-LD components implement the
full set of NGSI-LD operations, thus the operations
supported by the Context Source need to be specified
• list of individual operations or
• predefined groups like federationOps (default),
updateOps (e.g. for actuation), retrieveOps (e.g.
sensors)
• Depending on assumptions, attributes of the same
Entity may appear in different places or should be
exclusive to one component
• inclusive (default, entity information can be local and in
any registered source)
• auxilliary (entity information is only used, if other
(primary)is not available – e.g. provide a backup if primary
broker is not available)
• exclusive (entity/attribute information can only be in
registered source, e.g. for actuation)
• redirect (entity can only be in one or more registered
sources, e.g. to organize entities – cars in one broker,
bicycles in another)

10. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Distributed Operation - Relevance for Digital Twins
▪ Digital Twins need to interact with real-world assets
• Get information from the real-world asset
• Change the situation of real-world asset
▪ Distributed operations enable the direct integration with real-world assets through
system adapters (e.g. IoT Agents)
• System adapters for sensors only need to implement retrieveOps for highly volatile or
costly (e.g. battery status, where permanently checking would drain the battery)
• System adapters for actuators only need to implement updateOps and register as
exclusive, making sure that an update will actually trigger an actuation
▪ Distributed operations enable the distributed realization of Digital Twins, e.g.
• Local control loops can be implemented on the edge where low latency is required
• Complex simulations for predictions requiring large models can be executed in the cloud
• Applications can access all information related to Digital Twin through federation broker

11. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Asset Administration Shell (AAS) Model
▪ The Asset Administration Shell (AAS) is the
digital representation of assets in the Industrie
4.0
▪ Thus, “the Asset Administration Shell is the
implementation of the Digital Twin for
Industrie 4.0” (Plattform Industrie 4.0)
▪ The AAS has the concept of Submodel, i.e. has
a level of substructuring properties
▪ It is required to be able to access the whole
AAS, as well as individual submodels
Under CC BY 4.0 License - Cavalieri, Salvatore & Salafia, Marco. (2020). Insights into
Mapping Solutions Based on OPC UA Information Model Applied to the Industry 4.0
Asset Administration Shell. Computers. 9. 28. 10.3390/computers9020028. Figure 1.

12. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Supporting “Submodels” in NGSI-LD, as needed for AAS
▪ Goal: Enable representation of AAS in NGSI-LD
▪ Problem:
• Submodel concept does not exist and is difficult to add as a separate concept
▪ Submodels can be represented as separate Entities
• Enables AAS (entity) that has relationships to each submodel (separate entities)
• Submodels can be separately retrieved
▪ Problem:
• when retrieving AAS with the current NGSI-LD API only the identifiers of the repspective
submodels are provided, which then would have to be retrieved sepeartely –
not acceptable

13. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Retrieving Hierarchically Structured Information, not just for AAS
Example
I hold several pieces of land type:AgriParcel
▪ Each AgriParcel has some of its own attributes, e.g.
soilType, cropType
▪ Each AgriParcel also has its own related
weather station (i.e. Relationship to an entity
type:WeatherObserved) displaying values
holding to current observed weather conditions
▪ We also require a weather forecast (i.e.
Relationship to an entity type:WeatherForecast)
which covers a wider area encompassing multiple
AgriParcels for a predicted weather
conditions.
▪ Note: WeatherObserved and WeatherForecast share
similar attributes

14. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Solution: NGSI-LD Linked Entity Retrieval (NGSI-LD v1.8.1)
▪ NGSI-LD models graph of Entities through
explicit relationships (e.g. owns / livesAt)
▪ Up to now, retrieval can only be done
step-by-step
▪ From v1.8 retrieval can be done for a
whole subgraph (default: expand one
level)
▪ With “join=inline”, they can be
represented in a hierarchical structure
▪ With “join=flat”, the relationships stay as
they are, but the target entities are
returned in the result lists
temperature
humidity
windSpeed
…
prediction
observation
soilType
cropType
temperature
humidity
{
"id": "urn:ngsi-ld:AgriParcel:001",
"type": “AgriParcel",
"soilType": "Loamy",
"prediction": {
"type": “Relationship",
"object": "urn:ngsi-ld:WeatherForecast:XXX",
"objectType": “WeatherForecast"
},
“observation": {
"type": “Relationship",
"object": "urn:ngsi-ld:WeatherObserved:001",
"objectType": “WeatherObserved“
}
} Normalized Representation
{
"id": "urn:ngsi-ld:AgriParcel:001",
"type": “AgriParcel",
"soilType": "Loamy",
"prediction": {
"object": "urn:ngsi-ld:WeatherForecast:XXX",
"objectType": “WeatherForecast",
"entity": {
"id": "urn:ngsi-ld:WeatherForecast:XXX ",
"type": “WeatherForecast",
"humidity": {
"type": "Property", "value": 98, "unitCode: "PCT"
},
"temperature": {
"type": "Property", "value": 30, "unitCode: "CEL"
},
"windSpeed": {
"type": "Property", "value": 3, "unitCode: "MPH"
}
}},
“observation": {
"object": "urn:ngsi-ld:WeatherObserved:001",
"objectType": “WeatherObserved",
"entity": {
"id": "urn:ngsi-ld:WeatherObserved:001",
"type": “WeatherObserved",
… Concise Representation

15. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Solution: NGSI-LD Linked Entity Retrieval (NGSI-LD v1.8.1)
join=flat
15
[
{
"id": "urn:ngsi-ld:AgriParcel:001",
"type": "AgriParcel",
"soilType": {"type": "Property", "value": "Loamy"},
"cropType": {"type": "Relationship", "object": "urn:ngsi-ld:AgriCrop:BuckWheat"},
"location": {"type": "GeoProperty", "value": { "type": "Point", "coords": [13, 58]}},
"prediction": {
"type": "Relationship", "object": "urn:ngsi-ld:WeatherForecast:XXX",
“objectType":"WeatherForecast",
},
"observation": {
"type": "Relationship", "object": "urn:ngsi-ld:WeatherObserved:001",
“objectType":["WeatherForecast"],
"providedBy": {
"type": "Relationship", "object: "urn:ngsi-ld:Device:ABC"
},
}
},
{
"id": "urn:ngsi-ld:WeatherForecast:XXX"
"type": "WeatherForecast",
"humidity": {"type": "Property", "value": 98, "unitCode: "P1"},
"temperature": {"type": "Property", "value": 30, "unitCode: "CEL"},
"windSpeed": {"type": "Property", "value": 3, "unitCode: "MTS"},
"description": {"type": "Property", "value": "Rain"}
},
{
"id": "urn:ngsi-ld:WeatherObserved:001",
"type": "WeatherObserved",
"humidity": {"type": "Property", "value": 80, "unitCode: "P1"},
"temperature": {"type": "Property", "value": 30, "unitCode: "CEL"},
"windSpeed": {"type": "Property", "value": 3, "unitCode: "MTS"}
}
]
join=flat returns the
entity and all fully
expanded sub-entities as
a single flattened array
It would therefore be possible to
serialize the whole entity and its
dependencies into a format
which could be upserted directly
using the batch endpoints
Normalized Representation

16. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
NGSI-LD Linked Entity Retrieval for AAS Model
Under CC BY 4.0 License - Cavalieri, Salvatore & Salafia, Marco. (2020). Insights into
Mapping Solutions Based on OPC UA Information Model Applied to the Industry 4.0
Asset Administration Shell. Computers. 9. 28. 10.3390/computers9020028. Figure 1.
{
"id": "<AAS Identification>",
"assetId": "<Asset Identification>"
"type": “AAS",
"Submodel1": {
"object": "urn:<AAS-NNN>:Submodel1",
"objectType": “EnergyEfficiency",
"entity": {
"id": "urn:<AAS-NNN>:Submodel1",
"type": “EnergyEfficiency",
"Property1.1": {
"type": "Property",
"value": {
“Property1.1.1”: “…”,
"Property1.1.2”: “…”,
},
}},
"Submodel2": {
"object": "urn:<AAS-NNN>:Submodel2",
"objectType": "PositioningMode",
"entity": {
"id": "urn:<AAS-NNN>:Submodel2",
"type": "PositioningMode",
"Property2.1": {
…

17. Vienna, 12-13 June, 2023 | #FIWARESummit www.fiware.org
Hosting Partner Keystone Sponsors
Media Partners
Find Us On Stay up to date Be certified and featured
JOIN OUR NEWSLETTER

18. Vienna, Austria
12-13 June, 2023
#FIWARESummit
Thanks!