Section: 5.3.5.2 3GPP access service area restrictions
Content: The service area restrictions consist of tracking areas forming either an allowed area, or a non-allowed area. The tracking areas belong to the registered PLMN, its equivalent PLMNs in the registration area, or the registered SNPN. The allowed area can contain up to 16 tracking areas or include all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area, or in the registered SNPN. The non-allowed area can contain up to 16 tracking areas. The network conveys the service area restrictions to the UE by including either an allowed area, or a non-allowed area, but not both, in the Service area list IE of a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. If the network does not convey the service area restrictions to the UE in the Service area list IE of a REGISTRATION ACCEPT message, the UE shall treat all tracking areas in the registered PLMN, its equivalent PLMN(s) in the registration area, or in the registered SNPN, as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas". When the UE receives a Service area list IE with an allowed area indication during a registration procedure or a generic UE configuration update procedure: a) if the "Type of list" included in the Service area list IE does not indicate "all TAIs belonging to the PLMNs in the registration area are allowed area", the UE shall delete the old list of "allowed tracking areas" and store the tracking areas in the allowed area as the list of "allowed tracking areas". If the UE has a stored list of "non-allowed tracking areas", the UE shall delete that list; or b) if the "Type of list" included in the Service area list IE indicates "all TAIs belonging to the PLMNs in the registration area are allowed area", the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s), or in the registered SNPN, as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas". When the UE receives a Service area list IE with a non-allowed area indication during a registration procedure or a generic UE configuration update procedure, the UE shall delete the old list of "non-allowed tracking areas" and store the tracking areas in the non-allowed area as the list of "non-allowed tracking areas". If the UE has a stored list of "allowed tracking areas", the UE shall delete that list. If the UE is successfully registered to a PLMN or SNPN and has a stored list of "allowed tracking areas": a) while the current TAI is in the list of "allowed tracking areas", the UE shall stay in, or enter, the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and b) while the UE is camped on a cell which is in the registered PLMN, a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and: 1) if the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access, the UE: i) shall not include the Uplink data status IE in the registration procedure for mobility and periodic registration update except for emergency services or for high priority access; ii) shall not perform the registration procedure for mobility and periodic registration update with Follow-on request indicator set to "Follow-on request pending", except for: - emergency services; - high priority access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container; iii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: - emergency services; - emergency services fallback; - high priority access; - responding to paging; - responding to notification received over non-3GPP access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iv) if the UE responds to a paging which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed; and 2) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE: i) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access; ii) shall not initiate a service request procedure except for: - emergency services; - emergency services fallback; - high priority access; - responding to paging or responding to a notification. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iii) shall not initiate a 5GSM procedure except for: - emergency services; - high priority access; or - indicating a change of 3GPP PS data off UE status; iv) shall not perform the NAS transport procedure except for the sending: - SMS; - an LPP message; - a UPP-CMI container; - an SLPP message; - a location services message; - an SOR transparent container; - a UE policy container; - a UE parameters update transparent container; or - a CIoT user data container; and NOTE 1: The contents of CIoT user data container can be data that is not for exception reports, or data that is for exception reports if allowed for the UE (see subclause 6.2.13). v) if the UE responds to a notification which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed. If the UE is successfully registered to a PLMN or an SNPN and has a stored list of "non-allowed tracking areas": a) while the UE is camped on a cell which is in the registered PLMN,a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "non-allowed tracking areas", the UE shall stay in, or enter, the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and b) while the current TAI is in the list of "non-allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and: 1) if the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access, the UE: i) shall not include the Uplink data status IE in the registration procedure for mobility and periodic registration update except for emergency services or for high priority access; ii) shall not perform the registration procedure for mobility and periodic registration update with Follow-on request indicator set to "Follow-on request pending", except for: - emergency services; - high priority access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container; and iii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: - emergency services; - emergency services fallback; - high priority access; - responding to paging; - responding to notification received over non-3GPP access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iv) if the UE responds to a paging which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed; and 2) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE: i) shall not perform the registration procedure for mobility and periodic registration update with the Uplink data status IE except for emergency services or for high priority access; ii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: - emergency services; - emergency services fallback; - high priority access; or - responding to paging or responding to a notification. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iii) shall not initiate a 5GSM procedure except for: - emergency services; - high priority access; or - indicating a change of 3GPP PS data off UE status; iv) shall not perform the NAS transport procedure except for the sending: - SMS; - an LPP message; - a UPP-CMI container; - an SLPP message; - a location services message; - an SOR transparent container; - a UE policy container; - a UE parameters update transparent container; or - a CIoT user data container; and NOTE 2: The contents of CIoT user data container can be data that is not for exception reports, or data that is for exception reports if allowed for the UE (see subclause 6.2.13). v) if the UE responds to a notification which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed. The list of "allowed tracking areas", as well as the list of "non-allowed tracking areas" shall be erased when: a) the UE is switched off; and b) the UICC containing the USIM is removed or an entry of the "list of subscriber data" with the SNPN identity of the SNPN is updated. When a tracking area is added to the list of "5GS forbidden tracking areas for roaming" or to the list of "5GS forbidden tracking areas for regional provision of service" as specified in the subclauses 5.5.1.2.5 or 5.5.1.3.5, the tracking area shall be removed from the list of "allowed tracking areas" if the tracking area is already present in the list of "allowed tracking areas" and from the list of "non-allowed tracking areas" if the tracking area is already present in the list of "non-allowed tracking areas".