切片选择服务

3GPPTS29.531V17.1.0(2021-06)

TechnicalSpecification

3rdGenerationPartnershipProject;

TechnicalSpecificationGroupCoreNetworkandTerminals;

5GSystem;

NetworkSliceSelectionServices;

Stage3

(Release17)

Thepresentdocumenthasbeendevelopedwithinthe3rdGenerationPartnershipProject(3GPPTM)andmaybefurtherelaboratedforthepurposesof3GPP.

Thepresentdocumenthasnotbeensubjecttoanyapprovalprocessbythe3GPPOrganizationalPartnersandshallnotbeimplemented.

ThisSpecificationisprovidedforfuturedevelopmentworkwithin3GPPonly.TheOrganizationalPartnersacceptnoliabilityforanyuseofthisSpecification.

SpecificationsandReportsforimplementationofthe3GPPTMsystemshouldbeobtainedviathe3GPPOrganizationalPartners'PublicationsOffices.

STYLEREFZA

PAGE

56

STYLEREFZGSM

Release17

3GPP

3GPP

Postaladdress

3GPPsupportofficeaddress

650RoutedesLucioles-SophiaAntipolis

Valbonne-FRANCE

Tel.:+33492944200Fax:+33493654716

Internet

CopyrightNotification

Nopartmaybereproducedexceptasauthorizedbywrittenpermission.

Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.

©2021,3GPPOrganizationalPartners(ARIB,ATIS,CCSA,ETSI,TSDSI,TTA,TTC).

Allrightsreserved.

UMTS™isaTradeMarkofETSIregisteredforthebenefitofitsmembers

3GPP™isaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners

LTE™isaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners

GSM®andtheGSMlogoareregisteredandownedbytheGSMAssociation

Contents

TOC\o"1-9"

Foreword

6

1 Scope

7

2 References

7

3 Definitionsandabbreviations

8

3.1 Definitions

8

3.2 Abbreviations

8

4 Overview

8

4.1 Introduction

8

5 ServicesofferedbytheNSSF

9

5.1 Introduction

9

5.2 Nnssf_NSSelectionService

9

5.2.1 ServiceDescription

9

5.2.2 ServiceOperations

9

Introduction

9

GET

9

.1 General

9

.2 GetserviceoperationofNnssf_NSSelectionservice

10

.3 GetserviceoperationofNnssf_NSSelectionserviceduringthePDUsessionestablishment

11

.4 GetserviceoperationofNnssf_NSSelectionserviceduringUEconfigurationupdateprocedure

12

5.3 Nnssf_NSSAIAvailabilityService

12

5.3.1 ServiceDescription

12

5.3.2 ServiceOperations

13

Introduction

13

UpdateServiceOperation

13

.1 General

13

SubscribeServiceOperation

14

.1 Creationofasubscription

14

.2 Modificationofasubscription

14

UnsubscribeServiceOperation

15

.1 General

15

NotifyServiceOperation

16

.1 General

16

DeleteServiceOperation

16

.1 General

16

OptionsServiceOperation

17

.1 General

17

6 APIDefinitions

17

6.1 Nnssf_NSSelectionServiceAPI

17

6.1.1 APIURI

17

6.1.2 UsageofHTTP

18

General

18

HTTPstandardheaders

18

.1 General

18

.2 Contenttype

18

.1 General

18

6.1.3 Resources

18

Overview

18

Resource:NetworkSliceInformation

19

.1 Description

19

.2 ResourceDefinition

19

.3 ResourceStandardMethods

19

.3.1 GET

19

.4 ResourceCustomOperations

22

6.1.4 CustomOperationswithoutassociatedresources

22

6.1.5 Notifications

22

6.1.6 DataModel

22

General

22

Structureddatatypes

23

.1 Introduction

23

.2 Type:AuthorizedNetworkSliceInfo

24

.3 Type:SubscribedSnssai

26

.4 Void

27

.5 Type:AllowedSnssai

27

.6 Type:AllowedNssai

27

.7 Type:NsiInformation

27

.8 Type:MappingOfSnssai

27

.9 Void

28

.10 Type:SliceInfoForRegistration

28

.11 Type:SliceInfoForPDUSession

30

.12 Type:ConfiguredSnssai

30

.13 Type:SliceInfoForUEConfigurationUpdate

31

Simpledatatypesandenumerations

31

.1 Introduction

31

.2 Simpledatatypes

31

.3 Enumeration:RoamingIndication

31

Binarydata

32

6.1.7 ErrorHandling

32

General

32

ProtocolErrors

32

ApplicationErrors

32

6.1.8 Featurenegotiation

32

6.1.9 Security

33

6.1.10 HTTPredirection

33

6.2 Nnssf_NSSAIAvailabilityServiceAPI

33

6.2.1 APIURI

33

6.2.2 UsageofHTTP

34

General

34

HTTPstandardheaders

34

.1 General

34

.2 Contenttype

34

.3 Accept-Encoding

34

HTTPcustomheaders

34

.1 General

34

6.2.3 Resources

35

Overview

35

Resource:NSSAIAvailabilityDocument

36

.1 Description

36

.2 ResourceDefinition

36

.3 ResourceStandardMethods

36

.3.1 PUT

36

.3.2 PATCH

38

.3.3 DELETE

40

Resource:NSSAIAvailabilityNotificationSubscriptionsCollection

41

.1 Description

41

.2 ResourceDefinition

41

.3 ResourceStandardMethods

41

.3.1 POST

41

Resource:IndividualNSSAIAvailabilityNotificationSubscriptions

43

.1 Description

43

.2 ResourceDefinition

43

.3 ResourceStandardMethods

43

.3.1 DELETE

43

.3.2 PATCH

44

Resource:NSSAIAvailabilityStore

45

.1 Description

45

.2 ResourceDefinition

46

.3 ResourceStandardMethods

46

.3.1 OPTIONS

46

6.2.4 CustomOperationswithoutassociatedresources

47

6.2.5 Notifications

48

General

48

NSSAIAvailabilityNotification

48

.1 Description

48

.2 NotificationDefinition

48

.3 NotificationStandardMethods

48

.3.1 POST

48

6.2.6 DataModel

49

General

49

Structureddatatypes

50

.1 Introduction

50

.2 Type:NssaiAvailabilityInfo

50

.3 Type:SupportedNssaiAvailabilityData

51

.4 Type:AuthorizedNssaiAvailabilityData

51

.5 Type:RestrictedSnssai

52

.6 Type:AuthorizedNssaiAvailabilityInfo

52

.7 Type:PatchDocument

52

.8 Type:NssfEventSubscriptionCreateData

53

.9 Type:NssfEventSubscriptionCreatedData

54

.10 Type:NssfEventNotification

54

Simpledatatypesandenumerations

55

.1 Introduction

55

.2 Simpledatatypes

55

.3 Enumeration:NssfEventType

55

Binarydata

55

6.2.7 ErrorHandling

55

General

55

ProtocolErrors

55

ApplicationErrors

55

6.2.8 Featurenegotiation

56

6.2.9 Security

57

6.2.10 HTTPredirection

57

AnnexA(normative):OpenAPIspecification

59

A.1 General

59

A.2 Nnssf_NSSelectionAPI

59

A.3 Nnssf_NSSAIAvailabilityAPI

63

AnnexB(informative):Changehistory

73

Foreword

ThisTechnicalSpecificationhasbeenproducedbythe3rdGenerationPartnershipProject(3GPP).

ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithintheTSGandmaychangefollowingformalTSGapproval.ShouldtheTSGmodifythecontentsofthepresentdocument,itwillbere-releasedbytheTSGwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:

Versionx.y.z

where:

x thefirstdigit:

1 presentedtoTSGforinformation;

2 presentedtoTSGforapproval;

3 orgreaterindicatesTSGapproveddocumentunderchangecontrol.

y theseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.

z thethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthedocument.

Inthepresentdocument,modalverbshavethefollowingmeanings:

shall indicatesamandatoryrequirementtodosomething

shallnot indicatesaninterdiction(prohibition)todosomething

Theconstructions"shall"and"shallnot"areconfinedtothecontextofnormativeprovisions,anddonotappearinTechnicalReports.

Theconstructions"must"and"mustnot"arenotusedassubstitutesfor"shall"and"shallnot".Theiruseisavoidedinsofaraspossible,andtheyarenotusedinanormativecontextexceptinadirectcitationfromanexternal,referenced,non-3GPPdocument,orsoastomaintaincontinuityofstylewhenextendingormodifyingtheprovisionsofsuchareferenceddocument.

should indicatesarecommendationtodosomething

shouldnot indicatesarecommendationnottodosomething

may indicatespermissiontodosomething

neednot indicatespermissionnottodosomething

Theconstruction"maynot"isambiguousandisnotusedinnormativeelements.Theunambiguousconstructions"mightnot"or"shallnot"areusedinstead,dependinguponthemeaningintended.

can indicatesthatsomethingispossible

cannot indicatesthatsomethingisimpossible

Theconstructions"can"and"cannot"arenotsubstitutesfor"may"and"neednot".

will indicatesthatsomethingiscertainorexpectedtohappenasaresultofactiontakenbyanagencythebehaviourofwhichisoutsidethescopeofthepresentdocument

willnot indicatesthatsomethingiscertainorexpectednottohappenasaresultofactiontakenbyanagencythebehaviourofwhichisoutsidethescopeofthepresentdocument

might indicatesalikelihoodthatsomethingwillhappenasaresultofactiontakenbysomeagencythebehaviourofwhichisoutsidethescopeofthepresentdocument

mightnot indicatesalikelihoodthatsomethingwillnothappenasaresultofactiontakenbysomeagencythebehaviourofwhichisoutsidethescopeofthepresentdocument

Inaddition:

is (oranyotherverbintheindicativemood)indicatesastatementoffact

isnot (oranyothernegativeverbintheindicativemood)indicatesastatementoffact

Theconstructions"is"and"isnot"donotindicaterequirements.

1 Scope

Thepresentdocumentspecifiesthestage3protocolanddatamodelfortheNnssfServiceBasedInterface.Itprovidesstage3protocoldefinitionsandmessageflows,andspecifiestheAPIforeachserviceofferedbytheNSSF.

The5GSystemstage2architectureandproceduresarespecifiedin3GPP

TS

23.501

[2]and

3GPP

TS

23.502

[3].

TheTechnicalRealizationoftheServiceBasedArchitectureandthePrinciplesandGuidelinesforServicesDefinitionarespecifiedin3GPP

TS

29.500

[4]and

3GPP

TS

29.501

[5].

2 References

Thefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.

- Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornonspecific.

- Foraspecificreference,subsequentrevisionsdonotapply.

- Foranon-specificreference,thelatestversionapplies.Inthecaseofareferencetoa3GPPdocument(includingaGSMdocument),anon-specificreferenceimplicitlyreferstothelatestversionofthatdocumentinthesameReleaseasthepresentdocument.

[1] 3GPP

TR

21.905:"Vocabularyfor3GPPSpecifications".

[2] 3GPP

TS

23.501:"SystemArchitectureforthe5GSystem;Stage2".

[3] 3GPP

TS

23.502:"Proceduresforthe5GSystem;Stage2".

[4] 3GPP

TS

29.500:"5GSystem;TechnicalRealizationofServiceBasedArchitecture;Stage3".

[5] 3GPP

TS

29.501:"5GSystem;PrinciplesandGuidelinesforServicesDefinition;Stage3".

[6] OpenAPI:"OpenAPISpecificationVersion3.0.0",

/oas/v3.0.0

.

[7] 3GPP

TS

29.571:"5GSystem;CommonDataTypesforServiceBasedInterfaces;Stage3".

[8] IETF

RFC

6902:"JavaScriptObjectNotation(JSON)Patch".

[9] 3GPP

TS

23.003:"Numbering,addressingandidentification".

[10] IETF

RFC

7540:"HypertextTransferProtocolVersion2(HTTP/2)".

[11] 3GPP

TS

33.501:"Securityarchitectureandproceduresfor5Gsystem".

[12] IETF

RFC

6749:"TheOAuth2.0AuthorizationFramework".

[13] 3GPP

TS

29.510:"NetworkFunctionRepositoryServices;Stage3".

[14] IETF

RFC

8259:"TheJavaScriptObjectNotation(JSON)DataInterchangeFormat".

[15] IETF

RFC

7807:"ProblemDetailsforHTTPAPIs".

[16] IETF

RFC

1952:"GZIPfileformatspecificationversion4.3".

[17] 3GPP

TR

21.900:"TechnicalSpecificationGroupworkingmethods".

[18] IETFRFC7231:"HypertextTransferProtocol(HTTP/1.1):SemanticsandContent".

[19] IETFRFC7694:"HypertextTransferProtocol(HTTP)Client-InitiatedContent-Encoding".

[20] 3GPP

TS

24.501:"Non-Access-Stratum(NAS)protocolfor5GSystem(5GS);Stage3".

3 Definitionsandabbreviations

3.1 Definitions

Forthepurposesofthepresentdocument,thetermsanddefinitionsgivenin3GPP

TR

21.905

[1]andthefollowingapply.Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,in3GPP

TR

21.905

[1].

3.2 Abbreviations

Forthepurposesofthepresentdocument,theabbreviationsgivenin3GPP

TR

21.905

[1]andthefollowingapply.Anabbreviationdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameabbreviation,ifany,in3GPP

TR

21.905

[1].

4 Overview

4.1 Introduction

Withinthe5GC,theNSSFoffersservicestotheAMFandNSSFinadifferentPLMNviatheNnssfservicebasedinterface(see3GPP

TS

23.501

[2]and3GPP

TS

23.502

[3]).

Figure4.1-1providesthereferencemodel(inservicebasedinterfacerepresentationandinreferencepointrepresentation),withfocusontheNSSFandthescopeofthepresentspecification.

Figure4.1-1:NSSFin5GSystemarchitecture

ThefunctionalitiessupportedbytheNSSFarelistedinclause6.2.14of3GPP

TS

23.501

[2].

5 ServicesofferedbytheNSSF

5.1 Introduction

TheNSSFsupportsthefollowingservices.

Table5.1-1:NFServicesprovidedbyNSSF

ServiceName

Description

ExampleConsumer

Nnssf_NSSelection

ThisserviceenablesNetworkSliceselectioninboththeServingPLMNandtheHPLMN

AMF,V-NSSF

Nnssf_NSSAIAvailability

ThisserviceenablestoupdatetheS-NSSAI(s)theNFserviceconsumer(e.gAMF)supportsonaperTAbasisontheNSSFandtosubscribeandnotifyanychangeinstatus,onaperTAbasis,oftheSNSSAIsavailableperTA(unrestricted)andtherestrictedS-NSSAI(s)perPLMNinthatTAintheservingPLMNoftheUE.

AMF

Table5.1-2summarizesthecorrespondingAPIsdefinedforthisspecification.

Table5.1-2:APIDescriptions

ServiceName

Clause

Description

OpenAPISpecificationFile

apiName

Annex

Nnssf_NSSelection

6.1

NSSFNetworkSliceSelectionService

TS29531_Nnssf_NSSelection.yaml

nnssf-nsselection

A.2

Nnssf_NSSAIAvailability

6.2

NSSFNSSAIAvailabilityService

TS29531_Nnssf_NSSAIAvailability.yaml

nnssf-nssaiavailability

A.3

5.2 Nnssf_NSSelectionService

5.2.1 ServiceDescription

TheNnssf_NSSelectionserviceisusedbyanNFServiceConsumer(e.g.AMForNSSFinadifferentPLMN)toretrievetheinformationrelatedtonetworksliceinthenon-roamingandroamingcase.ItalsoenablestheNSSFtoprovidetotheAMFtheAllowedNSSAIandtheConfiguredNSSAIfortheServingPLMN.TheNFserviceconsumerdiscoverstheNSSFbasedonthelocalconfiguration.TheNSSFinadifferentPLMNisdiscoveredbasedontheself-constructedFQDNasspecifiedin3GPP

TS

23.003

[9].

5.2.2 ServiceOperations

Introduction

FortheNnssf_NSSelectionservicethefollowingserviceoperationsaredefined:

- Get.

GET

.1 General

TheGetoperationshallbeinvokedbytheAMFinthenon-roamingorroamingscenariotoretrieve:

- ThesliceselectioninformationincludingtheallowedNSSAI,ConfiguredNSSAI,targetAMFSetorthelistofcandidateAMF(s),andoptionally

- TheMappingOfAllowedNSSAI;

- TheMappingOfConfiguredNSSAI;

- NSIID(s)associatedwiththeNetworkSliceinstancesoftheAllowedNSSAI;

- NRF(s)tobeusedtoselectNFs/serviceswithintheselectedNetworkSliceinstance(s)andNRFtobeusedtodeterminethelistofcandidateAMF(s)fromtheAMFSet,duringRegistrationprocedureand

- InformationonwhethertheS-NSSAI(s)notincludedintheAllowedNSSAIwhichwerepartoftheRequestedNSSAIarerejectedintheservingPLMNorinthecurrentTA.

- TheNRFtobeusedtoselectNFs/serviceswithintheselectednetworksliceinstance,andoptionallytheNSIIDassociatedwiththeS-NSSAIprovidedintheinput,duringthePDUSessionEstablishmentprocedure.

- TheslicemappinginformationincludingthemappingofS-NSSAI(s)oftheVPLMNtocorrespondingHPLMNS-NSSAI(s).

TheGetoperationshallalsobeinvokedbythevNSSFintheroamingscenariotoretrieve:

- ThehNRFtobeusedtoselectNFs/serviceswithintheselectednetworksliceinstanceintheHPLMN,andoptionallytheNSIIDassociatedwiththeS-NSSAIprovidedintheinput,duringthePDUSessionEstablishmentprocedure.

Itisusedinthefollowingprocedures:

- RegistrationwithAMFre-allocation(seeclause

.3of3GPP

TS

23.502

[3]);

- EPSto5GShandoverusingN26interface(seeclause

.2of3GPP

TS

23.502

[3]);

- EPSto5GSmobilityregistrationprocedure(seeclauses.3,.3A,.4and4.23.12of3GPP

TS

23.502

[3]);

- XnandN2HandoverprocedureswithPLMNchange(seeclauses4.9.1,4.23.7and4.23.11of3GPP

TS

23.502

[3]);

- UEConfigurationUpdateprocedure(seeclauseof3GPP

TS

23.502

[3]);

- SMFselectionfornon-roamingandroamingwithlocalbreakout(seeclause

.3.2of3GPP

TS

23.502

[3])orSMFselectionforhome-routedroamingscenario(seeclause

.3.3of3GPP

TS

23.502

[3]).

NOTE: Thelistofproceduresabove,whichtriggerinvokingoftheNnssf_NSSelection_Getserviceoperation,isnotexhaustive.

.2 GetserviceoperationofNnssf_NSSelectionservice

Inthisprocedure,theNFServiceConsumer(e.g.AMF)retrievesthesliceselectioninformationincludingtheAllowedNSSAI,ConfiguredNSSAI,targetAMFSetorthelistofcandidateAMF(s)andotheroptionalinformation.

ThisserviceoperationshallalsobeusedtoretrievetheslicemappinginformationincludingthemappingofS-NSSAI(s)oftheVPLMNtocorrespondingHPLMNS-NSSAI(s)duringinter-PLMNmobilityprocedure.

Figure.2-1:Retrievethenetworksliceinformationduringthemobilityprocedure

1 TheAMFshallsendaGETrequesttotheNSSF.

IftheAMFwantstoretrievethesliceselectioninformation,oneormoreofthefollowingparametersshallbeincludedasqueryparameters:RequestedNSSAIandSubscribedS-NSSAI(s)withtheindicationifmarkedasdefaultS-NSSAIincludedintheslice-info-request-for-registration,PLMNIDoftheSUPI,TAI,NFtypeoftheNFserviceconsumer,RequesterID.

IftheAMFwantstoretrievetheslicemappinginformation,thefollowingparametersshallbeincludedasqueryparameters:sNssaiForMappingIEandrequestMappingIEincludedintheslice-info-request-for-registration,PLMNIDoftheSUPI,TAI,NFtypeoftheNFserviceconsumerandRequesterID.

2a Onsuccess,"200OK"shallbereturnedwhentheNSSFisabletofindauthorizednetworksliceinformationfortherequestednetworksliceselectioninformation,theresponsebodyshallincludeapayloadbodycontainingatleasttheAllowedNSSAI,targetAMFSetorthelistofcandidateAMF(s);thepayloadbodymayadditionallycontainatargetAMFServiceSet."200OK"shallalsobereturnedwhentheNSSFisabletofindtherequestedslicingmappinginformation,theresponsebodyshallincludeapayloadbodycontainingthemappingofS-NSSAI(s)oftheVPLMNtocorrespondingHPLMNS-NSSAI(s)includedintheallowedNssaiListIE.

2b Ifnosliceinstancescanbefoundfortherequestedsliceselectioninformationortherequestedslicemappinginformation,thentheNSSFshallreturna403Forbiddenresponsewiththe"ProblemDetails"IEcontainingtheApplicationError"SNSSAI_NOT_SUPPORTED"(cf.Table-1).

Onfailureorredirection,theNSSFshallreturnoneoftheHTTPstatuscodestogetherwiththeresponsebodylistedinTable.3.1-3.

.3 GetserviceoperationofNnssf_NSSelectionserviceduringthePDUsessionestablishment

Inthisprocedure,theNFServiceConsumer(e.g.AMF)retrievestheNRFandtheoptionallytheNSIIDofthenetworksliceinstance:

Figure.3-1:RetrievethenetworksliceinformationduringthePDUsessionestablishmentprocedure

1 TheNFServiceconsumer(e.g.AMForNSSFinthedifferentPLMN)shallsendaGETrequesttotheNSSF.Therequestshallincludequeryparameters,containatleastS-NSSAI,S-NSSAIfromtheHPLMNthatmapstotheS-NSSAIfromtheAllowedNSSAIoftheServingPLMN,theNFtypeoftheNFserviceconsumer,RequesterIDandnon-roaming/LBOroaming/HRroamingindication.FortherequesttowardsanNSSFintheServingPLMN,thequeryparametersshallalsocontainthePLMNIDoftheSUPIandTAI.

2a Onsuccess,"200OK"shallbereturnedwhentheNSSFisabletofindnetworksliceinstanceinformationfortherequestednetworksliceselectioninformation,theresponsebodyshallincludeapayloadbodycontainingatleasttheNRFtobeusedtoselectNFs/serviceswithintheselectedNetworkSliceinstance;

2b Ifnosliceinstancescanbefoundfortherequestedsliceselectioninformation,thentheNSSFshallreturna403Forbiddenresponsewiththe"ProblemDetails"IEcontainingtheApplicationError"SNSSAI_NOT_SUPPORTED"(cf.Table-1).

Onfailureorredirection,theNSSFshallreturnoneoftheHTTPstatuscodestogetherwiththeresponsebodylistedinTable.3.1-3.

.4 GetserviceoperationofNnssf_NSSelectionserviceduringUEconfigurationupdateprocedure

Inthisprocedure,theNFServiceConsumer(e.g.AMF)retrievesnetworksliceconfigurationinformation(e.g.theAllowedNSSAIandtheConfiguredNSSAI)duringtheUEconfigurationupdateprocedure.

Figure.4-1:RetrievethenetworksliceinformationduringUEconfigurationupdateprocedure

1 TheNFServiceconsumer(e.g.AMF)shallsendaGETrequesttotheNSSF.Therequestshallincludequeryparameters:SubscribedS-NSSAI(s)withtheindicationiftheS-NSSAIismarkedasdefaultS-NSSAI,PLMNIDoftheSUPI,TAI,NFtypeoftheNFserviceconsumerandtheNFinstanceIDoftherequesterNF.

2a Onsuccess,"200OK"shallbereturnedwhentheNSSFisabletofindauthorizednetworksliceinformationfortherequestednetworksliceselectioninformation,theresponsebodyshallincludeapayloadbodycontainingatleasttheAllowedNSSAI,ConfiguredNSSAI;

2b Ifnosliceinstancescanbefoundfortherequestedsliceselectioninformation,thentheNSSFshallreturna403Forbiddenresponsewiththe"ProblemDetails"IEcontainingtheApplicationError"SNSSAI_NOT_SUPPORTED"(cf.Table-1).

Onfailureorredirection,theNSSFshallreturnoneoftheHTTPstatuscodestogetherwiththeresponsebodylistedinTable.3.1-3.

5.3 Nnssf_NSSAIAvailabilityService

5.3.1 ServiceDescription

TheNnssf_NSSAIAvailabilityserviceisusedbytheNFserviceconsumer(e.gAMF)toupdatetheS-NSSAI(s)theAMFsupportsonaperTAbasisontheNSSF,subscribeandunsubscribethenotificationofanychangestotheNSSAIavailabilityinformationonaperTAbasis,oftheS-NSSAIsavailableperTA(unrestricted)andtherestrictedS-NSSAI(s)perPLMNinthatTAintheservingPLMNofoftheUE.

5.3.2 ServiceOperations

Introduction

FortheNnssf_NSSAIAvailabilityservicethefollowingserviceoperationsaredefined:

- Update;

- Subscribe;

- Unsubscribe;

- Notify;

- Delete;

- Options.

UpdateServiceOperation

.1 General

TheUpdateoperationshallbeusedbyanNFServiceConsumer(e.g.AMF)toupdatetheNSSFwiththeS-NSSAIstheNFserviceconsumer(e.g.AMF)supportsperTA,andgettheavailabilityoftheS-NSSAIsperTAfortheS-NSSAIs