3GPP 23.501 v20.2.0 — the document's own text
5.38.5 Paging Restriction
Taught in 27. Overload, energy, deployment and the rest (The 5G system architecture, in depth).
A Multi-USIM UE and the network may support Paging Restriction. A Multi-USIM UE, if the AMF indicates that the network supports Paging Restriction feature, may indicate Paging Restriction Information in the Service Request or Registration Request message (including the case where the Registration Request is sent due to mobility outside the Registration Area, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Paging Restriction feature in the current stored Registration Area) as specified in clauses 5.38.2 and 5.38.4.
Based on operator policy the AMF may accept or reject the Paging Restriction Information requested by the UE. If the AMF accepts the Paging Restriction Information from the UE, the AMF stores the Paging Restriction Information from the UE in the UE context. If the AMF rejects the Paging Restriction Information, the AMF removes any stored Paging Restriction Information from the UE context and discards the UEs requested Paging Restriction Information. The AMF informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Registration Accept or Service Accept message.
If the UE does not provide any Paging Restriction Information in the Service Request over 3GPP access or the Registration Request over 3GPP access, the AMF removes any stored Paging Restriction Information from the UE context.
The Paging Restriction Information may indicate any of the following:
- all paging is restricted; or
- all paging is restricted, except paging for voice service (IMS voice); or
- all paging is restricted, except for certain PDU Session(s); or
- all paging is restricted, except paging for voice service (IMS voice) and certain PDU session(s).
NOTE 1: The UE expects not to be paged for any purpose in case a). The UE expects to be paged only for voice service in case b). The UE expects to be paged only for certain PDU Session(s) in case c). The UE expects to be paged for voice service and certain PDU session(s) in case d). The AMF can page the UE for mobile terminated signalling based on local policy considering the stored Paging Restriction Information, except for case a). In this case, to comply with the UE provided Paging Restriction Information, the AMF can trigger AN release procedure as soon as possible after the mobile terminated signalling procedure is executed.
NOTE 2: In the case of roaming, the Paging Restrictions for voice service implied by bullet b) and d) depends on the existence of an agreement with the HPLMN to support voice service via IMS. Hence the support of Paging Restrictions in bullets b) and d) takes the IMS voice service agreement into consideration.
NOTE 3: When there is no PLMN-wide support for the Paging Restriction feature, it can occur that upon Mobility Registration Update with Paging Restriction Information the UE detects the network does not support the feature. If so, the UE assumes that no Paging Restriction Information is applied.