ETSI GS NFV-SOL 011 V5.3.1 (2025-09)

Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; RESTful protocols specification for the Or-Or Reference Point

RGS/NFV-SOL011ed531

General Information

• Status: Not Published
• Technical Committee: NFV SOL - Solutions
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 17-Sep-2025
• Completion Date: 09-Sep-2025

Standards Content (Sample)

GROUP SPECIFICATION
Network Functions Virtualisation (NFV) Release 5;
Protocols and Data Models;
RESTful protocols specification for the Or-Or Reference Point
Disclaimer
The present document has been produced and approved by the Network Functions Virtualisation (NFV) 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 NFV-SOL 011 V5.3.1 (2025-09)

Reference
RGS/NFV-SOL011ed531
Keywords
API, data, management, model, NFV, protocol

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 NFV-SOL 011 V5.3.1 (2025-09)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 7
3.1 Terms . 7
3.2 Symbols . 8
3.3 Abbreviations . 8
4 General aspects . 8
4.1 Overview . 8
4.2 Common data types . 8
5 NSD Management interface . 9
6 NS Lifecycle Management interface . 9
7 NS Lifecycle Operation Granting interface . 9
7.1 Description . 9
7.2 API version . 9
7.3 Resource structure and method . 9
7.4 Sequence diagrams (informative) . 10
7.4.1 Flow of requesting a grant . 10
7.5 Resources . 10
7.5.1 Introduction. 10
7.5.2 Resource: API versions . 11
7.5.3 Resource: Grants . 11
7.5.3.1 Description . 11
7.5.3.2 Resource definition . 11
7.5.3.3 Resource methods . 11
7.5.3.3.1 POST . 11
7.5.3.3.2 GET . 12
7.5.3.3.3 PUT . 12
7.5.3.3.4 PATCH . 12
7.5.3.3.5 DELETE . 12
7.5.4 Resource: Individual grant . 12
7.5.4.1 Description . 12
7.5.4.2 Resource definition . 12
7.5.4.3 Resource methods . 13
7.5.4.3.1 POST . 13
7.5.4.3.2 GET . 13
7.5.4.3.3 PUT . 13
7.5.4.3.4 PATCH . 13
7.5.4.3.5 DELETE . 13
7.6 Data model . 14
7.6.1 Introduction. 14
7.6.2 Resource and notification data types . 14
7.6.2.1 Introduction . 14
7.6.2.2 Type: GrantNsLifecycleOperationRequest . 14
7.6.2.3 Type: Grant . 14
7.6.3 Referenced structured data types . 15
7.6.4 Referenced simple data types and enumerations . 15
7.6.4.1 Introduction . 15
ETSI
4 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
7.6.4.2 Simple data types . 15
7.6.4.3 Enumeration: NsLcmOperation . 15
8 NS Instance Usage Notification interface . 15
8.1 Description . 15
8.2 API version . 16
8.3 Resource structure and method . 16
8.4 Sequence diagrams (informative) . 17
8.4.1 Flow of managing subscriptions . 17
8.4.2 Flow of sending notifications. 19
8.5 Resources . 20
8.5.1 Introduction. 20
8.5.2 Resource: API versions . 20
8.5.3 Resource: Subscriptions . 20
8.5.3.1 Description . 20
8.5.3.2 Resource definition . 20
8.5.3.3 Resource methods . 21
8.5.3.3.1 POST . 21
8.5.3.3.2 GET . 22
8.5.3.3.3 PUT . 23
8.5.3.3.4 PATCH . 23
8.5.3.3.5 DELETE . 23
8.5.4 Resource: Individual subscription . 24
8.5.4.1 Description . 24
8.5.4.2 Resource definition . 24
8.5.4.3 Resource methods . 24
8.5.4.3.1 POST . 24
8.5.4.3.2 GET . 24
8.5.4.3.3 PUT . 25
8.5.4.3.4 PATCH . 25
8.5.4.3.5 DELETE . 25
8.5.5 Resource: Notification endpoint . 25
8.5.5.1 Description . 25
8.5.5.2 Resource definition . 25
8.5.5.3 Resource methods . 26
8.5.5.3.1 POST . 26
8.5.5.3.2 GET . 26
8.5.5.3.3 PUT . 26
8.5.5.3.4 PATCH . 27
8.5.5.3.5 DELETE . 27
8.6 Data model . 27
8.6.1 Introduction. 27
8.6.2 Resource and notification data types . 27
8.6.2.1 Introduction . 27
8.6.2.2 Type: NsInstanceUsageSubscriptionRequest . 27
8.6.2.3 Type: NsInstanceUsageSubscription . 27
8.6.2.4 Type: NsInstanceUsageNotification . 28
8.6.3 Referenced structured data types . 28
8.6.3.1 Type: NsInstanceUsageNotificationsFilter . 28
8.6.4 Referenced simple data types and enumerations . 29
8.6.4.1 Introduction . 29
8.6.4.2 Simple data types . 29
8.6.4.3 Enumeration: NsInstanceUsageStatusType . 29
9 NS Performance Management interface . 29
10 NS Fault Management interface . 29
Annex A (informative): Mapping operations to protocol elements . 30
A.1 Overview . 30
A.2 NSD Management interface . 30
ETSI
5 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
A.3 NS lifecycle management interface . 30
A.4 NS lifecycle operation granting interface . 31
A.5 NS instance usage notification interface . 31
A.6 NS performance management interface . 31
A.7 NS fault management interface . 32
Annex B (normative): Authorization scope values . 33
B.1 Overview . 33
B.2 NSD Management interface . 33
B.3 NS Lifecycle Management interface . 33
B.4 NS Performance Management interface . 33
B.5 NS Fault Management interface . 34
B.6 NS Lifecycle Operation Granting interface . 34
B.7 NS Instance Usage Notification interface . 34
Annex C (informative): Complementary material for API utilization . 36
Annex D (informative): Change history . 37
History . 38

ETSI
6 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
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) Network Functions
Virtualisation (NFV).
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
7 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
1 Scope
The present document specifies a set of RESTful protocol and data models fulfilling the requirements specified in ETSI
GS NFV-IFA 030 [1] for the interfaces used over the Or-Or reference point.
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 NFV-IFA 030: "Network Functions Virtualisation (NFV) Release 5; Management and
Orchestration; Multiple Administrative Domain Aspect Interfaces Specification".
[2] ETSI GS NFV-SOL 013: "Network Functions Virtualisation (NFV) Release 5; Protocols and Data
Models; Specification of common aspects for RESTful NFV MANO APIs".
[3] ETSI GS NFV-SOL 005: "Network Functions Virtualisation (NFV) Release 5; Protocols and Data
Models; RESTful protocols specification for the Os-Ma-nfvo Reference Point".
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 NFV 003: "Network Functions Virtualisation (NFV); Terminology for Main Concepts in
NFV".
[i.2] OpenAPI™ Specification.
[i.3] ETSI GS NFV-SOL 015: "Network Functions Virtualisation (NFV); Protocols and Data Models;
Specification of Patterns and Conventions for RESTful NFV-MANO APIs".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI GR NFV 003 [i.1] and ETSI GS NFV-IFA 030 [1]
apply.
ETSI
8 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI GR NFV 003 [i.1] and the following apply:
HTTP HyperText Transfer Protocol
4 General aspects
4.1 Overview
The present document defines the protocol and data model for the following interfaces, in the form of RESTful
Application Programming Interface (APIs) specifications:
• NSD Management interface (as produced by the NFVO-N towards the NFVO-C).
• NS Lifecycle Management interface (as produced by the NFVO-N towards the NFVO-C).
• NS Lifecycle Operation Granting interface (as produced by the NFVO-N towards the NFVO-C).
• NS Instance Usage Notification interface (as produced by the NFVO-N towards the NFVO-C).
• NS Performance Management interface (as produced by the NFVO-N towards the NFVO-C).
• NS Fault Management interface (as produced by the NFVO-N towards the NFVO-C).
The design of the protocol and data model for the above interfaces is based on the information model and requirements
defined in ETSI GS NFV-IFA 030 [1].
In the subsequent clauses, the protocol and data model for the individual interfaces are specified. Per interface, the
resource structure with associated HTTP methods is defined and applicable flows are provided. Further, the resources
and the data model are specified in detail.
Annex A provides the mapping of the combination of resources and methods defined in the present document to the
operations defined in ETSI GS NFV-IFA 030 [1].
Even though the various interfaces defined in the present document are related, implementations shall not assume a
particular order of messages that arrive via different interfaces.
4.2 Common data types
The structured data types and simple data types defined in clause 7 of ETSI GS NFV-SOL 013 [2] shall apply in the
present document.
ETSI
9 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
5 NSD Management interface
This interface allows the NFVO-C to invoke management operations of NSDs towards the NFVO-N.
The interface shall follow the provisions specified in clause 5 of ETSI GS NFV-SOL 005 [3] for the NSD management
interface, except that the producer is NFVO-N and the consumer is NFVO-C.
Only the "query NSD info" operation as defined in clause 5 of ETSI GS NFV-SOL 005 [3] is supported on the Or-Or
reference point, i.e. only the "NS Descriptors" and "Individual NS Descriptor" resources with the GET method are
supported for the present interface, and the API producer shall return a "405 Method Not Allowed" response for other
methods requested on the "NS Descriptors" and "Individual NS Descriptor" resources, as defined in clause 6.4 of ETSI
GS NFV-SOL 013 [2].
6 NS Lifecycle Management interface
This interface allows the NFVO-C to invoke NS lifecycle management operations of NS instances towards the NFVO-N,
and to subscribe to notifications regarding NS lifecycle changes provided by the NFVO-N.
The interface shall follow the provisions specified in clause 6 of ETSI GS NFV-SOL 005 [3] for the NS lifecycle
management interface, except that the producer is NFVO-N and the consumer is NFVO-C.
The "update NS" as defined in clause 6 of ETSI GS NFV-SOL 005 [3] is not supported on the Or-Or reference point,
i.e. the "Update NS task" resource and related methods are not supported for the present interface, and the API producer
shall return a "404 Not Found" response for all methods requested on the "update NS" resource, as defined in clause 6.4
of ETSI GS NFV-SOL 013 [2].
7 NS Lifecycle Operation Granting interface
7.1 Description
This interface allows the NFVO-N to obtain from the NFVO-C permission for an NS lifecycle operations. This
interface also allows API version information retrieval.
The operations provided through this interface are:
• Grant NS Lifecycle Operation.
7.2 API version
For the NS lifecycle operation granting interface as specified in the present document, the MAJOR version field shall be
1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see clause 9.1 of ETSI
GS NFV-SOL 013 [2] for a definition of the version fields). Consequently, the {apiMajorVersion} URI variable shall
be set to "v1".
7.3 Resource structure and method
All resource URIs of the API shall use the base URI specification defined in clause 4.1 of ETSI GS NFV-SOL 013 [2].
The string "nslcog" shall be used to represent {apiName}. All resource URIs in the clauses below are defined relative to
the above base URI.
Figure 7.3-1 shows the overall resource URI structure defined for the NS lifecycle operation granting interface.
ETSI
10 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
{apiRoot}/nslcog/{apiMajorVersion}
/grants
/{grantId}
Figure 7.3-1: Resource URI structure of the NS lifecycle operation granting interface
Table 7.3-1 lists the individual resources defined, and the applicable HTTP methods.
The NFVO-C shall support responding to requests for all HTTP methods on the resources in table 7.3-1 that are marked
as "M" (Mandatory) in the "Cat" column. The NFVO-C shall also support the "API versions" resource as specified in
clause 9.3.2 of ETSI GS NFV-SOL 013 [2].
Table 7.3-1: Resources and methods overview of the NS lifecycle operation granting interface
Resource name Resource URI HTTP Method Cat Meaning
Grants /grants POST M Request a grant
Individual grant /grants/{grantId} GET M Read a grant

7.4 Sequence diagrams (informative)
7.4.1 Flow of requesting a grant
This clause describes a sequence for requesting a grant.

Figure 7.4.1-1: Flow of requesting a grant
The grant request procedure, as illustrated in figure 7.4.1-1, consists of the following steps:
1) The NFVO-N sends a POST request to the "Grants" resource, including one data structure of type
"GrantNsLifecycleOperationRequest" in the payload body.
2) The NFVO-C checks whether the consistency of the composite NS is impacted by the nested NS lifecycle
operation.
3) The NFVO-C returns a "201 Created" response with a "Grant" data structure in the body.
Error handling: In case of failure or rejection of the grant request, appropriate error information is provided in the
response.
7.5 Resources
7.5.1 Introduction
This clause defines all the resources and methods provided by the NS lifecycle operation granting interface.
ETSI
11 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
7.5.2 Resource: API versions
The "API versions" resources, as defined in clause 9.3.3 of ETSI GS NFV-SOL 013 [2], are part of the NS lifecycle
operation granting interface.
7.5.3 Resource: Grants
7.5.3.1 Description
This resource represents grants. The NFVO-N can use this resource to request a grant.
7.5.3.2 Resource definition
The resource URI is:
{apiRoot}/nslcog/{apiMajorVersion}/grants
This resource shall support the resource URI variables defined in table 7.5.3.2-1.
Table 7.5.3.2-1: Resource URI variables for this resource
Name Definition
apiRoot See clause 4.1 of ETSI GS NFV-SOL 013 [2]
apiMajorVersion See clause 7.2

7.5.3.3 Resource methods
7.5.3.3.1 POST
The POST method requests a grant for a particular NS lifecycle operation.
This method shall follow the provisions specified in tables 7.5.3.3.1-1 and 7.5.3.3.1-2 for URI query parameters, request
and response data structures, and response codes.
As the result of successfully processing this request, a new "Individual grant" resource shall be created.
Table 7.5.3.3.1-1: URI query parameters supported by the POST method on this resource
Name Cardinality Description
none supported
ETSI
12 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
Table 7.5.3.3.1-2: Details of the POST request/response on this resource
Data type Cardinality Description
Request
GrantNsLifecycleOperat 1 The NS lifecycle operation grant request parameters, as defined
body
ionRequest in clause 7.6.2.2.
Response
Data type Cardinality Description
Codes
Grant 201 Shall be returned when the grant has been created
Created successfully.
A representation of the created "Individual grant"
resource shall be returned in the response body.

The HTTP response shall include a "Location"
HTTP header that indicates the URI of the
Response
"Individual grant" resource just created.
body
ProblemDetails 1 403 Shall be returned upon the following error: the grant
Forbidden request was rejected.

A ProblemDetails structure shall be included in the
response to provide more details about the
rejection in the "details" attribute.
ProblemDetails See 4xx/5xx In addition to the response codes defined above,
clause 6.4 of any common error response code as defined in
[2] clause 6.4 of ETSI GS NFV-SOL 013 [2] may be
returned.
7.5.3.3.2 GET
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.3.3.3 PUT
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.3.3.4 PATCH
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.3.3.5 DELETE
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.4 Resource: Individual grant
7.5.4.1 Description
This resource represents an individual grant.
7.5.4.2 Resource definition
The resource URI is:
{apiRoot}/nslcog/{apiMajorVersion}/grants/{grantId}
This resource shall support the resource URI variables defined in table 7.5.4.2-1.
ETSI
13 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
Table 7.5.4.2-1: Resource URI variables for this resource
Name Definition
apiRoot See clause 4.1 of ETSI GS NFV-SOL 013 [2]
apiMajorVersion See clause 7.2
grantId Identifier of the grant. See note.
NOTE: This identifier can be retrieved from the "id" attribute in the payload body of the response
to a POST request granting a new NS lifecycle operation.

7.5.4.3 Resource methods
7.5.4.3.1 POST
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.4.3.2 GET
The GET method reads a grant.
This method shall follow the provisions specified in tables 7.5.4.3.2-1 and 7.5.4.3.2-2 for URI query parameters, request
and response data structures, and response codes.
Table 7.5.4.3.2-1: URI query parameters supported by the GET method on this resource
Name Cardinality Description
none supported
Table 7.5.4.3.2-2: Details of the GET request/response on this resource
Request Data type Cardinality Description
body n/a
Response
Data type Cardinality Description
Codes
Grant 1 200 OK Shall be returned when the grant has been read
successfully.
Response
A representation of the "Individual grant" resource
body
shall be returned in the response body.
ProblemDetails See clause 6.4 4xx/5xx In addition to the response codes defined above, any
of [2] common error response code as defined in
clause 6.4 of ETSI GS NFV-SOL 013 [2] may be
returned.
7.5.4.3.3 PUT
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.4.3.4 PATCH
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
7.5.4.3.5 DELETE
This method is not supported. When this method is requested on this resource, the API producer shall return a
"405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [2].
ETSI
14 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
7.6 Data model
7.6.1 Introduction
This clause defines the request and response data structures of the NS lifecycle operation granting interface. If a request
or response contains attributes not defined in the present document, a receiving functional block that does not
understand these attributes shall not treat their presence as an error, and may choose to ignore them.
7.6.2 Resource and notification data types
7.6.2.1 Introduction
This clause defines the data structures to be used in resource representations and notifications.
7.6.2.2 Type: GrantNsLifecycleOperationRequest
This type represents request parameters for the "grant NS lifecycle" operation. It shall comply with the provisions
defined in table 7.6.2.2-1.
Table 7.6.2.2-1: Definition of the GrantNsLifecycleOperationRequest data type
Attribute name Data type Cardinality Description
nsInstanceId Identifier 1 Identifier of the NS instance which this grant
request relates to.
See note 1.
nsdId Identifier 1 Identifier of the NSD that defines the NS for which
the lifecycle management operation is to be
granted.
nsLcmOpOccId Identifier 1 The identifier of the NS lifecycle management
operation occurrence associated to the
GrantRequest.
lifecycleOperation NsLcmOperation 1 Type of the lifecycle management operation for
which the granting is requested.

See note 2.
additionalParams KeyValuePairs 0.1 Additional parameters passed by NFVO-N,
specific to the NS and the lifecycle management
operation.
NOTE 1: Each NFVO-N instance manages its own namespace for NS instance identifiers.
NOTE 2: The NS LCM operations InstantiateNS, CreateNsIdentifier, DeleteNsIdentifier, Get Operation Status and
QueryNs can be executed by NFVO-N without requesting granting.

7.6.2.3 Type: Grant
This type represents a grant. It shall comply with the provisions defined in table 7.6.2.3-1.
ETSI
15 ETSI GS NFV-SOL 011 V5.3.1 (2025-09)
Table 7.6.2.3-1: Definition of the Grant data type
Attribute name Data type Cardinality Description
id Identifier 1 Identifier of the grant.
nsInstanceId Identifier 1 Identifier of the NS instance which this grant
request relates to.
nsLcmOpOccId Identifier 1 Identifier of the NS lifecycle management
operation occurrence associated to the
GrantRequest.
additionalParams KeyValuePairs 0.1 Additional parameters passed by NFVO-N,
specific to the NS and the lifecycle management
operation.
_links Structure (inlined) 1 Links to resources related to this resource.
>self Link 1 URI of this resource.
>nsLcmOpOcc Link 1 Related NS lifecycle management operation
occurrence.
>nsInstance Link 1 Related NS instance.

7.6.3 Referenced structured data types
No particular referenced structured data types are defined for this interface.
7.6.4 Referenced simple data types and enumerations
7.6.4.1 Introduction
This clause defines simple data types and enumerations that can be referenced from data structures defined in the
previous clauses.
7.6.4.2 Simple data types
No particular simple data types are defined for this interface, in addition to those defined in clause 4.2.
7.6.4.3 Enumeration: NsLcmOperation
The enumeration NsLcmOperation shall comply with the provisions defined in table 7.6.4.3-1. It indicates the type of
the NS lifecycle management operation for which the granting is requested.
Table 7.6.4.3-1: Enumeration NsLcmOperation
Enumeration value
...