Uploaded by panesar_narinder

5GC Registration Failure Codes PPT 4

advertisement
Upload
Search
5GC Registration Failure
Codes
Koorosh Hoveyda
Signup
Follow
Senior PS Core/LTE/NFV
Engineer at Huawei…
Technologies
Sep 5, 2021 • 1 like • 480 views
Login
Technology
in this doc I collected 5GC Registration Failure Codes and their Description
Read more
5GC Registration Failure Codes
Download Now
8 of 9
Recommended
2.oeo000010 lte
handover fault
diagnosis issue 1
Download to read o!line
Klajdi Husi
1.9K views • 53 slides
06a_LTE mobility
management
v1_0.ppt
ssuser022794
771 views • 124 slides
Throughput
Calculation for LTE
TDD and FDD System
Sukhvinder Singh Malik
338K views • 11 slides
Lte irattroubleshootingguide
Denmark Wilson
5.7K views • 46 slides
Volte troubleshooting
Jamil Awan
Innextpage,ImentionedFailureCausecodes
814 views • 24 slides
Save slide
andincomingpages,descriptionforeach
causecodeisexplained.
FAILURE
LTE Call Processing
and Handover
Sitha Sok
16K views • 73 slides
ItcanbeusedforOptimization,Maintenance,Monitoring
andTroubleshooting.
KOOROSH
Save for later
CauseCode
Description
Causevalue
IllegalUEin5GMMissenttotheUEwhenthenetworkrefusesservicetotheUEeitherbecauseanidentityoftheUEisnot
3
IllegalUE
acceptabletothenetworkorbecausetheUEdoesnotpasstheauthenticationcheck.UEdoesfollowingactionsupon
receivingthiscause.
TheUEshallconsidertheUSIMasinvalidfor5GSservicesuntilswitchingoffortheUICCcontainingtheUSIMisremoved
UEshalldeletethelistofequivalentPLMNsandenterthestate5GMM-DEREGISTERED
USIMshallbeconsideredasinvalidalsofornon-EPSservicesuntilswitchingoffortheUICCcontainingtheUSIMisremoved
IllegalMEissenttotheUEiftheMEusedisnotacceptabletothenetwork,e.g.blacklisted.UEdoesfollowingactionsupon
6
IllegalME
recievingthiscause.
TheUEshallconsidertheUSIMasinvalidfor5GSservicesuntilswitchingoffortheUICCcontainingtheUSIMisremoved
UEshalldeletethelistofequivalentPLMNsandenterthestate5GMM-DEREGISTERED
USIMshallbeconsideredasinvalidalsofornon-EPSservicesuntilswitchingoffortheUICCcontainingtheUSIMisremoved
This5GMMcauseissenttotheUEwhenitisnotallowedtooperate5GSservices
7
5GSservicesnotallowedTheUEshallconsidertheUSIMasinvalidfor5GSservicesuntilswitchingoffortheUICCcontainingtheUSIMisremoved
UEshalldeletethelistofequivalentPLMNsandenterthestate5GMM-DEREGISTERED
USIMshallbeconsideredasinvalidalsofornon-EPSservicesuntilswitchingoffortheUICCcontainingtheUSIMisremoved
11
PLMNnotallowed
this5GMMcauseissenttotheUEifitrequestsservice,orifthenetworkinitiatesade-registrationrequest,inaPLMN
wheretheUE,bysubscriptionorduetooperatordeterminedbarring,isnotallowedtooperate.
UEshalldeletethelistofequivalentPLMNsandresettheregistrationattemptcounterandstorethePLMNidentityinthe
"forbiddenPIMNlist"
UEshallenterstate5GMM-DEREGISTERED.PLMN-SEARCHandperformaPLMNselection
KOOROSH
Description
CauseCode Causevalue
This5GMMcauseissenttotheUEifitrequestsservice,orifthenetworkinitiatesade-registrationrequest,inatrackingareawhere
theHPLMNdeterminesthattheUE,bysubscription,isnotallowedtooperate.
12
If5GMMcause#12issenttoaroamingsubscriberthesubscriberisdeniedserviceevenifotherPLMNsareavailableonwhich
Trackingarearegistrationwaspossible.
notallowed UEshalldelete5G-GUTI,lastvisitedregisteredTAI,TAIlistandngKSI
UEshallresettheregistrationattemptcounter
UEshallstorethecurrentTAIinthelistof"5GSforbiddentrackingareasforregionalprovisionofservice"andenterthestate5GMM-
DEREGISTERED,LIMITED-SERVICE
This5GMMcauseissenttoaUEwhichrequestsservice,orifthenetworkinitiatesade-registrationrequest,inatrackingareaofa
13
RoamingnotPLMNwhichbysubscriptionoffersroamingtothatUEbutnotinthattrackingarea.
allowedinthisUEshalldelete5G-GUTI,lastvisitedregisteredTAI,TAIlistandngKSI.Additionally,theUEshalldeletethelistofequivalentPLMNs
trackingareaUEshallresettheregistrationattemptcounter
lUEshallstorethecurrentTAIinthelistof"5GSforbiddentrackingareasforroaming"andenterthestate5GMM-DEREGISTERED,
LIMITED-SERVICEoroptionally5GMM-DEREGISTERED.PLMN-SEARCH
This5GMMcauseissenttotheUEifitrequestsservice,orifthenetworkinitiatesade-registrationrequest,inatrackingareawhere
theUE,bysubscription,isnotallowedtooperate,butwhenitshouldfindanotherallowedtrackingareainthesamePLMNoran
equivalentPLMN.
15
NosuitablecellsCause#15andcause#12differinthefactthatcause#12doesnottriggertheUEtosearchforanotherallowedtrackingareaonthe
LMN.
intrackingareaSameP
UEshalldelete5G-GUTI,lastvisitedregisteredTAI,TAIlistandngKSI.Additionally,theUEshalldeletethelistofequivalentPLMNs
UEshallresettheregistrationattemptcounter
UFshallstorethecurrentTAIinthelistof"5GSforbiddentrackingareasforroaming"andenterthestate5GMM-DEREGISTERED,
LIMITED-SERVICEoroptionally5GMM-DEREGISTERED.PLMN-SEARCH
KOOROSH
CauseCodeCausevalue
Description
Whenreceivedovernon-3GPPaccesstheUEshallsetthe5GSupdatestatusto53ROAMINGNOTALLOWED(andshallstoreitaccordingtosubclause
72
Non-3GPPaccess5.1.3.2.2)andshalldelete5G-GUTI,lastvisitedregisteredTAI,TAIlistandngKSI.Additionally,theUEshallresettheregistrationattemptcounterandenterthe
to5GCNnot
allowed
state5GMM-DEREGISTERED.IfthemessagehasbeensuccessfullyintegritycheckedbytheNAS,theUEshallset:
1)thePLMN-specificN1modeattemptcounterfornon-3GPPaccessforthatPLMNincaseofPLMN:or
2)theSPN-specificattemptcounterfornon-3GPPaccessforthatSPNincaseofSNPN;
ThiscausevaluereceivedfromacellbelongingtoanSPNisconsideredasanabnormalcaseandthebehavioroftheUEisspecifiedinsubclause5.5.1.2.7.
TheUEshallsetthe5GSupdatestatusto53ROAMINGNOTALLOWED(andshallstoreitaccordingtosubclause5.1.3.2.2)andshalldeleteany5G-GUTI,last
visitedregisteredTAI,TAIlistandngKSI.TheUEshalldeletethelistofequivalentPLMNs,resettheregistrationattemptcounter,storethePLMNidentityinthe
forbiddenPLMNlistasspecifiedinsubclause5.3.13A.For3GPPaccesstheUEshallenterstate5GMM-DEREGISTERED.PLMN-SEARCHinordertoperforma
73
ServingnetworkPLMNselectionaccordingto3GPPTS23.122[5],andfornon-3GPPaccesstheUEshallenterstate5GMM-DEREGISTERED.LIMITED-SERVICEandperform
notauthorizednetworkselectionasdefinedin3GPPTS24.502[18].IfthemessagehasbeensuccessfullyintegritycheckedbytheNAS,theUEshallsetthePLMN-specific
attemptcounterandthePLMN-specificattemptcounterfornon-3GPPaccessforthatPLMNtotheUEimplementation-specificmaximumvalue.
Ifthemessagewasreceivedvia3GPPaccessandtheUEisoperatinginsingle-registrationmode,theUEshallinadditionsettheEPSupdatestatustoEU3
ROAMINGNOTALLOWEDandshalldeleteany4G-GUTI,lastvisitedregisteredTAI,TAIlistandeKSI.Additionally,theUEshallresettheattachattemptcounter
andenterthestateEMM-DEREGISTERED
5GMMcause#74isonlyapplicablewhenreceivedfromacellbelongingtoanSPN.5GMMcause#74receivedfromacellnotbelongingtoanSPNis
consideredasanabnormalcaseandthebehavioroftheUEisspecifiedinsubclause5.5.1.2.7.
TheUEshallsetthe5GSupdatestatusto5U3ROAMINGNOTALLOWED(andshallstoreitaccordingtosubclause5.1.3.2.2)andshalldeleteany5G-GUTI,last
visitedregisteredTAI,TAIlistandngKSI.TheUEshallresettheregistrationattemptcounterandstoretheSPNidentityinthe"temporarilyforbiddenSNPNs"
74
Temporarilvnotlistforthespecificaccesstypeforwhichthemessagewasreceivedand,iftheUEsupportsaccesstoanSNPNusingcredentialsfromacredentialsholder,the
authorizedforthisselectedentryofthe"listofsubscriberdata"ortheselectedPLMNsubscription.IftheregistrationrequestisnotforonboardingservicesinSNPN,theUEshall
SNPN
enterstate5GMM-DEREGISTERED.PLMN-SEARCHandperformanSPselectionaccordingto3GPPTS23.122[51.Iftheregistrationrequestisforonboarding
servicesinSNPN,theUEshallenterstate5GMM-DEREGISTERED.PLMN-SEARCHandperformanSNPNselectionforonboardingservicesaccordingto3GPPTS
23.122[5].IfthemessagehasbeensuccessfullyintegritycheckedbytheNAS,theUEshallsettheSPN-specificattemptcounterfor3GPPaccessandthe
SNPN-specificattemptcounterfornon-3GPPaccessforthecurrentSNPNtotheUEimplementation-specificmaximumvalue.
IfthemessagehasbeensuccessfullyintegritycheckedbytheNASandtheUEalsosupportstheregistrationprocedureovertheotheraccesstothesame
SNPN.theUEshallinadditionhandle5GMMparametersand5GMMstateforthisaccess.asdescribedforthis5GMMcausevalue
KOOROSH
More Related Content
What's hot (20)
rrc-procedures-in-lte
Lte principles overview
rrc-procedures-in-lte
Oea000000 lte principle
fundamental issue 1.01
Morg • 35K views
Ndukwe Ama… • 265 views
Lte principles overview
Ndukwe Ama… • 615 views
UMTS/LTE/EPC Call Flows for CSFB
Da
UMTS/LTE/EPC Call
Flows for CSFB
Justin MA (⾺… • 65K views
Similar to 5GC Registration Failure Codes (20)
Etsi smg3 wpa gprs ad hoc
2 g 3gcell_reselection_alcate…
Engineer EMERSON
EMERSON ED… • 67 views
EDUARDO RODRIGUES
Small cell tmo54097 w pdf
Etsi smg3 wpa gprs ad
hoc
Small cell tmo54097 w
pdf
adebisi adeba… • 192 views
Nitin George …
• 27 views
359182077-LTE-Mobility-Strategy.pptx
int
359182077-LTE-MobilityStrategy.pptx
ssuser38e5dc1 • 17 views
Ad for Scribd subscription
Slideshows for you (20)
Advertising Design
Public Relations
What is strategy?
Advertising Design
Public Relations
What is strategy?
Sarah Fernetich • 12K views
Prathamesh P… • 212K views
Dr. Marc Sniu… • 370K views
2. A Strategic Plan Format
Pu
2. A Strategic Plan
Format
Earl Stevens • 7.7K views
Recently uploaded (20)
scale-model-slides-v1
Rewind Quiz 2023-24,
Quiz Club NITW (2023 …
Edition)
New Millennium for
Computer …
Entertainment - Kutaragi
Quiz Club NITW • 105 views
Wait Storyboard.pptx
scale-model-slides-v1
Wait Storyboard.pptx
ehclark63 • 79 views
ehclark63 • 31 views
Slide_N • 14 views
Ad for Scribd subscription
Related Books
Free with a 30 day trial from Everand
Ebook
View All
Ebook
5G NR:
Architecture,…
Sassan
Ahmadi
Technology,
Implementati…
3.5 / 5
and Operation
Mobile Network
Optimization:…
Emmanuel
Guide forUsuah
2G
and 3G Mobile
3.5 / 5
Network
Ebook
PLC
Programming…
Sanusi
A. L.
from Novice
to
Professional:
5/5
Learn PLC
Ebook
PLC
Programming…
Charles
H Johnso…
from Novice
to
Professional:
5/5
Learn PLC
Ebook
Ebook
Introduction to
GSM: Second…
Guy
Inchbald
Edition
MORE
Electron
Robert
E. I
Gadgets
Evil Gen
NEW Bui
0/5
5GC Registration Failure Codes
1. Code 5G Registration
2. In next page, I mentioned Failure Cause codes and in coming pages, description for each cause code is explained. It can be used for Optimization , Maintenance , Monitoring and
Troubleshooting.
3. Cause Code Cause Value Cause Code Cause Value 3 Illegal UE 31 Redirection to EPC required 6 Illegal ME 62 No network slices available 7 5GS services not allowed 72 Non-3GPP
access to 5GCN not allowed 11 PLMN not allowed 73 Serving network not authorized 12 Tracking area not allowed 74 Temporarily not authorized for this SNPN 13 Roaming not
allowed in this tracking area 75 Permanently not authorized for this SNPN 15 No suitable cells in tracking area 76 Not authorized for this CAG or authorized for CAG cells only 22
Congestion 77 Wireline access area not allowed 27 N1 mode not allowed 79 UAS services not allowed
4. Cause Code Cause value Description 3 Illegal UE Illegal UE in 5GMM is sent to the UE when the network refuses service to the UE either because an identity of the UE is not
acceptable to the network or because the UE does not pass the authentication check. UE does following actions upon receiving this cause. The UE shall consider the USIM as invalid
for 5GS services until switching o! or the UICC containing the USIM is removed UE shall delete the list of equivalent PLMNs and enter the state 5GMM-DEREGISTERED USIM shall be
considered as invalid also for non-EPS services until switching o! or the UICC containing the USIM is removed 6 Illegal ME Illegal ME is sent to the UE if the ME used is not acceptable
to the network, e.g. blacklisted. UE does following actions upon recieving this cause. The UE shall consider the USIM as invalid for 5GS services until switching o! or the UICC
containing the USIM is removed UE shall delete the list of equivalent PLMNs and enter the state 5GMM-DEREGISTERED USIM shall be considered as invalid also for non-EPS services
until switching o! or the UICC containing the USIM is removed 7 5GS services not allowed This 5GMM cause is sent to the UE when it is not allowed to operate 5GS services The UE
shall consider the USIM as invalid for 5GS services until switching o! or the UICC containing the USIM is removed UE shall delete the list of equivalent PLMNs and enter the state
5GMM-DEREGISTERED USIM shall be considered as invalid also for non-EPS services until switching o! or the UICC containing the USIM is removed 11 PLMN not allowed this 5GMM
cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a PLMN where the UE, by subscription or due to operator determined barring, is
not allowed to operate. UE shall delete the list of equivalent PLMNs and reset the registration attempt counter and store the PLMN identity in the “forbidden PLMN list”. UE shall
enter state 5GMM-DEREGISTERED, PLMN-SEARCH and perform a PLMN selection
5. Cause Code Cause value Description 12 Tracking area not allowed This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a
tracking area where the HPLMN determines that the UE, by subscription, is not allowed to operate. If 5GMM cause #12 is sent to a roaming subscriber the subscriber is denied service
even if other PLMNs are available on which registration was possible. UE shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI UE shall reset the registration attempt
counter UE shall store the current TAI in the list of “5GS forbidden tracking areas for regional provision of service” and enter the state 5GMM- DEREGISTERED, LIMITED-SERVICE 13
Roaming not allowed in this tracking area This 5GMM cause is sent to a UE which requests service, or if the network initiates a de-registration request, in a tracking area of a PLMN
which by subscription o!ers roaming to that UE but not in that tracking area. UE shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall delete
the list of equivalent PLMNs UE shall reset the registration attempt counter UE shall store the current TAI in the list of “5GS forbidden tracking areas for roaming” and enter the state
5GMM-DEREGISTERED, LIMITED-SERVICE or optionally 5GMM-DEREGISTERED.PLMN-SEARCH 15 No suitable cells in tracking area This 5GMM cause is sent to the UE if it requests
service, or if the network initiates a de-registration request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed
tracking area in the same PLMN or an equivalent PLMN. Cause #15 and cause #12 di!er in the fact that cause #12 does not trigger the UE to search for another allowed tracking area
on the same PLMN. UE shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall delete the list of equivalent PLMNs UE shall reset the registration
attempt counter UE shall store the current TAI in the list of “5GS forbidden tracking areas for roaming” and enter the state 5GMM-DEREGISTERED, LIMITED-SERVICE or optionally
5GMM-DEREGISTERED.PLMN-SEARCH
6. Cause Code Cause value Description 22 Congestion If the T3346 value IE is present in the REGISTRATION REJECT message and the value indicates that this timer is neither zero
nor deactivated, UE shall abort the initial registration procedure and enter state 5GMM-DEREGISTERED, ATTEMPTING-REGISTRATION stop timer T3346 if it is running stays in the
current serving cell and applies the normal cell reselection process. The initial registration procedure is started if still needed when timer T3346 expires or is stopped. Else Consider it
as abnormal case 27 N1 mode not allowed This 5GMM cause is sent to the UE if it requests service, or if the network initiates a de-registration request, in a PLMN where the UE by
subscription, is not allowed to operate in N1 mode. UE shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI UE shall reset the registration attempt counter and shall
enter the state 5GMM-NULL UE shall disable the N1 mode capability for both 3GPP access and non-3GPP access 31 Redirection to EPC required 5GMM cause #31 received by a UE
that has not indicated support for CIoT optimizations or received by a UE over non-3GPP access is considered as an abnormal case and the behavior of the UE is specified in
subclause 5.5.1.2.7. This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behavior of the UE is specified in subclause 5.5.1.2.7. The
UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list
and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall enable the E-UTRA capability if it was disabled, disable the N1 mode capability for 3GPP
access (see subclause 4.9.2) and enter the 5GMM- DEREGISTERED.NO-CELL-AVAILABLE. If the message was received via 3GPP access and the UE is operating in single-registration
mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301 [15] for the case
when the EPS attach procedure is rejected with the EMM cause with the same value. 62 No network slices available The UE shall abort the initial registration procedure, set the 5GS
update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.NORMAL-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the
registration attempt counter.
7. Cause Code Cause value Description 72 Non-3GPP access to 5GCN not allowed When received over non-3GPP access the UE shall set the 5GS update status to 5U3 ROAMING NOT
ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration
attempt counter and enter the state 5GMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode
attempt counter for non-3GPP access for that PLMN in case of PLMN: or 2) the SNPN-specific attempt counter for non-3GPP access for that SNPN in case of SNPN; 73 Serving network
not authorized This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behavior of the UE is specified in subclause 5.5.1.2.7. The UE
shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list
and ngKSI. The UE shall delete the list of equivalent PLMNs, reset the registration attempt counter, store the PLMN identity in the forbidden PLMN list as specified in subclause
5.3.13A. For 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122 [5], and for non-3GPP
access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502 [18]. If the message has been successfully
integrity checked by the NAS, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE
implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS
update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter
and enter the state EMM-DEREGISTERED. 74 Temporarily not authorized for this SNPN 5GMM cause #74 is only applicable when received from a cell belonging to an SNPN. 5GMM
cause #74 received from a cell not belonging to an SNPN is considered as an abnormal case and the behavior of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS
update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE
shall reset the registration attempt counter and store the SNPN identity in the "temporarily forbidden SNPNs" list for the specific access type for which the message was received
and, if the UE supports access to an SNPN using credentials from a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the
registration request is not for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS
23.122 [5]. If the registration request is for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection for
onboarding services according to 3GPP TS 23.122 [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP
access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully
integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and
5GMM state for this access, as described for this 5GMM cause value.
8. Cause Code Cause value Description 75 Permanently not authorized for this SNPN 5GMM cause #75 is only applicable when received from a cell belonging to an SNPN with a
globally-unique SNPN identity. 5GMM cause #75 received from a cell not belonging to an SNPN or a cell belonging to an SNPN with a non-globally-unique SNPN identity is
considered as an abnormal case and the behavior of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store
it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall reset the registration attempt counter and store the SNPN
identity in the "permanently forbidden SNPNs" list for the specific access type for which the message was received and, if the UE supports access to an SNPN using credentials from
a credentials holder, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the registration request is not for onboarding services in SNPN, the UE
shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122 [5]. If the registration request is for onboarding services in SNPN,
the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection for onboarding services according to 3GPP TS 23.122 [5]. If the message has been
successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the
current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration
procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. 76 Not
authorized for this CAG or authorized for CAG cells only This cause value received via non-3GPP access or from a cell belonging to an SNPN is considered as an abnormal case and
the behavior of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED, store the 5GS update status according to clause
5.1.3.2.2, and reset the registration attempt counter. If 5GMM cause #76 is received from: 77 Wireline access area not allowed 5GMM cause #77 is only applicable when received from
a wireline access network by the 5G-RG or the W-AGF acting on behalf of the FN-CRG. 5GMM cause #77 received from a 5G access network other than a wireline access network and
5GMM cause #77 received by the W-AGF acting on behalf of the FN-BRG are considered as abnormal cases and the behavior of the UE is specified in subclause 5.5.1.2.7. When
received over wireline access network, the 5G-RG and the W-AGF acting on behalf of the FN-CRG shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it
according to subclause 5.1.3.2.2), shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI, shall reset the registration attempt counter, shall enter the state 5GMMDEREGISTERED and shall act as specified in subclause 5.3.23. 79 UAS services not allowed The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT
UPDATED and enter state 5GMM-DEREGISTERED.NORMAL-SERVICE or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. The UE
shall not attempt the registration procedure with including the Service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE to the current PLMN until the
UE is switched o! or the UICC containing the USIM is removed.
About
Support
Terms
Everand
© 2024 SlideShare from Scribd
Privacy
Copyright
Cookie Preferences
Do not sell or share my personal information
English



Download