5G終端切片測試框架定義

DEFINITIONOFTHETESTINGFRAMEWORKFOR5GDEVICENETWORKSLICINGPRE-COMMERCIALTRIALSbyNGMNAllianceVersion:1.0Date:24.01.2022DocumentType:ConfidentialityClass:FinalDeliverable(approved)P-PublicProject:NetworkSlicingforOperatingSystemsof5GSmartPhonesEditor/Submitter:Contributors:DanniSong(ChinaMobile)HuHao(Anritsu),JonathanBorrill(Anritsu),JavanErfanian(Bell),AitongHan(ChinaMobile),ChenguangJin(ChinaMobile),DanniSong(ChinaMobile),LutingKong(ChinaMobile),JakobBelschner(DeutscheTelekom),LudgerVerhaag(DeutscheTelekom),MarcusMüller-Jung(DeutscheTelekom),MaokiHikosaka(NTTDOCOMO),MasahiroTamaoki(NTTDOCOMO),VidaChen(Ericsson),AmolTuli(Google),RaymondCheung(HKT),StanWong(HKT),GaryLi(Intel),DustinFan(MediaTek),XiliangYue(MediaTek),AntoineMouquet(Orange),KennyZhang(Qualcomm),TimothySenathirajah(Smart/PLDT),KyungsikHan(SKT),GiulioColombo(TIM),CemilKarakus(Turkcell),QianqianLv(Unisoc),ZhenzhenSu(Unisoc),ShiyangZheng(ZTE)Approvedby/Date:NGMNBoard,9thFebruary2022DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page1(84)?2022NextGenerationMobileNetworkse.V.Allrightsreserved.NopartofthisdocumentmaybereproducedortransmittedinanyformorbyanymeanswithoutpriorwrittenpermissionfromNGMNe.V.TheinformationcontainedinthisdocumentrepresentsthecurrentviewheldbyNGMNe.V.ontheissuesdiscussedasofthedateofpublication.Thisdocumentisprovided“asis”withnowarrantieswhatsoeverincludinganywarrantyofmerchantability,non-infringement,orfitnessforanyparticularpurpose.Allliability(includingliabilityforinfringementofanypropertyrights)relatingtotheuseofinformationinthisdocumentisdisclaimed.Nolicense,expressorimplied,toanyintellectualpropertyrightsaregrantedherein.Thisdocumentisdistributedforinformationalpurposesonlyandissubjecttochangewithoutnotice.Readersshouldnotdesignproductsbasedonthisdocument.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page2(84)AbstractThe5Gnetworkslicingcanprovideon-demandnetworkslicestosatisfydifferentservicerequirements.However,howtoguaranteethenetworkslicingservicequalityof5Gdevicesbythenetworkslicingtestbasedontheactualnetworkelementsisstillatechnicalgaptobeaddressed.Therefore,thefundamentalpurposeofthisdocumentistoprovideatestingframeworkfor5Gdevicenetworkslicingpre-commercialtrialsbasedontheactualnetworkelements,whichincludethetestcasesoftheconfigurationandusageofNSSAI,UErouteselectionpolicy,interworkingwithEPCandotherservicespecificnetworkslicingtestcases.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page3(84)Contents123Introduction6Scope7TrialSetupRequirements73.1NetworkArchitectureandConfiguration7TestToolRequirements9TestReportRequirements93.23.34CommonRequirementsforNetworkSlicingTrial104.1TheConfigurationandUsageofNSSAI10NSSAIHandlinginInitialRegistration10NSSAIHandlingduringMobilityRegistrationUpdate12DefaultConfiguredNSSAIPre-configurationandUpdate14GenericUEConfigurationUpdateforNSSAI16NSSAIInclusionModeA17NSSAIInclusionModeB22NSSAIInclusionModeC26NSSAIInclusionModeD30UERouteSelectionPolicy35URSPConfigurationinInitialRegistration35UpdateandDeleteofURSP37TrafficDescriptorsinURSPAPPID40TrafficDescriptorsinURSPDNN42TrafficDescriptorsinURSPIP45TrafficDescriptorsinURSPIP3Tuple47TrafficDescriptorsinURSPFQDN49TrafficDescriptorsinURSPOSID+OSAPPID51TrafficDescriptorsinURSPMatch-all594.2.10Multi-dimensionalMatchinginURSP564.3InterworkingwithEPC67Handoverfrom5GCtoEPC67RedirectionfromEPCto5GC70HandoverfromEPCto5GC72Handoverfrom5GCtoEPC,thenRedirectionbackto5GC7..4DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page4(84)4.3.5Handoverfrom5GCtoEPC,thenHandoverbackto5GC775ServiceSpecificRequirementsforNetworkSlicingTrial785.1FTP/SpeedtestDownloadService78TestObjective78Pre-configuration78TestProcedure78SuccessCriteria79VideoService79TestObjective79Pre-configuration79TestProcedure80SuccessCriteria80CloudGamingService81TestObjective81Pre-configuration81TestProcedure82SuccessCriteria84ListofAbbreviations83References84DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page5(84)1INTRODUCTIONTheNGMNNetworkSlicingforOperatingSystemsof5GSmartPhonesprojectwaskickedoffin2020.Aftermorethanhalfayearofresearchandanalysis,the“5GSmartDevicesSupportingNetworkSlicing”WhitePaper[1]waspublishedjointlywithGTIinJanuary2021.BasedonthisWhitePaper,NGMNsendsaLiaisonto3GPPRAN5tostresstheimportanceofthenetworkslicingtesting.AlthoughanewWorkItemonUEConformanceTestAspectsforEnhancementofNetworkSlicingandanewStudyItemon5GNRUEsupportingNetworkSlicingTestinghavebeenendorsedbyRAN5,whatisdiscussedandanalysedinRAN5isstilltheconformancetestofnetworkslicingbytestequipment.Sometests,suchasnetworkslicingtestsbasedontheactualnetworkelements,arenotincludedin3GPPRAN5.Butthesetestsarestillnecessarytoensurethecommercialsuccessofnetworkslicing.Furthermore,theindustryhasademandfornetworkslicingtesting,andUEvendorsandnetworkprovidersarecapabledoingthenetworkslicingtest.Therefore,itisnecessarytoperformthenetworkslicingtestinginNGMNandGTIbasedontheactualnetworkelements,whichwillprovidevaluablefeedbackandinputto3GPPandtheindustry.TheprojectfocusesontheNetworkSlicingTrialsbasedontheactualnetworkelements,andhasthefollowingscope:???Developingatestingframeworkfor5GNetworkSlicingDevices,whichallowstheharmonisationofthetestingmethodologiesamongdifferentpartiesconductingtrials;Testing5GNetworkslicingcapabilitiesbylabtest/fieldtrialswithdifferentkindsofdevices,e.g.smartphones,modem;Consolidatingtheresultsfromdifferentindustryplayersanddrawingconclusions.Analysingthetestingconclusionsandbringingobservationsthatcouldleadtofutureimprovement.ThemainpurposeoftheprojectistoassessthefunctionalityandperformanceofNetworkSlicingimplementationin5GDevicesbasedonRelease15andforwardofthe5GNRstandardisationbylabtest/fieldtrials,soastoensuretheuserexperience.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page6(84)2SCOPEThisframeworkdocumentisstructuredinthreeparts:1.Trialsetuprequirements2.Commonrequirementsfornetworkslicingtrial3.ServicespecificrequirementsfornetworkslicingtrialThetrialsetuprequirementssectionintroducesthetrialenvironmentrequirements,suchasthenetworkarchitectureandconfiguration,thetesttoolrequirements,andthereportingrequirements.Thecommonrequirementsfornetworkslicingtrialsectiondefinethetestcasesofnetworkslicingin5Gdevices,suchastheconfigurationandusageofNSSAI,UERouteSelectionPolicyandInterworkingwithEPC.Eachtestcaseincludesthetestobjective,pre-configuration,testprocedureandsuccesscriteria.Theservicespecificrequirementsfornetworkslicingtrialsectiondefinestheserviceperformancetestsofnetworkslicingin5Gdevices,suchasthevideoservice,thecloudgamingserviceandFTP/speedtestdownloadservice.Eachtestcaseincludesthetestobjective,pre-configuration,testprocedureandsuccesscriteriaforspecificservices.3TRIALSETUPREQUIREMENTS3.1NetworkArchitectureandConfigurationThepre-commercialnetworkslicingtrialswillprimarilyaimattestingnetworkslicingin5Gdevicesusingactualnetworkelementstoreflectthefunctionalityandperformanceofdevicesinamorerealisticenvironmentformoremeaningfulresults.Thenetworkslicingtrialsinthisprojectaredifferentfromthe5Gpre-commercialtrials.The5Gpre-commercialtrialsfocusonwhethertheperformanceparameters,suchaslatency,userthroughput,cellcapacity,andcoverage,meettherequirements.The5GdevicenetworkslicingtrialsinthisprojectfocusonthesignallingaspectandwhetherthenetworkanddevicecansuccessfullydealwiththeconfigurationofNSSAI,theUErouteselectionpolicyandtheinterworkingwithEPC.Thedeploymentscenariosarenotmainconsiderationsinthisversionofthedocumentandneedtobedeterminedaccordingtotheactualtestenvironment.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page7(84)The5Gdevicenetworkslicingtrialisanend-to-endtest.Thetestenvironmentrequiresthecells/sites,corenetwork,UEsandsignallinganalysistools.Thesiteneedstobea5GNRsitesothattheUEcanaccessthecorenetworkthroughthisNRsite.Thecorenetworkshouldbea5Gcorenetwork,anditsnetworkelements--AMF,SMF,PCF,NSSFandothersneedtohavetheabilitytosupportnetworkslicing(whichismandatoryper3GPPRel-15specifications).Figure1:OverallArchitectureNote:Formoredetails,pleasesee[2].TheUEsusedinthistrialaretestUEs,notcommercialUEs.Forthistrial,thetestUEsincludethesmartUEsandnon-smartUEs.ThesmartUEsincludethesmartphonesandotherdeviceswithoperatingsystems,whilethenon-smartUEsincludetheModemandCPEs.Table1:TestEnvironmentRequirementsTestEnvironmentRequirementsCells/SitesTestEnvironmentSetupNotesAtleasttwositesThesesitesshouldincludeonesiteforNRandonesiteforLTE.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page8(84)NetworkelementsNSSFThe5Gcorenetworkshouldhavetheabilitytosupportnetworkslicingfeature.Ifnot,therelatednetworkelementsof5Gcorenetworkshouldbeupdatedtotheversionwhichsupportsthenetworkslicingfeature.SMFPCFAMFUDMTherequirementofthenumberofcells/siteswillvaryindifferenttestcases.FortestcasesrelatedtoNSSAIandURSPscenarios,oneNRsiteissufficient.FortestcasesrelatedtointerworkingwithEPC,atleasttwositesarerequired,i.e.oneforNRandoneforLTE.3.2TestToolRequirementsInordertoobservewhethertheUEcansuccessfullyhandletheconfigurationofNSSAI,theUErouteselectionpolicyandtheinterworkingwithEPCforsignallingaspects,thistestrequiresthevendorstoprovideappropriatesignallinganalysistoolstoanalyseNASlayersignalling,andanappropriatetooltosimulateAPPsorrealAPP.Table2:TestToolRequirementsToolsLogicalNetworkElementNameAPPNumbersNotesApplicationAnalysistoolAtleasttwoforeachUEoneAnappropriatetooltosimulateAPPsorrealAPPAnalyseNASlayersignallingmessage.SimulatinganoverloadednetworkAnalysistoolIperfNetworkperformancetesttoolone3.3TestReportRequirementsThetrialreportingisaveryimportantphaseforthetrial.Inordertoprovideanalyticallyvaluabletestresults,itisnecessarytoprovideabenchmarkforthetestcasesforthecomparisonoftestresults.Hence,contributorsareencouragedtoprovideasmanydetailsaspossibleabouttheirtrials.Thefollowingaspectsneedtobecoveredinthetrialreporting.1.TrialsetupinformationThefollowingdeploymentparametersneedtobereportedforeachtrial:DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page9(84)??????FrequencybandOperatingbandwidthNumberofsitesTypeoftestUEs(smartphones,modem,CPE…)Networkelements(RAN,corenetwork)……2.TrialresultinformationContributorsarerequiredtoprovidetestresultsrelatedinformation,includingtestlog,testresultsanalysis,etc.3.TrialresultbenchmarkDefiningthebenchmarkstoevaluatetheperformanceof5Gnetworkslicingisverycrucial.Forthenetworkslicingsignallingtest,using5GNRRel.15asabenchmarkisanoption.Forthenetworkslicingperformancetest,thebenchmarkistheperformanceofthesamekindofapplicationwithoutnetworkslicing.Ideally,thebenchmarkisbasedonthesametestenvironment/condition,suchasthebenchmarkapplicationhasthesamesetupparametersandthesametestenvironmentwiththetestapplication.TheonlydifferenceisthatthetestapplicationisimplementedinthespecificnetworksliceaccordingtotheUEsubscription,whilethebenchmarkapplicationisimplementedinthedefaultnetworkslice.However,thedifferenttestenvironment/conditionbetweenbenchmarkandtestapplicationcouldalsobeacceptableaslongasthedifferencesarewelldescribed.4COMMONREQUIREMENTSFORNETWORKSLICINGTRIAL4.1TheConfigurationandUsageofNSSAI4.1.1NSSAIHandlinginInitialRegistrationTestObjectiveThepurposeofthistestcaseistoverifytheUEcansuccessfullyperformtheinitialregistrationtothe5Gsystemwithout/withRequestedNSSAIandsupportofConfiguredNSSAI/AllowedNSSAI/RejectedNSSAIfornetworkslicing.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page10(84)Pre-configurationNW:––5GCCellAbelongstoHomePLMN;SubscribedS-NSSAIsareconfiguredforUE,theConfiguredNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)canbegeneratedforUE.UE:––ThetestUICCwithUSIMshouldbeinserted;UEhasnostoredallowedNSSAIforthecurrentPLMN,noconfiguredNSSAIforthecurrentPLMN,andnodefaultconfiguredNSSAI;TheUEisinstateSwitchedOFF.–TestProcedure1.SwitchonUE;2.TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure;3.TheNWsendsaREGISTRATIONACCEPTmessageincludingConfiguredNSSAI;4.SwitchoffUE;5.Fromnetworkside,removeS-NSSAI-3fromtheUE'ssubscriptioninformationintheUDM,sothattheAllowedNSSAI(S-NSSAI1andS-NSSAI2)andtheRejectedNSSAI(S-NSSAI3)canbegeneratedfortheUEinthisregistrationarea;6.SwitchonUE;7.TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure;8.TheNWsendsaREGISTRATIONACCEPTmessageincludingAllowedNSSAIandRejectedNSSAI;9.UseMMI/ATcommand(+C5GNSSAIRDP)orothermethodtoverifytheAllowedNSSAIandRejectedNSSAIstoredinUE;10.SwitchoffUE,thenswitchonUE;11.TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure.Table3:MainMessageFlowforNSSAIHandlinginInitialRegistrationDirectionUE-NWStepMessageCommentsRegistrationtype“initialregistration”NOTincludingRequestedNSSAI2-->REGISTRATIONREQUESTDefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page11(84)IncludingConfiguredNSSAI(S-NSSAI1,S-NSSAI2andS-NSSAI3)Registrationtype“initialregistration”;37<>REGISTRATIONACCEPTREGISTRATIONREQUESTincludingRequestedNSSAIIncludingAllowedNSSAI(S-NSSAI1andS-NSSAI2),ConfiguredNSSAI(S-NSSAI1,S-NSSAI2)andRejectedNSSAI(S-NSSAI3)8<>REGISTRATIONACCEPTREGISTRATIONREQUESTRegistrationtype“initialregistration”;11includingRequestedNSSAINote:TheAllowedNSSAIistheintersectionoftherequestedNSSAI,theNSSAIsupportedbytheAMF,theNSSAIsupportedbytheRAN,andtheNSSAIsubscribedbytheUE.SuccessCriteriaStep2:UEperformsinitialregistrationwithoutRequestedNSSAI;Step7:UEperformsinitialregistrationwithRequestedNSSAI,whichincludingtheS-NSSAI(s)fromtheconfiguredNSSAI(e.g.S-NSSAI1,S-NSSAI2andS-NSSAI3);Step9:UEcorrectlystoresthelatestAllowedNSSAI(S-NSSAI1andS-NSSAI2),ConfiguredNSSAI(S-NSSAI1,S-NSSAI2)andRejectedNSSAI(S-NSSAI3);Step11:UEperformsinitialregistrationwithRequestedNSSAI,whichincludingtheS-NSSAI(s)fromtheallowedNSSAI(e.g.S-NSSAI1andS-NSSAI2).4.1.2NSSAIHandlingduringMobilityRegistrationUpdateTestObjectiveThepurposeofthistestcaseistoverifytheUEcansuccessfullyperformMobilityRegistrationUpdateprocedureafterreselectingacellinanewTrackingAreaoutsideitsRegistrationArea,andtheUEshallincludetherequestedNSSAIcontainingtheS-NSSAI(s)correspondingtotheslicestowhichtheUEintendstoregister.Pre-configurationNW:–2cells,5GCCellAand5GCCellBbelongingtothesameHomePLMNbutdifferentRA;DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page12(84)–SubscribedS-NSSAIsareconfiguredforUE,AllowedNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)andConfiguredNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)canbegeneratedforUE.UE:––ThetestUICCwithUSIMshouldbeinserted;TheUEisinstateSwitchedOFF.TestProcedure1.2.OnlyCellAisON,thenswitchonUE;TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedureonCellA;3.TheNWsendsaREGISTRATIONACCEPTmessageincludingAllowedNSSAIandConfiguredNSSAI;4.5.CellBisON,andletUEmovefromtheserviceareaofCellAtoCellB;TheUEsendsaREGISTRATIONREQUESTmessageformobilityregistrationupdateonCellB.Table4:MainMessageFlowforNSSAIHandlingduringMobilityRegistrationUpdateDirectionStepMessageCommentsUE-NW2-->REGISTRATIONREQUESTRegistrationtype“initialregistration”IncludingAllowedNSSAI(S-NSSAI1,S-NSSAI2andS-NSSAI3)andConfiguredNSSAI(S-NSSAI1,S-NSSAI2andS-NSSAI3)3<>REGISTRATIONACCEPTREGISTRATIONREQUESTRegistrationtype“mobilityregistrationupdating”;5includingRequestedNSSAISuccessCriteriaStep5:UEperformsregistrationprocedureformobilityregistrationupdatewithRequestedNSSAI,whichincludingtheS-NSSAI(s)fromtheallowedNSSAIandconfiguredNSSAI(e.g.S-NSSAI1,S-NSSAI2andS-NSSAI3).DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page13(84)4.1.3DefaultConfiguredNSSAIPre-configurationandUpdateTestObjectiveThepurposeofthistestcaseistoverifytheUEcantransmitREGISTRATIONREQUESTmessagewithRequestedNSSAIusingthedefaultconfiguredNSSAIandalsoincludeNetworkslicingindication,whilethedefaultconfiguredNSSAIcanbepre-configuredinUEandupdatedbyNW.Pre-configurationNW:––5GCCellAbelongstoHomePLMN;NoSubscribedS-NSSAIconfiguredforUE.UE:––UEhasnostoredallowedNSSAIforthecurrentPLMN,noconfiguredNSSAIforthecurrentPLMN,andnodefaultconfiguredNSSAI;TheUEisinstateSwitchedOFF.TestProcedure1.2.SwitchonUE;ViaATcommandorothermethod,UEispreconfiguredwithDefaultConfiguredNSSAIasS-NSSAI1andS-NSSAI2,thenswitchoffUE;3.Fromnetworkside,configureSubscribedS-NSSAIsforUE,sothattheAllowedNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)andConfiguredNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)canbegeneratedforUE;4.5.6.SwitchonUE;TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure;TheNWsendsaREGISTRATIONACCEPTmessageincludingAllowedNSSAIandConfiguredNSSAI;7.8.Fromnetworkside,triggerstheUEParameterUpdateviaUDMControlPlanprocedure,tore-configurethedefaultconfiguredNSSAIasS-NSSAI1andS-NSSAI3;TheUEacknowledgementofsuccessfulreceptionoftheupdatedUEconfigurationparameterinformationissentbacktothenetworkusingtheUE-initiateduplinkNAStransportprocedure;9.UseMMI/ATcommand(+C5GNSSAIRDP)orothermethodtoverifytheupdateoftheDefaultConfiguredNSSAIstoredinUE.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page14(84)Table5:MainMessageFlowforDefaultConfiguredNSSAIPre-configurationandUpdateDirectionStepMessageCommentsUE-NWRegistrationtype“initialregistration”;RequestedNSSAI=S-NSSAI1,S-NSSAI2;5-->REGISTRATIONREQUESTnetworkslicingindication-->DefaultconfiguredNSSAIindication(DCNI)bit=1IncludingAllowedNSSAI(S-NSSAI1,S-NSSAI2andConfiguredNSSAI(S-NSSAI1,S-NSSAI2andS-NSSAI3)Payloadcontainertype=0110(i.e.UEparametersupdatetransparentcontainer);6<--REGISTRATIONACCEPTUEparametersupdatedatatype="0";Acknowledgement(ACK)value=1(acknowledgementrequested);UEparametersupdatedatasettype=0010(DefaultconfiguredNSSAIupdatedata);7<--DLNAStransportdefaultconfiguredNSSAI=S-NSSAI1,S-NSSAI3Payloadcontainertype=0110(i.e.UEparametersupdatetransparentcontainer);8-->ULNAStransportUEparametersupdatedatatype="1"SuccessCriteriaStep5:UEsendsREGISTRATIONREQUESTmessagewithRequestedNSSAIusingthedefaultconfiguredNSSAI(S-NSSAI1,S-NSSAI2)andalsoincludesNetworkslicingindication;DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page15(84)Step9:TheDefaultConfiguredNSSAIstoredinUEisupdatedsuccessfully,i.e.S-NSSAI1andS-NSSAIGenericUEConfigurationUpdateforNSSAITestObjectiveThepurposeofthistestcaseistoverifytheUEsupportsthegenericUEconfigurationupdateprocedureinitiatedbythenetworktoupdateConfiguredNSSAI/AllowedNSSAI/rejectedNSSAI.Pre-configurationNW:––5GCCellAbelongstoHomePLMN;SubscribedS-NSSAIsareconfiguredforUE,AllowedNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)andConfiguredNSSAI(includingS-NSSAI1,S-NSSAI2andS-NSSAI3)canbegeneratedforUE.UE:––ThetestUICCwithUSIMshouldbeinserted;TheUEisinstateSwitchedOFF.TestProcedure1.2.3.SwitchonUE;TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure;TheNWsendsaREGISTRATIONACCEPTmessageincludingAllowedNSSAIandConfiguredNSSAI;4.Fromnetworkside,initiatestheGenericUEconfigurationupdateprocedure,toupdatetheUEwiththenewConfiguredNSSAI,AllowedNSSAI;5.6.TheUEsendsaCONFIGURATIONUPDATECOMPLETEmessage;UseMMI/ATcommand(+C5GNSSAIRDP)orothermethodtoverifytheupdateofallowedNSSAIandrejectedNSSAI.Table6:MainMessageFlowforGenericUEConfigurationUpdateforNSSAIDirectionStepMessageCommentsUE-NW2-->REGISTRATIONREQUESTRegistrationtype“initialregistration”DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page16(84)includingAllowedNSSAI(S-NSSAI1,S-NSSAI2andS-NSSAI3)andConfiguredNSSAI(S-NSSAI1,S-NSSAI2andS-NSSAI3)3<--REGISTRATIONACCEPTIncludingAllowedNSSAI(S-NSSAI1,S-NSSAI2),ConfiguredNSSAI(S-NSSAI1,S-NSSAI2)andRejectedNSSAI(S-NSSAI3);CONFIGURATIONUPDATECOMMAND45<>Configurationupdateindication-->Acknowledgement(ACK)value=1CONFIGURATIONUPDATECOMPLETESuccessCriteriaStep5:UEsendsaconfirmationresponse“CONFIGURATIONUPDATECOMPLETE”toNW;Step6:UEcorrectlystorestheupdatedAllowedNSSAI(S-NSSAI1andS-NSSAI2),ConfiguredNSSAI(S-NSSAI1,S-NSSAI2)andRejectedNSSAI(S-NSSAI3).4.1.5NSSAIInclusionModeATestObjectiveThepurposeofthistestcaseistoverifytheUEsupportsNSSAIinclusionmodeAindicatedbyNW.Pre-configurationNW:––5GCCellAbelongstoHomePLMN;SubscribedS-NSSAIsareconfiguredforUE,AllowedNSSAI(includingS-NSSAI1,S-NSSAI2,S-NSSAI3,S-NSSAI4,S-NSSAI5andS-NSSAI6)andConfiguredNSSAI(includingS-NSSAI1,S-NSSAI2,S-NSSAI3,S-NSSAI4,S-NSSAI5andS-NSSAI6)canbegeneratedforUE;Settheperiodicregistrationupdatetimer(T3512)totheminimumvalue.–UE:––ThetestUICCwithUSIMshouldbeinserted;TheUEisinstateSwitchedOFF.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page17(84)TestProcedure1.2.3.SwitchonUE;TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure;TheNWsendsaREGISTRATIONACCEPTmessageincludingAllowedNSSAIandConfiguredNSSAI,andtheNSSAIinclusionmodeIEissetto“NSSAIinclusionmodeA”;SwitchoffUE,thenSwitchonUE;4.5.TheUEsendsaREGISTRATIONREQUESTmessagetoinitiatetheregistrationprocedure,checkthes-NSSAI-ListinRRCSetupCompletemessage;6.7.TheNWsendsaREGISTRATIONACCEPTmessage;Fromnetworkside,initiatesagenericUEconfigurationupdateprocedurebysendingtheCONFIGURATIONUPDATECOMMANDtotheUEwitharequesttoperformtheregistrationprocedure;8.9.TheUEsendsaCONFIGURATIONUPDATECOMPLETEmessage;WaitforNWreleasingtheexistingN1NASsignallingconnection;10.TheUEsendsaREGISTRATIONREQUESTmessageformobilityregistrationupdate,checkthes-NSSAI-ListinRRCSetupCompletemessage;11.TheNWsendsaREGISTRATIONACCEPTmessage;12.WaitforNWreleasingtheRRCconnectionduetouserinactivity,UEisin5GMM-IDLEmode;13.UsesettingmenuorengineeringmodeorothermethodtochangeUEradiocapabilityforNG-RAN,e.g.changethe5GmodefromSAmodetoSA+NSAmode,totriggerUEinitiatetheregistrationprocedureformobilityregistrationupdatebysendingaREGISTRATIONREQUESTmessage,checkthes-NSSAI-ListinRRCSetupCompletemessage;14.TheNWsendsaREGISTRATIONACCEPTmessage;15.Waitfortheperiodicregistrationupdatetimer(T3512)toexpire,UEsendsaREGISTRATIONREQUESTmessageforperiodicregistrationupdate,checkthes-NSSAI-ListinRRCSetupCompletemessage;16.TheNWsendsaREGISTRATIONACCEPTmessage;17.Initiatedatatransfer(Ping)oninternetDNN,withthePDUsessionestablishedonthedefaultnetworkslice(e.g.S-NSSAI1);18.Stopanydatatransfer,waitforNWreleasingtheRRCconnectionduetouserinactivity;19.Initiatedatatransfer(Ping)oninternetDNN,UEsendsaSERVICEREQUESTmessage,checkthes-NSSAI-ListinRRCSetupCompletemessage.DefinitionoftheTestingFrameworkfor5GDeviceNetworkSlicingPre-CommercialTrialsVersion1.0,24–January–2022Page18(84)Table7:MainMessageFlowforNSSAIInclusionModeADirectionUE-NW-->StepMessageComments2NAS:REGISTRATIONREQUESTRegistrationtype“initialregistration”IncludingAllowedNSSAI(S-NSSAI1,S-NSSAI2,S-NSSAI3,S-NSSAI4,S-NSSAI5andS-NSSAI6)andConfiguredNSSAI(S-NSSAI1,S-NSSAI2,S-NSSAI3,S-NSSAI4