ETSI TS 129 531 V15.5.0 (2019-10)

TECHNICAL SPECIFICATION
5G;
5G System;
Network Slice Selection Services;
Stage 3
(3GPP TS 29.531 version 15.5.0 Release 15)


3GPP TS 29.531 version 15.5.0 Release 15 1 ETSI TS 129 531 V15.5.0 (2019-10)

Reference
RTS/TSGC-0429531vf50
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2019.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ 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.
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 2 ETSI TS 129 531 V15.5.0 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, 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.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
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
3GPP TS 29.531 version 15.5.0 Release 15 3 ETSI TS 129 531 V15.5.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Overview . 8
4.1 Introduction . 8
5 Services offered by the NSSF . 8
5.1 Introduction . 8
5.2 Nnssf_NSSelection Service . 9
5.2.1 Service Description . 9
5.2.2 Service Operations . 9
5.2.2.1 Introduction . 9
5.2.2.2 GET . 9
5.2.2.2.1 General . 9
5.2.2.2.2 Get service operation of Nnssf_NSSelection service during the registration procedure . 10
5.2.2.2.3 Get service operation of Nnssf_NSSelection service during the PDU session establishment . 10
5.2.2.2.4 Get service operation of Nnssf_NSSelection service during UE configuration update
procedure . 11
5.3 Nnssf_NSSAIAvailability Service . 12
5.3.1 Service Description . 12
5.3.2 Service Operations . 12
5.3.2.1 Introduction . 12
5.3.2.2 Update Service Operation . 12
5.3.2.2.1 General . 12
5.3.2.3 Subscribe Service Operation . 13
5.3.2.3.1 General . 13
5.3.2.4 Unsubscribe Service Operation . 14
5.3.2.4.1 General . 14
5.3.2.5 Notify Service Operation . 14
5.3.2.5.1 General . 14
5.3.2.6 Delete Service Operation . 15
5.3.2.6.1 General . 15
6 API Definitions . 15
6.1 Nnssf_NSSelection Service API . 15
6.1.1 API URI . 15
6.1.2 Usage of HTTP . 15
6.1.2.1 General . 15
6.1.2.2 HTTP standard headers . 16
6.1.2.2.1 General . 16
6.1.2.2.2 Content type . 16
6.1.2.3.1 General . 16
6.1.3 Resources . 16
6.1.3.1 Overview . 16
6.1.3.2 Resource: Network Slice Information Document . 17
6.1.3.2.1 Description . 17
6.1.3.2.2 Resource Definition . 17
6.1.3.2.3 Resource Standard Methods . 17
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 4 ETSI TS 129 531 V15.5.0 (2019-10)
6.1.3.2.3.1 GET. 17
6.1.3.2.4 Resource Custom Operations . 18
6.1.4 Custom Operations without associated resources . 18
6.1.5 Notifications . 18
6.1.6 Data Model . 18
6.1.6.1 General . 18
6.1.6.2 Structured data types . 19
6.1.6.2.1 Introduction . 19
6.1.6.2.2 Type: AuthorizedNetworkSliceInfo . 20
6.1.6.2.3 Type: SubscribedSnssai . 22
6.1.6.2.4 Void . 22
6.1.6.2.5 Type: AllowedSnssai . 22
6.1.6.2.6 Type: AllowedNssai . 22
6.1.6.2.7 Type: NsiInformation . 23
6.1.6.2.8 Type: MappingOfSnssai . 23
6.1.6.2.9 Void . 24
6.1.6.2.10 Type: SliceInfoForRegistration . 24
6.1.6.2.11 Type: SliceInfoForPDUSession . 25
6.1.6.2.12 Type: ConfiguredSnssai . 25
6.1.6.2.13 Type: SliceInfoForUEConfigurationUpdate. 26
6.1.6.3 Simple data types and enumerations . 26
6.1.6.3.1 Introduction . 26
6.1.6.3.2 Simple data types . 26
6.1.6.3.3 Enumeration: RoamingIndication . 26
6.1.6.4 Binary data . 27
6.1.7 Error Handling . 27
6.1.7.1 General . 27
6.1.7.2 Protocol Errors . 27
6.1.7.3 Application Errors . 27
6.1.8 Feature negotiation . 27
6.1.9 Security . 28
6.2 Nnssf_NSSAIAvailability Service API . 28
6.2.1 API URI . 28
6.2.2 Usage of HTTP . 28
6.2.2.1 General . 28
6.2.2.2 HTTP standard headers . 28
6.2.2.2.1 General . 28
6.2.2.2.2 Content type . 28
6.2.2.2.3 Accept-Encoding . 29
6.2.2.3 HTTP custom headers . 29
6.2.2.3.1 General . 29
6.2.3 Resources . 29
6.2.3.1 Overview . 29
6.2.3.2 Resource: NSSAI Availability Document . 30
6.2.3.2.1 Description . 30
6.2.3.2.2 Resource Definition . 30
6.2.3.2.3 Resource Standard Methods . 30
6.2.3.2.3.1 PUT . 30
6.2.3.2.3.2 PATCH . 31
6.2.3.2.3.3 DELETE . 32
6.2.3.3 Resource: NSSAI Availability Notification Subscriptions Collection . 32
6.2.3.3.1 Description . 32
6.2.3.3.2 Resource Definition . 32
6.2.3.3.3 Resource Standard Methods . 32
6.2.3.3.3.1 POST. 32
6.2.3.4 Resource: Individual NSSAI Availability Notification Subscriptions . 33
6.2.3.4.1 Description . 33
6.2.3.4.2 Resource Definition . 33
6.2.3.4.3 Resource Standard Methods . 33
6.2.3.4.3.1 DELETE . 33
6.2.3.5 Resource: NSSAI Availability Store . 34
6.2.3.5.1 Description . 34
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 5 ETSI TS 129 531 V15.5.0 (2019-10)
6.2.3.5.2 Resource Definition . 34
6.2.3.5.3 Resource Standard Methods . 34
6.2.3.5.3.1 OPTIONS . 34
6.2.4 Custom Operations without associated resources . 35
6.2.5 Notifications . 35
6.2.5.1 General . 35
6.2.5.2 NSSAI Availability Notification . 35
6.2.5.2.1 Description . 35
6.2.5.2.2 Notification Definition . 35
6.2.5.2.3 Notification Standard Methods . 35
6.2.5.2.3.1 POST. 35
6.2.6 Data Model . 36
6.2.6.1 General . 36
6.2.6.2 Structured data types . 36
6.2.6.2.1 Introduction . 36
6.2.6.2.2 Type: NssaiAvailabilityInfo . 37
6.2.6.2.3 Type: SupportedNssaiAvailabilityData . 37
6.2.6.2.4 Type: AuthorizedNssaiAvailabilityData. 37
6.2.6.2.5 Type: RestrictedSnssai . 37
6.2.6.2.6 Type: AuthorizedNssaiAvailabilityinfo . 38
6.2.6.2.7 Type: PatchDocument . 38
6.2.6.2.8 Type: NssfEventSubscriptionCreateData . 38
6.2.6.2.9 Type: NssfEventSubscriptionCreatedData . 39
6.2.6.2.10 Type: NssfEventNotification . 39
6.2.6.3 Simple data types and enumerations . 39
6.2.6.3.1 Introduction . 39
6.2.6.3.2 Simple data types . 39
6.2.6.3.3 Enumeration: NssfEventType . 40
6.2.6.4 Binary data . 40
6.2.7 Error Handling . 40
6.2.7.1 General . 40
6.2.7.2 Protocol Errors . 40
6.2.7.3 Application Errors . 40
6.2.8 Feature negotiation . 40
6.2.9 Security . 41
Annex A (normative): OpenAPI specification . 42
A.1 General . 42
A.2 Nnssf_NSSelection API . 42
A.3 Nnssf_NSSAIAvailability API . 46
Annex B (informative): Change history . 53
History . 54

ETSI
3GPP TS 29.531 version 15.5.0 Release 15 6 ETSI TS 129 531 V15.5.0 (2019-10)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.

ETSI
3GPP TS 29.531 version 15.5.0 Release 15 7 ETSI TS 129 531 V15.5.0 (2019-10)
1 Scope
The present document specifies the stage 3 protocol and data model for the Nnssf Service Based Interface. It provides
stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NSSF.
The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition
are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[6] OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-
Specification/blob/master/versions/3.0.0.md.
[7] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[8] IETF RFC 6902: "JavaScript Object Notation (JSON) Patch".
[9] 3GPP TS 23.003: "Numbering, addressing and identification".
[10] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
[11] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
[12] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
[13] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".
[14] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
[15] IETF RFC 7807: "Problem Details for HTTP APIs".
[16] IETF RFC 1952: "GZIP file format specification version 4.3".
[17] 3GPP TR 21.900: "Technical Specification Group working methods".
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 8 ETSI TS 129 531 V15.5.0 (2019-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in
3GPP TR 21.905 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
4 Overview
4.1 Introduction
Within the 5GC, the NSSF offers services to the AMF and NSSF in a different PLMN via the Nnssf service based
interface (see 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]).
Figure 4.1-1 provides the reference model (in service based interface representation and in reference point
representation), with focus on the NSSF and the scope of the present specification.
AMF
N22
Nnssf NSSF
N31
NSSF
Figure 4.1-1: NSSF in 5G System architecture
The functionalities supported by the NSSF are listed in clause 6.2.14 of 3GPP TS 23.501 [2].
5 Services offered by the NSSF
5.1 Introduction
The NSSF supports the following services.
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 9 ETSI TS 129 531 V15.5.0 (2019-10)
Table 5.1-1: NF Services provided by NSSF
Service Name Description Example
Consumer
Nnssf_NSSelection This service enables Network Slice selection in both AMF, V-NSSF
the Serving PLMN and the HPLMN
Nnssf_NSSAIAvailability This service enables to update the S-NSSAI(s) the NF AMF
service consumer (e.g AMF) supports on a per TA
basis on the NSSF and to subscribe and notify any
change in status, on a per TA basis, of the SNSSAIs
available per TA (unrestricted) and the restricted S-
NSSAI(s) per PLMN in that TA in the serving PLMN of
the UE.
5.2 Nnssf_NSSelection Service
5.2.1 Service Description
The Nnssf_NSSelection service is used by an NF Service Consumer (e.g. AMF or NSSF in a different PLMN) to
retrieve the information related to network slice in the non-roaming and roaming case. It also enables the NSSF to
provide to the AMF the Allowed NSSAI and the Configured NSSAI for the Serving PLMN. The NF service consumer
discovers the NSSF based on the local configuration. The NSSF in a different PLMN is discovered based on the self-
constructed FQDN as specified in 3GPP TS 23.003 [9].
5.2.2 Service Operations
5.2.2.1 Introduction
For the Nnssf_NSSelection service the following service operations are defined:
- Get.
5.2.2.2 GET
5.2.2.2.1 General
The Get operation shall be used in the non-roaming or roaming scenario to retrieve:
- The Allowed NSSAI, Configured NSSAI, target AMF Set or the list of candidate AMF(s), and optionally
- The Mapping Of Allowed NSSAI;
- The Mapping Of Configured NSSAI;
- NSI ID(s) associated with the Network Slice instances of the Allowed NSSAI;
- NRF(s) to be used to select NFs/services within the selected Network Slice instance(s) and NRF to be used to
determine the list of candidate AMF(s) from the AMF Set, during Registration procedure and
- Information on whether the S-NSSAI(s) not included in the Allowed NSSAI which were part of the
Requested NSSAI are rejected in the serving PLMN or in the current TA.
- The NRF to be used to select NFs/services within the selected network slice instance, and optionally the NSI ID
associated with the S-NSSAI provided in the input, during the PDU Session Establishment procedure.
It is used in the following procedures:
- Registration with AMF re-allocation (see clause 4.2.2.2.3 of 3GPP TS 23.502 [3]);
- UE Configuration Update procedure (see clause 4.2.4.2 of 3GPP TS 23.502 [3]);
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 10 ETSI TS 129 531 V15.5.0 (2019-10)
- SMF selection for non-roaming and roaming with local breakout (see clause 4.3.2.2.3.2 of 3GPP TS 23.502 [3])
or SMF selection for home-routed roaming scenario (see clause 4.3.2.2.3.3 of 3GPP TS 23.502 [3]).
NOTE: The list of procedures above, which trigger invoking of the Nnssf_NSSelection_Get service operation, is
not exhaustive.
5.2.2.2.2 Get service operation of Nnssf_NSSelection service during the registration
procedure
In this procedure, the NF Service Consumer (e.g. AMF) retrieves the Allowed NSSAI, Configured NSSAI, target AMF
Set or the list of candidate AMF(s) and other optional information.

NF Service
NSSF
Consumer
1. GET ./v1/network-slice-information?
2. 200 OK (AuthorizedNetworkSliceInfo) or
4xx/5xx (ProblemDetails)
Figure 5.2.2.2.2-1: Retrieve the network slice information during the registration procedure
1 The AMF shall send a GET request to the NSSF. One or more of the following parameters shall be included as
query parameters: Requested NSSAI, Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI,
PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.
2 On success, "200 OK" shall be returned in the following cases:
- When the NSSF is able to find authorized network slice information for the requested network slice selection
information, the response body shall include a payload body containing at least the Allowed NSSAI, target AMF
Set or the list of candidate AMF(s);
- If no slice instances can be found for the requested slice selection information, then the response body shall
contain an empty "AuthorizedNetworkSliceInfo" JSON object.
On failure, the NSSF shall return one of the HTTP status codes together with the response body listed in Table
6.1.3.2.3.1-3.
5.2.2.2.3 Get service operation of Nnssf_NSSelection service during the PDU session
establishment
In this procedure, the NF Service Consumer (e.g. AMF) retrieves the NRF and the optionally the NSI ID of the network
slice instance:
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 11 ETSI TS 129 531 V15.5.0 (2019-10)

NF Service
NSSF
Consumer
1. GET ./v1/network-slice-information?
2. 200 OK (AuthorizedNetworkSliceInfo) or
4xx/5xx (ProblemDetails)
Figure 5.2.2.2.3-1: Retrieve the network slice information during the PDU session establishment
procedure
1 The NF Service consumer (e.g. AMF or NSSF in the different PLMN) shall send a GET request to the NSSF.
The request shall include query parameters, contain at least S-NSSAI, S-NSSAI from the HPLMN that maps to
the S-NSSAI from the Allowed NSSAI of the Serving PLMN, the NF type of the NF service consumer and
Requester ID. For the procedure invoked in the Serving PLMN, the query parameters shall also contain non-
roaming/LBO roaming/HR roaming indication, PLMN ID of the SUPI and TAI.
2 On success, "200 OK" shall be returned in the following cases:
- When the NSSF is able to find network slice instance information for the requested network slice selection
information, the response body shall include a payload body containing at least the NRF to be used to select
NFs/services within the selected Network Slice instance;
- If no slice instances can be found for the requested slice selection information, then the response body shall
contain an empty "AuthorizedNetworkSliceInfo" JSON object.
On failure, the NSSF shall return one of the HTTP status codes together with the response body listed in Table
6.1.3.2.3.1-3.
5.2.2.2.4 Get service operation of Nnssf_NSSelection service during UE configuration
update procedure
In this procedure, the NF Service Consumer (e.g. AMF) retrieves network slice configuration information (e.g. the
Allowed NSSAI and the Configured NSSAI) during the UE configuration update procedure.

NF Service
NSSF
Consumer
1. GET ./v1/network-slice-information?
2. 200 OK (AuthorizedNetworkSliceInfo) or
4xx/5xx (ProblemDetails)
Figure 5.2.2.2.4-1: Retrieve the network slice information during UE configuration update procedure
1 The NF Service consumer (e.g. AMF) shall send a GET request to the NSSF. The request shall include query
parameters: Subscribed S-NSSAI(s) with the indication if the S-NSSAI is marked as default S-NSSAI, PLMN
ID of the SUPI, TAI, NF type of the NF service consumer and the NF instance ID of the requester NF.
2 On success, "200 OK" shall be returned in the following cases:
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 12 ETSI TS 129 531 V15.5.0 (2019-10)
- When the NSSF is able to find authorized network slice information for the requested network slice selection
information, the response body shall include a payload body containing at least the Allowed NSSAI,
Configured NSSAI;
- If no slice instances can be found for the requested slice selection information, then the response body shall
contain an empty "AuthorizedNetworkSliceInfo" JSON object.
On failure, the NSSF shall return one of the HTTP status codes together with the response body listed in Table
6.1.3.2.3.1-3.
5.3 Nnssf_NSSAIAvailability Service
5.3.1 Service Description
The Nnssf_NSSAIAvailability service is used by the NF service consumer (e.g AMF) to update the S-NSSAI(s) the
AMF supports on a per TA basis on the NSSF, subscribe and unsubscribe the notification of any changes to the NSSAI
availability information on a per TA basis, of the S-NSSAIs available per TA (unrestricted) and the restricted S-
NSSAI(s) per PLMN in that TA in the serving PLMN of of the UE.
5.3.2 Service Operations
5.3.2.1 Introduction
For the Nnssf_NSSAIAvailability service the following service operations are defined:
- Update;
- Subscribe;
- Unsubscribe;
- Notify;
- Delete.
5.3.2.2 Update Service Operation
5.3.2.2.1 General
The Update operation shall be used by an NF Service Consumer (e.g. AMF) to update the NSSF with the S-NSSAIs the
NF service consumer (e.g. AMF) supports per TA, and get the availability of the S-NSSAIs per TA for the S-NSSAIs
the NF service consumer (e.g. AMF) supports.
NF Service
NSSF
Consumer
1. PUT ./v1/nssai-availability/{nfId}(NssaiAvailabilityInfo) or
PATCH ./v1/nssai-availability/{nfId}(NssaiAvailabilityUpdateInfo)
2. 200 OK (AuthorizedNssaiAvailabilityInfo) or
4xx / 5xx (ProblemDetails)
Figure 5.3.2.2.1-1: Update the S-NSSAIs the AMF supports per TA
1. The NF service consumer (e.g. AMF) shall send a PUT request to the resource representing the NSSAI
Availability information of the individual NF, identified by the {nfId}, to replace or create the NSSAI
ETSI
3GPP TS 29.531 version 15.5.0 Release 15 13 ETSI TS 129 531 V15.5.0 (2019-10)
Availability information of the NF. The payload of the body shall contain the NssaiAvailabilityInfo which
contains one or more representations of the individual supportedSnssai information to be replaced.
The NF service consumer (e.g. AMF) shall send a PATCH request to the resource representing the NSSAI
Availability information of the individual NF, identified by the {nfId}, to update the NSSAI Availability
information of the NF. The payload of the body shall contain the PatchDocument which contains one or more
PatchItem instructions for updating the individual supportedSnssai resources.
2. On success, "200 OK" shall be returned, the payload body of the PUT/PATCH response shall contain the
representation describing the status of the request and the complete AuthorizedNssaiAvailabilityData
information representing the current state of the AuthorizedNssaiAvailabilityInfo.
On failure, the NSSF shall return one of the HTTP status code together with the response body listed in Table
6.2.3.2.3.1-2 / Table 6.2.3.2.3.2-2.
5.3.
...