3GPP 24.501 v20.0.0 — the document's own text
5.6.3.2 Notification procedure initiation
Taught in 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).
The network shall initiate the notification procedure by sending the NOTIFICATION message to the UE and start timer T3565 (see example in figure 5.6.3.2.1).
For case a) in clause 5.6.3.1, the NOTIFICATION message is sent from the network to the UE via 3GPP access with access type indicating non-3GPP access.
For case b) in clause 5.6.3.1, the NOTIFICATION message is sent from the network to the UE via non-3GPP access with access type indicating 3GPP access when the UE is not in MICO mode or when the network determines the unavailability period is not activated for the UE.

For case b) in clause 5.6.3.1, if the network has downlink user data pending for a UE and the AMF has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to:
- "All paging is restricted", the network should not send the NOTIFICATION message to the UE;
- "All paging is restricted except for voice service", the network should send the NOTIFICATION message to the UE only when the pending downlink user data for the UE is considered as voice service related by the network and the MUSIM UE does not support the paging indication for voice services or the network has not indicated "paging indication for voice services supported" to the UE;
- "All paging is restricted except for specified PDU session(s)", the network should send the NOTIFICATION message to the UE only when:
- for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending;
- "All paging is restricted except for voice service and specified PDU session(s)" the network should send the NOTIFICATION message to the UE only:
- when the pending downlink user data for the UE is considered as voice service related by the network and the MUSIM UE does not support the paging indication for voice services, or the network has not indicated "paging indication for voice services supported" to the UE; or
- for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending.
For case b) in clause 5.6.3.1, if the network has downlink signalling pending for a UE and the AMF has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to:
- "All paging is restricted", the network should not send the NOTIFICATION message to the UE;
- "All paging is restricted except for voice service", then the network should send the NOTIFICATION message to the UE only when:
- the pending downlink signalling for the UE is 5GMM signalling or 5GSM signalling of the PDU session of voice service;
- "All paging is restricted except for specified PDU session(s)", the network should send the NOTIFICATION message to the UE only when:
- the pending downlink signalling for the UE is 5GMM signalling; or
- for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink 5GSM signalling pending; or
- "All paging is restricted except for voice service and specified PDU session(s)" then the network should send the NOTIFICATION message to the UE only when:
- the pending downlink signalling for the UE is 5GMM signalling or 5GSM signalling pending of the PDU session of voice service; or
- for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink 5GSM signalling pending.
NOTE 1: If the network sends NOTIFICATION message to the UE due to downlink signalling pending, the network initiates the release of the N1 NAS signalling connection over 3GPP access after network-requested procedure is completed.
Upon reception of a NOTIFICATION message, the UE shall stop the timer T3346, if running.
For case a) in clause 5.6.3.1, upon reception of NOTIFICATION message, the UE shall initiate a service request procedure over 3GPP access as specified in clauses 5.6.1.
NOTE 2: For a UE in NB-NI mode, if there is DL user data pending for a PDU session associated with non-3GPP access then the AMF notifies the SMF that reactivation of user plane resources cannot be performed if the number of PDU sessions that currently has user-plane resources established equals to the UE's maximum number of supported user-plane resources.
For case b) in clause 5.6.3.1, upon reception of NOTIFICATION message:
- if control plane CIoT 5GS optimization is not used by the UE, the UE shall:
- initiate a service request procedure over 3GPP access as specified in clause 5.6.1.2.1, if the UE is in 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in clause 5.3.5.2) state over 3GPP access or 5GMM-REGISTERED.NON-ALLOWED-SERVICE state (see clause 5.3.5.2), and the UE is in the 5GMM-IDLE mode without suspend indication;
- initiate a registration procedure for mobility and periodic registration update over 3GPP access as specified in clause 5.5.1.3.2, if the UE is in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state over 3GPP access; or
- proceed as specified in clause 5.3.1.5 if the UE is in the 5GMM-IDLE mode with suspend indication;
- if control plane CIoT 5GS optimization is used by the UE, the UE shall:
- initiate a service request procedure over 3GPP access as specified in clause 5.6.1.2.2, if the UE is in 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in clause 5.3.5.2) state and the UE is in the 5GMM-IDLE mode without suspend indication;
- initiate a registration procedure for mobility and periodic registration update over 3GPP access as specified in clause 5.5.1.3.2, if the UE is in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state; or
- proceed as specified in clause 5.3.1.5 if the UE is in the 5GMM-IDLE mode with suspend indication; or
- if:
- the UE is in 5GMM-REGISTERED.NO-CELL-AVAILABLE state, 5GMM-REGISTERED.PLMN-SEARCH state, 5GMM-REGISTERED.LIMITED-SERVICE state or 5GMM-REGISTERED.UPDATE-NEEDED state over 3GPP access; or
- the MUSIM UE is not able to respond the NOTIFICATION message as specified in case a) and b) above, e.g. due to UE implementation constraints;
the UE shall respond with NOTIFICATION RESPONSE message over non-3GPP access indicating inability of the UE to initiate a service request procedure or a registration procedure over 3GPP access and may include the PDU session status information element to indicate:
- the single access PDU session(s) not in 5GSM state PDU SESSION INACTIVE in the UE associated with the 3GPP access type; and
- the MA PDU session(s) not in 5GSM state PDU SESSION INACTIVE in the UE and having user plane resources established associated with the 3GPP access type.
Upon reception of NOTIFICATION message:
For case b) in clause 5.6.3.1, if the UE is in 5GMM-REGISTERED.NO-CELL-AVAILABLE state or 5GMM-REGISTERED.PLMN-SEARCH state and a local release was performed in the UE for the single access PDU sessions associated with the 3GPP access or for user plane resources on the 3GPP access of MA PDU sessions;
then the UE shall respond with NOTIFICATION RESPONSE message over non-3GPP access indicating with the PDU session status information element that:
- the local release of its single access PDU sessions associated with the 3GPP access was performed; and
- the local release of its 3GPP access user plane resources of MA PDU sessions was performed.