ETSI GS CIM 054 V1.1.1 (2025-07)

Context Information Management (CIM); NGSI-LD Interoperability tests specification

DGS/CIM-0054

General Information

• Status: Not Published
• Technical Committee: CIM - cross-cutting Context Information Management
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 16-Jun-2025
• Completion Date: 30-Jul-2025

Standards Content (Sample)

GROUP SPECIFICATION
Context Information Management (CIM);
NGSI-LD Interoperability tests specification
Disclaimer
The present document has been produced and approved by the cross-cutting Context Information Management (CIM) ETSI
Industry Specification Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

2 ETSI GS CIM 054 V1.1.1 (2025-07)

Reference
DGS/CIM-0054
Keywords
API, IoT, NGSI-LD, testing
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3 ETSI GS CIM 054 V1.1.1 (2025-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 6
4 Prerequisites and Test Configurations . 7
4.1 Request body resources . 7
4.1.1 Entities . 7
4.1.1.0 Foreword . 7
4.1.1.1 OffStreetParking . 7
4.1.1.2 Vehicle . 11
4.1.2 Attribute Fragments . 12
4.1.3 CSourceRegistrations. 12
4.1.3.0 Foreword . 12
4.1.3.1 Inclusive . 13
4.1.3.2 Auxiliary . 14
4.1.3.3 Exclusive . 15
4.1.3.4 Redirect . 16
4.2 Test Configurations . 17
4.2.0 Foreword . 17
4.2.1 IOP_CNF_01: Three brokers with Inclusive and Exclusive . 18
4.2.2 IOP_CNF_02: Four brokers with Inclusive and Redirect . 18
4.2.3 IOP_CNF_03: Four brokers with Auxiliary and Inclusive . 19
4.2.4 IOP_CNF_04: Five brokers with all registration modes . 20
4.3 Initial Conditions . 22
4.3.1 Initial data . 22
4.3.1.1 IOP_INIT_COND_DATA_01: No data in any brokers . 22
4.3.1.2 IOP_INIT_COND_DATA_02: Data in the local broker . 22
4.3.1.3 IOP_INIT_COND_DATA_03: Data in brokers that are a leaf . 22
4.3.1.4 IOP_INIT_COND_DATA_04: Data in all brokers . 22
4.3.2 @context file. 22
4.3.2.1 IOP_INIT_COND_CONTEXT_01: Core context only . 22
4.3.2.2 IOP_INIT_COND_CONTEXT_02: User context . 22
5 Interoperability Test Structure (ITS) . 23
5.1 Test Case Structure . 23
6 Test Descriptions . 23
6.0 Foreword . 23
6.1 Create Entity . 24
6.1.1 IOP_CNF_01 . 24
6.1.1.1 Create OffStreetParking:1 . 24
6.1.1.2 Create OffStreetParking:2 . 24
6.1.2 IOP_CNF_02 . 25
6.1.2.1 Create OffStreetParking:1 . 25
6.1.2.2 Create OffStreetParking:2 . 25
6.1.3 IOP_CNF_03 . 26
ETSI
4 ETSI GS CIM 054 V1.1.1 (2025-07)
6.1.3.1 Create OffStreetParking:1 . 26
6.1.3.2 Create Partial OffStreetParking:1 . 26
6.1.4 IOP_CNF_04 . 27
6.1.4.1 Create OffStreetParking:1 . 27
6.1.4.2 Create OffStreetParking:2 . 27
6.2 Retrieve Entity . 28
6.2.1 IOP_CNF_01 . 28
6.2.1.1 Retrieve OffStreetParking:1 . 28
6.2.1.2 Retrieve OffStreetParking:2 . 29
6.2.2 IOP_CNF_02 . 29
6.2.2.1 Retrieve OffStreetParking:1 . 29
6.2.2.2 Retrieve location from OffStreetParking:1 . 30
6.2.3 IOP_CNF_03 . 31
6.2.3.1 Retrieve OffStreetParking:1 . 31
6.2.3.2 Retrieve location from OffStreetParking:1 . 31
6.2.4 IOP_CNF_04 . 32
6.2.4.1 Retrieve OffStreetParking:1 . 32
6.2.4.2 Retrieve location from OffStreetParking:1 . 33
6.3 Query Entities . 34
6.3.1 IOP_CNF_01 . 34
6.3.1.1 Query Entities with type OffstreetParking (GET) . 34
6.3.1.2 Query Entities with type OffstreetParking (POST) . 35
6.3.2 IOP_CNF_02 . 36
6.3.2.1 Query Entities with type OffstreetParking (GET) . 36
6.3.2.2 Query the "location" Property from Entities having type OffstreetParking or Vehicle (GET) . 37
6.3.3 IOP_CNF_03 . 38
6.3.3.1 Query Entities with type OffstreetParking (GET) . 38
6.3.3.2 Query the "location" Property from Entities having type OffstreetParking or Vehicle (GET) . 39
6.3.4 IOP_CNF_04 . 40
6.3.4.1 Query Entities of type OffStreetParking (GET) . 40
6.3.4.2 Query Entities of type OffS treetParking (POST) . 41
Annex A (informative): Change history . 42
History . 43

ETSI
5 ETSI GS CIM 054 V1.1.1 (2025-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Group Specification (GS) has been produced by ETSI Industry Specification Group (ISG) cross-cutting Context
Information Management (CIM).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Several NGSI-LD Context Brokers and related software modules, such as data ingestion, event processing, and
visualization, are being developed globally, reflecting the widespread adoption of NGSI-LD standards. With multiple
open-source implementations available, establishing comprehensive interoperability test cases is essential to ensure that
different brokers, even from various vendors, can operate together seamlessly. While these tests do not directly validate
the NGSI-LD specification, these tests may also be used to demonstrate whether the implementations can interoperate
effectively and whether the NGSI-LD specification should be revised to avoid ambiguity (if any). The results can be
applied in specific scenarios to highlight system compatibility, showcase cross-vendor collaboration, and provide
valuable feedback for improving overall implementation quality.

ETSI
6 ETSI GS CIM 054 V1.1.1 (2025-07)
1 Scope
The present document extends the draft interoperability test descriptions agreed with ISG CIM.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI GS CIM 009 (V1.8.1): "Context Information Management (CIM); NGSI-LD API".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
Not applicable.
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
GS Group Specification
SUT System Under Test
ETSI
7 ETSI GS CIM 054 V1.1.1 (2025-07)
4 Prerequisites and Test Configurations
4.1 Request body resources
4.1.1 Entities
4.1.1.0 Foreword
The following clauses provide a detailed description of the specific Entities that shall be employed to perform the
interoperability tests outlined in clause 6 of the present document. Each clause contains the Entities of the given "type".
4.1.1.1 OffStreetParking
{
"id": "urn:ngsi-ld:OffStreetParking:1",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown One"
},
"availableSpotsNumber": {
"type": "Property",
"value": 121,
"observedAt": "2017-07-29T12:05:02Z",
"reliability": {
"type": "Property",
"value": 0.7
}
},
"totalSpotsNumber": {
"type": "Property",
"value": 200
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
-8.5,
41.2
],
"observedAt": "2021-04-04T11:41:00Z"
}
}
}
Figure 4.1.1.1-1: Full version of OffstreetParking:1
ETSI
8 ETSI GS CIM 054 V1.1.1 (2025-07)
{
"id": "urn:ngsi-ld:OffStreetParking:1",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown One"
},
"availableSpotsNumber": {
"type": "Property",
"value": 169,
"observedAt": "2017-07-29T12:10:02Z",
"reliability": {
"type": "Property",
"value": 0.3
}
},
"totalSpotsNumber": {
"type": "Property",
"value": 200
}
}
Figure 4.1.1.1-2: OffstreetParking:1 without location
{
"id": "urn:ngsi-ld:OffStreetParking:1",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown One"
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
-8.9,
42.2
] ,
"observedAt": "2021-04-04T11:45:00Z"
}
}
}
Figure 4.1.1.1-3: OffstreetParking:1 with location and name only
ETSI
9 ETSI GS CIM 054 V1.1.1 (2025-07)
{
"id": "urn:ngsi-ld:OffStreetParking:2",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown Two"
},
"availableSpotsNumber": {
"type": "Property",
"value": 112,
"observedAt": "2017-07-29T12:05:02Z",
"reliability": {
"type": "Property",
"value": 0.4
}
},
"totalSpotsNumber": {
"type": "Property",
"value": 150
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
-8.45,
41.2
]
}
}
}
Figure 4.1.1.1-4: Full version of OffstreetParking:2
{
"id": "urn:ngsi-ld:OffStreetParking:2",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown Two"
},
"availableSpotsNumber": {
"type": "Property",
"value": 87,
"observedAt": "2017-07-29T12:10:02Z",
"reliability": {
"type": "Property",
"value": 0.55
}
},
"totalSpotsNumber": {
"type": "Property",
"value": 150
}
}
Figure 4.1.1.1-5: OffstreetParking:2 without location
ETSI
10 ETSI GS CIM 054 V1.1.1 (2025-07)
{
"id": "urn:ngsi-ld:OffStreetParking:2",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown Two"
},
"availableSpotsNumber": {
"type": "Property",
"value": 92,
"observedAt": "2017-07-30T12:10:02Z",
"reliability": {
"type": "Property",
"value": 0.56
}
}
}
Figure 4.1.1.1-6: OffstreetParking:2 without location and totalSpotsNumber
{
"id": "urn:ngsi-ld:OffStreetParking:2",
"type": "OffStreetParking",
"name": {
"type": "Property",
"value": "Downtown Two"
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
-8.46,
41.25
] ,
"observedAt": "2021-04-04T11:46:00Z"
}
}
}
Figure 4.1.1.1-7: OffstreetParking:2 with location and name only
ETSI
11 ETSI GS CIM 054 V1.1.1 (2025-07)
4.1.1.2 Vehicle
{
"id": "urn:ngsi-ld:Vehicle:1",
"type": "Vehicle",
"brandName": {
"type": "Property",
"value": "Brand1"
},
"speed": {
"type": "Property",
"value": 0,
"source": {
"type": "Property",
"value": "Speedometer"
}
},
"isParked": {
"type": "Relationship",
"object": "urn:ngsi-ld:OffStreetParking:1",
"observedAt": "2017-07-29T12:00:04Z"
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
-8.45,
41.2
]
}
}
}
Figure 4.1.1.2-1: Full version of Vehicle:1
{
"id": "urn:ngsi-ld:Vehicle:1",
"type": "Vehicle",
"brandName": {
"type": "Property",
"value": "Brand1"
},
"speed": {
"type": "Property",
"value": 0,
"source": {
"type": "Property",
"value": "Speedometer"
}
},
"isParked": {
"type": "Relationship",
"object": "urn:ngsi-ld:OffStreetParking:1",
"observedAt": "2017-07-29T12:00:04Z"
},
}
Figure 4.1.1.2-2: Vehicle:1 without location
ETSI
12 ETSI GS CIM 054 V1.1.1 (2025-07)
{
"id": "urn:ngsi-ld:Vehicle:2",
"type": "Vehicle",
"brandName": {
"type": "Property",
"value": "Brand2"
},
"speed": {
"type": "Property",
"value": 5,
"source": {
"type": "Property",
"value": "Speedometer"
}
},
"isParked": {
"type": "Relationship",
"object": "urn:ngsi-ld:OffStreetParking:2",
"observedAt": "2017-07-30T12:00:04Z"
},
"location": {
"type": "GeoProperty",
"value": {
"type": "Point",
"coordinates": [
-9.45,
40.2
]
}
}
}
Figure 4.1.1.2-3: Full version of Vehicle:2
{
"id": "urn:ngsi-ld:Vehicle:2",
"type": "Vehicle",
"brandName": {
"type": "Property",
"value": "Brand2"
},
"speed": {
"type": "Property",
"value": 10,
"source": {
"type": "Property",
"value": "Speedometer"
}
},
"isParked": {
"type": "Relationship",
"object": "urn:ngsi-ld:OffStreetParking:2",
"observedAt": "2017-07-28T12:00:04Z"
},
}
Figure 4.1.1.2-4: Vehicle:2 without location
4.1.2 Attribute Fragments
None.
4.1.3 CSourceRegistrations
4.1.3.0 Foreword
The following clauses provide a detailed description of the specific CSourceRegistrations that shall be employed to
perform the interoperability tests outlined in clause 6 of the present document. Each clause contains the
CSourceRegistrations of the given "mode".
ETSI
13 ETSI GS CIM 054 V1.1.1 (2025-07)
NOTE: In all subsequential clauses, the "endpoint" member is represented containing the placeholder text "xxx".
The text should be replaced with a valid endpoint URL during the set-up of a test configuration.
4.1.3.1 Inclusive
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Inclusive:1",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking"
}
],
}
],
"mode": "inclusive",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.1-1: Inclusive:1 on OffStreetParking entities, only type
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Inclusive:2",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking"
}
],
"propertyNames": [
"availableSpotsNumber",
"totalSpotsNumber"
]
}
],
"mode": "inclusive",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.1-2: Inclusive:2 on OffStreetParking entities, type and attributes
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Inclusive:3",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "Vehicle"
}
]
}
],
"mode": "inclusive",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.1-3: Inclusive:3 on Vehicle entities, only type
ETSI
14 ETSI GS CIM 054 V1.1.1 (2025-07)
4.1.3.2 Auxiliary
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Auxiliary:1",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking"
}
]
}
],
"mode": "auxiliary",
"endpoint": "xxx"
}
Figure 4.1.3.2-1: Auxiliary:1 on OffStreetParking entities, only type
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Auxiliary:2",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking"
}
],
"propertyNames": [
"availableSpotsNumber",
"totalSpotsNumber"
]
}
],
"mode": "auxiliary",
"endpoint": "xxx"
}
Figure 4.1.3.2-2: Auxiliary:2 on OffStreetParking entities, only type
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Auxiliary:3",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "Vehicle"
}
]
}
],
"mode": "auxiliary",
"endpoint": "xxx"
}
Figure 4.1.3.2-3: Auxiliary:3 on Vehicle entities, only type
ETSI
15 ETSI GS CIM 054 V1.1.1 (2025-07)
4.1.3.3 Exclusive
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Exclusive:1",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"id": "urn:ngsi-ld:OffStreetParking:2",
"type": "OffStreetParking"
}
],
"propertyNames": [
"totalSpotsNumber"
]
}
],
"mode": "exclusive",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.3-1: Exclusive:1 on OffStreetParking:2 and totalSpotsNumber
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Exclusive:2",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"id": "urn:ngsi-ld:OffStreetParking:2",
"type": "OffStreetParking"
}
],
"propertyNames": [
"location"
]
}
],
"mode": "exclusive",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.3-2: Exclusive:2 on OffStreetParking:2 and location
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Exclusive:3",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"id": "urn:ngsi-ld:OffStreetParking:1",
"type": "OffStreetParking"
}
],
"propertyNames": [
"location"
]
}
],
"mode": "exclusive",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.3-3: Exclusive:3 on OffStreetParking:1 and location
ETSI
16 ETSI GS CIM 054 V1.1.1 (2025-07)
4.1.3.4 Redirect
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Redirect:1",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking"
}
]
}
],
"mode": "redirect",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.4-1: Redirect:1 on OffStreetParking entities, only type
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Redirect:2",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking"
}
],
"propertyNames": [
"location"
]
}
],
"mode": "redirect",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.4-2: Redirect:2 on OffStreetParking entities and location
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Redirect:3",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "OffStreetParking",
"id": "urn:ngsi-ld:OffStreetParking:2"
}
],
"propertyNames": [
"location"
]
}
],
"mode": "redirect",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.4-3: Redirect:3 on OffStreetParking:2 and location
ETSI
17 ETSI GS CIM 054 V1.1.1 (2025-07)
{
"id": "urn:ngsi-ld:ContextSourceRegistration:Redirect:4",
"type": "ContextSourceRegistration",
"information": [
{
"entities": [
{
"type": "Vehicle",
"id": "urn:ngsi-ld:Vehicle:2"
}
],
"propertyNames": [
"location"
]
}
],
"mode": "redirect",
"operations": ["redirectionOps"],
"endpoint": "xxx"
}
Figure 4.1.3.4-4: Redirect:4 on Vehicle:2 and location
4.2 Test Configurations
4.2.0 Foreword
The following clauses provide a detailed description of the specific test configurations that shall be employed to
perform the interoperability tests outlined in clause 6 of the present document. Each clause includes a diagram
illustrating the topology of the configuration, a formal description that explains the rationale for selecting the given
configuration, and a comprehensive list of the Context Source Registrations required when setting up the configuration.

Figure 4.2.0-1: Legend
Figure 4.2.0-1 illustrates the legend for each element utilized in the diagrams of the configurations described in the
present document. As depicted, registrations are represented as arcs, characterized by a color and a label that denote a
specific Context Source Registration mode. Nodes are depicted as circles. Additionally, a dashed line is employed to
indicate interactions with a specific node originating from an element external to the System Under Test (SUT),
typically a client.
ETSI
18 ETSI GS CIM 054 V1.1.1 (2025-07)
4.2.1 IOP_CNF_01: Three brokers with Inclusive and Exclusive

Figure 4.2.1-1: IOP_CNF_01 topology with registrations
Figure 4.2.1-1 shows the topology for IOP_CNF_01 which is one of the simplest possible setups, consisting of only
three brokers. It is suitable for both Provision and Consumption operations, testing a scenario where broker b2 mirrors
most of the information contained in b1 and b3 contains some exclusive data that cannot be stored in b1.
When this configuration is utilized, the following registrations shall be established:
• From b1 to b2, Inclusive
• From b1 to b3, Exclusive
Considering the above registrations, the following restrictions are to be expected:
• b1 cannot store any input data that matches against the Exclusive registration
The following behaviours are to be expected when a Consumption operation is triggered on b1:
• b1 searches locally when the input data does not match against the Exclusive registration established with b3
• b2 is contacted by b1when the input data matches against the Inclusive registration
• b3 is the only broker contacted by b1 when the input data matches against the Exclusive registration
The following behaviours are to be expected when a Provision operation is triggered on b1:
• b1 writes locally when the input data does not match against the Exclusive registration established with b3
• b2 is contacted by b1 when the input data matches against the Inclusive registration
• b3 is the only broker contacted by b1 when the input data matches against the Exclusive registration
4.2.2 IOP_CNF_02: Four brokers with Inclusive and Redirect

Figure 4.2.2-1: IOP_CNF_02 topology with registrations
Figure 4.2.2-1 shows the topology for IOP_CNF_02 which is a variant of IOP_CNF_01 with four brokers and Redirect
registrations. It leverages the same approach, but it allows for more flexible tests. This is justified by the fact that
Redirect registrations do not require to specify an Entity id, but can work with Entity types.
ETSI
19 ETSI GS CIM 054 V1.1.1 (2025-07)
When this configuration is utilized, the following registrations shall be established:
• From b1 to b2, Inclusive
• From b1 to b3, Redirect
• From b1 to b4, Redirect
Considering the above registrations, the following restrictions are to be expected:
• b1 cannot store any input data that matches against the Redirect registration established with b3
• b1 cannot store any input data that matches against the Redirect registration established with b4
The following behaviours are to be expected when a Consumption operation is triggered on b1:
• b1 searches locally when the input data does not match against:
- the Redirect registration established with b3
- the Redirect registration established with b4
• b2 is contacted by b1when the input data matches against the Inclusive registration
• b3 is contacted by b1 when the input data matches against the Redirect registration
• b4 is contacted by b1 when the input data matches against the Redirect registration
The following behaviours are to be expected when a Provision operation is triggered on b1:
• b1 writes locally when the input data does not match against:
- the Redirect registration established with b3
- the Redirect registration established with b4
• b2 is contacted by b1when the input data matches against the Inclusive registration
• b3 is contacted by b1 when the input data matches against the Redirect registration
• b4 is contacted by b1 when the input data matches against the Redirect registration
4.2.3 IOP_CNF_03: Four brokers with Auxiliary and Inclusive

Figure 4.2.3-1: IOP_CNF_03 topology with registrations
Figure 4.2.3-1 shows the topology for IOP_CNF_03 which is a variant of IOP_CNF_02 with Auxiliary and Inclusive
registrations. Considering the presence of an Auxiliary registration, this configuration is very suitable for testing
Consumption operations. Provision operations can be tested as well, but the focus shifts towards a more "negative"
approach where the objective is checking that an operation was not performed when specific requirements are met.
ETSI
20 ETSI GS CIM 054 V1.1.1 (2025-07)
When this configuration is utilized, the following registrations shall be established:
• From b1 to b2, Auxiliary
• From b1 to b3, Inclusive
• From b1 to b4, Inclusive
The following behaviours are to be expected when a Consumption operation is triggered on b1:
• b1 searches locally
• b2 is contacted by b1 when the input data matches against the Auxiliary registration, but its data is retained
only when all following points are met:
- Data is not found locally within b1
- Data is not returned by b3
- Data is not returned by b4
• b3 is contacted by b1 when the input data matches against the Inclusive registration
• b4 is contacted by b1 when the input data matches against the Inclusive registration
The following behaviours are to be expected when a Provision operation is triggered on b1:
• b1 writes locally
• b2 is not contacted by b1
• b3 is contacted by b1 when the input data matches against the Inclusive registration
• b4 is contacted by b1 when the input data matches against the Inclusive registration
4.2.4 IOP_CNF_04: Five brokers with all registration modes

Figure 4.2.4-1: IOP_CNF_04 topology with registrations
Figure 4.2.4-1 shows the topology for IOP_CNF_04. This configuration contains all registration modes, enabling the
execution of complex and comprehensive tests, particularly for evaluating Consumption operations. However, it is less
suitable for Provision operations due to the presence of the Auxiliary registration from b1 to b2. In the case of a
Provision request, b1 will not contact b2, which implies that nodes b2, b4, and potentially b5 (depending on the specific
request) will remain unaffected.
When this configuration is utilized, the following registrations shall be established:
• From b1 to b2, Auxiliary
• From b2 to b4, Redirect
• From b2 to b5, Redirect
• From b1 to b3, Inclusive
• From b3 to b5, Exclusive
ETSI
21 ETSI GS CIM 054 V1.1.1 (2025-07)
Considering the above registrations, the following restrictions are to be expected:
• b2 cannot store any input data that matches against the Redirect registration established with b4
• b2 cannot store any input data that matches against the Redirect registration established with b5
• b3 cannot store any input data that matches against the Exclusive registration established with b5
The following behaviours are to be expected when a Consumption operation is triggered on b1:
• b1 searches locally
• b2 is contacted by b1 when the input data matches against the Auxiliary registration, but its data is retained
only when all following points are met:
- Data is not found locally within b1
- Data is not returned by b3
• When b2 is contacted by b1, the following behaviours are expected:
- b2 searches locally when the input data does not match against:
 the Redirect registration established with b4
 the Redirect registration established with b5
- b4 is contacted by b2 when the input data matches against the Redirect registration
- b5 is contacted by b2 when the input data matches against the Redirect registration
• b3 is contacted by b1 when the input data matches against the Inclusive registration
• When
...