ETSI GS CIM 013 V3.1.1 (2025-07)

Context Information Management (CIM); NGSI-LD Test Purposes Descriptions

RGS/CIM-0013v311

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 Test Purposes Descriptions
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 013 V3.1.1 (2025-07)

Reference
RGS/CIM-0013v311
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 theETSI 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 tothe 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 013 V3.1.1 (2025-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Test Purpose Descriptions . 8
4.1 jsonldContext . 8
4.1.1 Provision . 8
4.1.1.1 DeleteContext . 8
4.1.1.2 AddContext . 13
4.1.2 Consumption . 15
4.1.2.1 ServeContext . 15
4.1.2.2 ListContexts . 18
4.2 CommonBehaviours . 27
4.2.1 CommonResponses . 27
4.2.1.1 VerifyNotAcceptableMediaType . 27
4.2.1.2 VerifyMergePatchJson . 29
4.2.1.3 VerifyLdContextNotAvailable . 30
4.2.1.4 VerifyUnsupportedMediaType . 31
4.2.1.5 VerifyGETWithoutAccept . 33
4.3 ContextSource . 34
4.3.1 Registration . 34
4.3.1.1 RegisterContextSource . 34
4.3.1.2 UpdateContextSourceRegistration . 40
4.3.1.3 DeleteContextSourceRegistration . 43
4.3.2 RegistrationSubscription . 45
4.3.2.1 ContextSourceRegistrationSubscriptionNotificationBehaviour . 45
4.3.2.2 DeleteContextSourceRegistrationSubscription . 54
4.3.2.3 CreateContextSourceRegistrationSubscription . 55
4.3.2.4 RetrieveContextSourceRegistrationSubscription . 60
4.3.2.5 UpdateContextSourceRegistrationSubscription . 62
4.3.2.6 QueryContextSourceRegistrationSubscriptions . 64
4.3.3 Discovery . 68
4.3.3.1 QueryContextSourceRegistrations . 68
4.3.3.2 RetrieveContextSourceRegistration . 77
4.4 ContextInformation . 80
4.4.1 Provision . 80
4.4.1.1 TemporalEntity . 80
4.4.1.1.1 CreateTemporalRepresentationOfEntity . 80
4.4.1.1.2 DeleteTemporalRepresentationOfEntity . 82
4.4.1.1.3 UpdateTemporalRepresentationOfEntity . 83
4.4.1.2 EntityAttributes . 84
4.4.1.2.1 AppendEntityAttributes . 84
4.4.1.2.2 UpdateEntityAttributes . 89
4.4.1.2.3 ReplaceEntityAttribute . 97
4.4.1.2.4 PartialAttributeUpdate . 100
4.4.1.2.5 DeleteEntityAttribute . 108
4.4.1.3 BatchEntities . 112
ETSI
4 ETSI GS CIM 013 V3.1.1 (2025-07)
4.4.1.3.1 CreateBatchOfEntities . 112
4.4.1.3.2 MergeBatchOfEntities . 118
4.4.1.3.3 UpsertBatchOfEntities . 120
4.4.1.3.4 UpdateBatchOfEntities . 126
4.4.1.3.5 DeleteBatchOfEntities . 129
4.4.1.4 TemporalEntityAttributes . 130
4.4.1.4.1 DeleteAttribute . 130
4.4.1.4.2 DeleteAttributeInstance . 134
4.4.1.4.3 AddAttributes . 137
4.4.1.4.4 PartialUpdateAttributeInstance . 139
4.4.1.5 Entities . 143
4.4.1.5.1 DeleteEntity . 143
4.4.1.5.2 CreateEntity . 144
4.4.1.5.3 ReplaceEntity . 151
4.4.1.5.4 MergeEntity . 153
4.4.2 Consumption . 159
4.4.2.1 Entity . 159
4.4.2.1.1 QueryEntities . 159
4.4.2.1.2 RetrieveEntity . 178
4.4.2.2 TemporalEntity . 185
4.4.2.2.1 RetrieveTemporalEvolutionOfEntity . 185
4.4.2.2.2 QueryTemporalEvolutionOfEntities. 203
4.4.2.3 Discovery . 217
4.4.2.3.1 RetrieveDetailsOfAvailableEntityTypes . 217
4.4.2.3.2 RetrieveAvailableEntityTypeInformation . 218
4.4.2.3.3 RetrieveDetailsOfAvailableAttributes . 219
4.4.2.3.4 RetrieveAvailableAttributeInformation . 220
4.4.2.3.5 RetrieveAvailableAttributes . 220
4.4.2.3.6 RetrieveAvailableEntityTypes . 221
4.4.3 Subscription . 222
4.4.3.1 QuerySubscriptions . 222
4.4.3.2 UpdateSubscription . 223
4.4.3.3 SubscriptionNotificationBehaviour . 228
4.4.3.3.1 MQTT . 246
4.4.3.4 RetrieveSubscription . 249
4.4.3.5 CreateSubscription . 250
4.4.3.6 DeleteSubscription . 253
Annex A (informative): Bibliography . 255
Annex B (informative): Change History . 256
History . 257

ETSI
5 ETSI GS CIM 013 V3.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.

ETSI
6 ETSI GS CIM 013 V3.1.1 (2025-07)
1 Scope
The present document contains the description of each abstract test case using the Test Template [i.2] and using the Test
Purposes Description Language identified in ETSI GS CIM 012 [i.3] and ETSI GR CIM 011 [i.1]. The test cases are
described in tabular form. All clauses mentioned in tables of clause 4 of the present document are references to the
NGSI-LD specification, hence to be found in ETSI GS CIM 009 [1].
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.6.1) (2022-08): "cross-cutting 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.
[i.1] ETSI GR CIM 011 (V1.1.1) (2021-04): "Context Information Management (CIM); NGSI-LD
Testing Framework: Test Purposes Description Language (TPDL)".
[i.2] ETSI GS CIM 016 (V1.1.1) (2021-04): "Context Information Management (CIM); NGSI-LD
Testing Framework: Test Template".
[i.3] ETSI GS CIM 012 (V2.1.1) (2024-04): "Context Information Management (CIM); NGSI-LD Test
Suite Structure".
ETSI
7 ETSI GS CIM 013 V3.1.1 (2025-07)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
NOTE: The letters "NGSI-LD" were added to most terms to confirm that they are distinct from other terms of
similar/same name in use in other organizations, however, in the present document the letters "NGSI-LD"
are generally omitted for brevity.
NGSI-LD Central Broker: NGSI-LD Context Broker that only uses a local storage when serving NGSI-LD requests,
without involving any external Context Sources
NGSI-LD Context Broker: architectural component that implements all the NGSI-LD interfaces
NGSI-LD Context Consumer: agent that uses the query and subscription functionality of NGSI-LD to retrieve context
information
NGSI-LD Context Producer: agent that uses the NGSI-LD context provision and/or registration functionality to
provide or announce the availability of its context information to an NGSI-LD Context Broker
NGSI-LD Context Registry: software functional element where Context Sources register the information that they can
provide
NOTE: It is used by Distribution Brokers and Federation Brokers to find the appropriate Context Sources which
can provide the information required for serving an NGSI-LD request.
NGSI-LD Context Source: source of context information which implements the NGSI-LD consumption and
subscription (and possibly provision) interfaces defined by the present document
NOTE: It is usually registered with an NGSI-LD Registry so that it can announce what kind of information it can
provide, when requested, to Context Consumers and Brokers.
NGSI-LD Distribution Broker: NGSI-LD Context Broker that uses both local context information and registration
information from an NGSI-LD Context Registry, to access matching context information from a set of distributed
Context Sources
NGSI-LD Federation Broker: Distribution Broker that federates information from multiple underlying NGSI-LD
Context Brokers and across domains
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
HTTP HperText Transfer Protocol
JSON Java Script Object Notation
MQTT Message Queueing Telemetry Transport
PICS Profile Implementation Conformance Statement
QoS Quality of Service
SUT System Under Test
TP Test Purpose
URI Unified Resource Identification
URL Unified Resource Location
ETSI
8 ETSI GS CIM 013 V3.1.1 (2025-07)
4 Test Purpose Descriptions
4.1 jsonldContext
4.1.1 Provision
4.1.1.1 DeleteContext
TP Id TP/NGSI-LD/CTX/Prov/051_09
Test objective
Check that one gets an error when try to delete the core @context
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection PICS_DelOneSpe@coInt
Initial conditions with { the SUT containing a core context and it has been deleted with reload set to true. }
Permutations
TP Permutation id
TP/NGSI-LD/CTX/Prov/051_09_01
Name
051_09_01 Delete a core @contexts with reload set to true and check if the context has
been download again by the broker
Parent Release v1.5.1
Description
Delete a core @contexts with reload set to true and check downloaded core context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'GET' Serve a
@context with contextID 'https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-
v1.6.jsonld' and details 'true' }
then { the SUT sends a valid Response for the operation: Serve a @context SUT -> Client
with Response Status Code set to 200 }

TP Id TP/NGSI-LD/CTX/Prov/051_08
Test objective Check that one gets an error when try to delete the core @context
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection PICS_DelOneSpe@coInt
Initial conditions
with { the SUT containing an initial state }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/051_08_01
Name 051_08_01 Delete a core @contexts and return an error with no reload
Parent Release v1.5.1
Description Check that one gets an error when try to delete the core @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to 'https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-
context-v1.6.jsonld' }
then { the SUT sends a valid Response for the operations: Delete a
SUT -> Client
@context with Response Status Code set to 400 and Delete a @context
with Response reason set to 'Bad Request' and Delete a @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/BadRequestData' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }
ETSI
9 ETSI GS CIM 013 V3.1.1 (2025-07)
TP Permutation id TP/NGSI-LD/CTX/Prov/051_08_02
Name 051_08_02 Delete a core @contexts and return an error with reload set to false
Parent Release v1.5.1
Description Check that one gets an error when try to delete the core @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to 'https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-
context-v1.6.jsonld' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 400 and Delete a @context
with Response reason set to 'Bad Request' and Delete a @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/BadRequestData' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }

TP Id TP/NGSI-LD/CTX/Prov/051_02
Test objective Check that one gets an error when trying to delete an unknown @context identifier
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection
PICS_DelOneSpe@coInt
Initial conditions
with { the SUT containing an initial state }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/051_02_01
Name 051_02_01 Delete a @context with unknown @context identifier
Parent Release v1.5.1
Description Check that an error message is obtained in the response when one tries to delete a
@context with unknonwn id
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${random_url}' }
then { the SUT sends a valid Response for the operations: Delete a
SUT -> Client
@context with Response Status Code set to 404 and Delete a @context
with Response reason set to 'Not Found' and Delete a @context with
Response Body containing the type
'${ERROR_TYPE_RESOURCE_NOT_FOUND}' and Response Body Title is
a string and is not ${EMPTY} and Response Body Detail is a string and is
not ${EMPTY} and Response Boty Title is not equal to Response Body
Detail }
TP Id TP/NGSI-LD/CTX/Prov/051_04
Test objective
Check that one gets an error when try to delete a @context
Reference
ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection PICS_DelOneSpe@coInt
Initial conditions with { the SUT containing a Hosted @context and the default Cached Core Context. }
Permutations
TP Permutation id
TP/NGSI-LD/CTX/Prov/051_04_01
Name
051_04_01 Delete a @contexts with a wrong id and reload set to true
Parent Release v1.5.1
Description Check that one can delete a hosted @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to 'wrong_id_context' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 400 and Delete a @context
with Response reason set to 'Bad Request' and Delete a @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/BadRequestData' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }
ETSI
10 ETSI GS CIM 013 V3.1.1 (2025-07)
TP Permutation id TP/NGSI-LD/CTX/Prov/051_04_02
Name 051_04_02 Delete a @contexts with a wrong id and reload set to false
Parent Release v1.5.1
Description Check that one can delete a hosted @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to 'wrong_id_context' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 404 and Delete a @context
with Response reason set to 'Not Found' and Delete a @context with
Response Body containing the type
'${ERROR_TYPE_RESOURCE_NOT_FOUND}' and Response Body Title is
a string and is not ${EMPTY} and Response Body Detail is a string and is
not ${EMPTY} and Response Boty Title is not equal to Response Body
Detail }
TP Permutation id TP/NGSI-LD/CTX/Prov/051_04_03
Name 051_04_03 Delete a @contexts with a wrong id and no reload value
Parent Release v1.5.1
Description Check that one can delete a hosted @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to 'wrong_id_context' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 404 and Delete a @context
with Response reason set to 'Not Found' and Delete a @context with
Response Body containing the type
'${ERROR_TYPE_RESOURCE_NOT_FOUND}' and Response Body Title is
a string and is not ${EMPTY} and Response Body Detail is a string and is
not ${EMPTY} and Response Boty Title is not equal to Response Body
Detail }
TP Permutation id
TP/NGSI-LD/CTX/Prov/051_04_04
Name 051_04_04 Delete a @contexts with a wrong id and wrong reload value
Parent Release v1.5.1
Description Check that one can delete a hosted @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to 'wrong_id_context' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 400 and Delete a @context
with Response reason set to 'Bad Request' and Delete a @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/BadRequestData' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }
TP Permutation id TP/NGSI-LD/CTX/Prov/051_04_05
Name 051_04_05 Delete a Hosted @contexts with a valid id and reload set to true
Parent Release v1.5.1
Description Check that one can delete a hosted @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to
SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${uri}' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 400 and Delete a @context
with Response reason set to 'Bad Request' and Delete a @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/BadRequestData' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }

ETSI
11 ETSI GS CIM 013 V3.1.1 (2025-07)
TP Id TP/NGSI-LD/CTX/Prov/051_06
Test objective Delete a @context whose kind is ImplicitlyCreated without reload param
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection
PICS_DelOneSpe@coInt
Initial conditions
with { the SUT containing a ImplicitlyCreated @context created from a subscription query. }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/051_06_01
Name 051_06_01 Delete a @context whose kind is ImplicitlyCreated without reload param
Parent Release v1.5.1
Description Check that one can delete a ImplicitlyCreated @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${implicit_id}' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 204 and Delete a @context
with Response reason set to 'No Content' and Delete a @context with
Response does not contain a body }

TP Id TP/NGSI-LD/CTX/Prov/051_01
Test objective Check that one can delete a previous created hosted @context without reload param
Reference
ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id
CF_01
PICS Selection PICS_DelOneSpe@coInt
Initial conditions with { the SUT containing a Hosted @context and the default Cached Core Context. }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/051_01_01
Name
051_01_01 Delete a @context whose kind is hosted without reload param
Parent Release
v1.5.1
Description Check that one can delete a hosted @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${uri}' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 204 and Delete a @context
with Response reason set to 'No Content' and Delete a @context with
Response does not contain a body }

TP Id
TP/NGSI-LD/CTX/Prov/051_03
Test objective Check that one can delete a previous created cached @context without reload param
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection PICS_DelOneSpe@coInt
Initial conditions with { the SUT containing a Cached @context added from a URL. }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/051_03_01
Name 051_03_01 Delete a @context whose kind is cached without reload param
Parent Release v1.5.1
Description Check that one can delete a cached @context
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${contextId}' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 204 and Delete a @context
with Response reason set to 'No Content' and Delete a @context with
Response does not contain a body }

ETSI
12 ETSI GS CIM 013 V3.1.1 (2025-07)
TP Id TP/NGSI-LD/CTX/Prov/051_07
Test objective Check that one cannot delete a ImplicitlyCreated @context with reload set to true
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection
PICS_DelOneSpe@coInt
Initial conditions
with { the SUT containing a ImplicitlyCreated @context created from a subscription query. }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/051_07_01
Name 051_07_01 Delete a ImplicitlyCreated @contexts with a valid id and reload set to true
Parent Release v1.5.1
Description Check that one cannot delete a ImplicitlyCreated @context with reload set to true
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${implicit_id}' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 400 and Delete a @context
with Response reason set to 'Bad Request' and Delete a @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/BadRequestData' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }

TP Id TP/NGSI-LD/CTX/Prov/051_05
Test objective Check that one gets an error if one created an entity with a context (Cached context) and
one tries to delete it with reload=true
Reference ETSI GS CIM 009 V1.6.1 [1], clause 5.13.5
Config Id CF_01
PICS Selection
PICS_DelOneSpe@coInt
Initial conditions
with { the SUT containing a Cached @context created from a entity creation through
downloading from external server. }
Permutations
TP Permutation id
TP/NGSI-LD/CTX/Prov/051_05_01
Name 051_05_01 Delete and Reload a Cached @context with no communication with the Context
Server
Parent Release
v1.5.1
Description
Check that one gets an error if one tries to reload a cached context with no communication
with the context server
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts/{contextId}' method set to 'DELETE' Delete a
@context whose 'URI' set to '${uri}' }
then { the SUT sends a valid Response for the operations: Delete a SUT -> Client
@context with Response Status Code set to 503 and Delete a @context
with Response reason set to 'Service Unavailable' and Delete a @context
with Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/LdContextNotAvailable' and Response Body Title is a string and is
not ${EMPTY} and Response Body Detail is a string and is not ${EMPTY}
and Response Boty Title is not equal to Response Body Detail }

ETSI
13 ETSI GS CIM 013 V3.1.1 (2025-07)
4.1.1.2 AddContext
TP Id TP/NGSI-LD/CTX/Prov/050_02
Test objective Check that one receives a 400 Bad Request creating a @context if the content is incorrect
Reference
ETSI GS CIM 009 V1.6.1 [1], clause 5.13.2
Config Id
CF_01
PICS Selection PICS_AddUse@coTheInt
Initial conditions with { the SUT containing an initial state }
Permutations
TP Permutation id TP/NGSI-LD/CTX/Prov/050_02_01
Name 050_02_01 Checking Incorrect Payload
Parent Release
v1.5.1
Description
Check that the payload include "@context"
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts' method set to 'POST' Add a new @context
based on the payload defined in the file @context-incorrect.json }
then { the SUT sends a valid Response for the operations: Add a new SUT -> Client
@context with Response Status Code set to 400 and Add a new @context
with Response reason set to 'Bad Request' and Add a new @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/InvalidRequest' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }
TP Permutation id
TP/NGSI-LD/CTX/Prov/050_02_02
Name
050_02_02 Checking Wrong JSON
Parent Release v1.5.1
Description Check that the payload include "@context"
Expected behaviour Test events Direction
when { the SUT receives a Request from the client containing: URL set to SUT <- Client
'/ngsi-ld/v1/jsonldContexts' method set to 'POST' Add a new @context
based on the payload defined in the file @context-wrong-json.json }
then { the SUT sends a valid Response for the operations: Add a new SUT -> Client
@context with Response Status Code set to 400 and Add a new @context
with Response reason set to 'Bad Request' and Add a new @context with
Response Body containing the type 'https://uri.etsi.org/ngsi-
ld/errors/InvalidRequest' and Response Body Title is a string and is not
${EMPTY} and Response Body Detail is a string and is not ${EMPTY} and
Response Boty Title is not equal to Response Body Detail }

TP Id
TP/NGSI-LD/CTX/Prov/050_04
Test objective Check that one can add a hosted @context with list of URIs and each of them are cached
@coxtexts
Reference
ETSI GS CIM 009 V1.6.1 [1], clause 5.13.2
Config Id CF_01
PICS Selection PICS_AddUse@coTheInt
Initial conditions with { the SUT containing an initial state }
Permutations
...