Section: 5.6.1.4.2 UE is using 5GS services with control plane CIoT 5GS optimization
Content: For case a in subclause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile terminating request", after completion of the 5GMM common procedures (if initiated) according to subclause 5.6.1.3, the AMF shall send a SERVICE ACCEPT message. For cases c, d and m in subclause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile originating request", after completion of the 5GMM common procedures (if initiated) according to subclause 5.6.1.3, the AMF shall send a SERVICE ACCEPT message, except for case d when the DDX field of the Release assistance indication IE or the DDX field of the CIoT small data container IE indicates "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected". For case a, c and d: a) if the CIoT small data container IE is included in the message, the AMF shall decipher the value part of the CIoT small data container IE and: 1) if the Data type field indicates "control plane user data", extract the PDU session ID and data content from the CIoT small data container IE, look up a PDU session routing context for the UE and the PDU session ID, and forward the content of the CIoT small data container IE to the SMF associated with the UE. If the corresponding PDU session is a PDU session for LADN, the AMF determines the UE presence in LADN service area (see subclause 6.2.6) and forwards the UE presence in LADN service area towards the SMF; 2) if the Data type field indicates "SMS", forward the content of the CIoT small data container IE to the SMSF associated with the UE; or 3) if the Data type field indicates "Location services message container", and if i) length of additional information field in the CIoT small data container IE is zero, forward the value of Data type field and the content of the CIoT small data container IE to the to the location services application; or ii) otherwise forward the value of Data type field and the content of the CIoT small data container IE to the LMF associated with the routing information that is included in the additional information field of the CIoT small data container IE; or NOTE 1: If the AMF determines there is no pending data or signalling for the UE, the AMF provides an indication of control plane CIoT 5GS Optimisation to the LMF as specified in 3GPP TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ]  [20B]. b) otherwise, the AMF shall decipher the value part of NAS message container IE and: 1) if the Payload container IE is included in the CONTROL PLANE SERVICE REQUEST message and if the Payload container type IE is set to "CIoT user data container", the AMF shall look up a PDU session routing context for the UE and the PDU session ID, and forward the content of the Payload container IE to the SMF associated with the UE. If the corresponding PDU session is a PDU session for LADN, the AMF determines the UE presence in LADN service area (see subclause 6.2.6) and forwards the UE presence in LADN service area towards the SMF; 2) if the Payload container IE is included in the CONTROL PLANE SERVICE REQUEST message and if the Payload container type IE is set to "SMS", the AMF shall forward the content of the Payload container IE to the SMSF associated with the UE; 3) if the PDU session status IE is included in the CONTROL PLANE SERVICE REQUEST message or the AMF needs to perform a PDU session status synchronization, the AMF shall include a PDU session status IE in the SERVICE ACCEPT message to indicate which PDU sessions associated with the access type the SERVICE ACCEPT message is sent over are active in the AMF; 4) if the Uplink data status IE is included in the CONTROL PLANE SERVICE REQUEST message and the UE is: i) not in NB-N1 mode; or ii) in NB-N1 mode and the UE does not indicate a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources; the AMF shall: i) indicate the SMF to re-establish the user-plane resources for the corresponding PDU sessions; and ii) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the user-plane resources re-establishment result of the PDU sessions for which the UE requested to re-establish the user-plane resources; 5) if the Uplink data status IE is included in the CONTROL PLANE SERVICE REQUEST, the UE is in NB-N1 mode, and the UE indicates a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources, the AMF shall not indicate to the SMF to re-establish the user-plane resources for the corresponding PDU sessions; or 6) otherwise, if the Payload container IE is included in the message and if the Payload container type IE is set to "Location services message container", the AMF shall forward the Payload container type and the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE of the CONTROL PLANE SERVICE REQUEST message. NOTE 2: If the AMF determines there is no pending data or signalling for the UE, the AMF provides an indication of control plane CIoT 5GS Optimisation to the LMF as specified in 3GPP TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ]  [20B]. For case k) in subclause 5.6.1.1, if the Uplink data status IE is included in the CONTROL PLANE SERVICE REQUEST message and the UE is: a) not in NB-N1 mode; or b) in NB-N1 mode and the UE does not indicate a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources, the AMF shall: a) indicate the SMF to re-establish the user-plane resources for the corresponding PDU sessions; and b) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the user-plane resources re-establishment result of the PDU sessions for which the UE requested to re-establish the user-plane resources. If the Allowed PDU session status IE is included in the CONTROL PLANE SERVICE REQUEST message, the AMF shall: a) for a 5GSM message from each SMF that has indicated pending downlink signalling only, forward the received 5GSM message via 3GPP access to the UE after the SERVICE ACCEPT message is sent; b) for each SMF that has indicated pending downlink data only: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; and 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if: i) for a UE not in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; or ii) for a UE in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE and the resulting number of PDU sessions with established user-plane resources does not exceed the UE's maximum number of supported user-plane resources; c) for each SMF that have indicated pending downlink signalling and data: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if: i) for a UE not in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; or ii) for a UE in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE and the resulting number of PDU sessions with established user-plane resources does not exceed the UE's maximum number of supported user-plane resources; and 3) discard the received 5GSM message for PDU session(s) associated with non-3GPP access; and d) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the successfully re-established user-plane resources for the corresponding PDU sessions, if any. If the DDX field in the CIoT small data container IE or the DDX field of the Release assistance indication IE indicates: 1) "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" and if there is no downlink signalling or downlink data for the UE; or 2) "Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected" and upon subsequent delivery of the next received downlink data transmission to the UE and if there is no additional downlink signalling or downlink data for the UE, the AMF initiates the release of the N1 NAS signalling connection (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ]  [9]). If the MUSIM UE does not include the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message, the AMF shall delete any stored paging restriction for the UE and stop restricting paging. For case m in subclause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" in the CONTROL PLANE SERVICE REQUEST message, the AMF shall initiate the release of the N1 NAS signalling connection after the completion of the service request procedure. For cases o and p in subclause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE in the CONTROL PLANE SERVICE REQUEST message and if the UE requests restriction of paging by including the Paging restriction IE, the AMF: - if accepts the paging restriction, shall include the 5GS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The AMF shall store the paging restriction of the UE and enforce these restrictions in the paging procedure as described in subclause 5.6.2; or - if rejects the paging restriction, shall include the 5GS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The AMF shall delete any stored paging restriction for the UE and stop restricting paging; and the AMF shall send the SERVICE ACCEPT message and initiate the release of the N1 NAS signalling connection as follows: - for case o in subclause 5.6.1.1, after the completion of the service request procedure; - for case p in subclause 5.6.1.1, after the completion of the generic UE configuration update procedure that is triggered after the completion of the service request procedure. Upon successful completion of the procedure, the UE shall reset the service request attempt counter, stop the timer T3517 and enter the state 5GMM-REGISTERED. If the PDU session status information element is included in the CONTROL PLANE SERVICE REQUEST message, then the AMF: a) shall perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE on the AMF side associated with the access type the CONTROL PLANE SERVICE REQUEST message is sent over, but are indicated by the UE as being inactive, and b) request the SMF to perform a local release of all those PDU sessions. If any of those PDU sessions is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions. If the PDU session status information element is included in the SERVICE ACCEPT message, then the UE shall perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING on the UE side associated with the 3GPP access but are indicated by the AMF as being inactive. If a locally released PDU session: a) is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions; or b) has the same PDU session identity value as that used by the UE in the CONTROL PLANE SERVICE REQUEST message, and the message contained CIoT user data, then the UE determines that the CIoT user data was not successfully sent. If the user-plane resources cannot be established for a PDU session, the AMF shall include the PDU session reactivation result IE in the SERVICE ACCEPT message indicating that user-plane resources for the corresponding PDU session cannot be re-established, and: a) if the user-plane resources cannot be established because the SMF indicated to the AMF that the UE is located out of the LADN service area (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ]  [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #43 "LADN not available"; b) if the user-plane resources cannot be established because the SMF indicated to the AMF that only prioritized services are allowed (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ]  [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #28 "restricted service area"; or c) if the user-plane resources cannot be established because: 1) the SMF indicated to the AMF that the resource is not available in the UPF (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ]  [20A]); or 2) the UE is in NB-N1 mode and the result will lead to user-plane resources established for more than two PDU sessions (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ]  [9]) the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #92 "insufficient user-plane resources for the PDU session": NOTE 3: For a UE that is not in NB-N1 mode, it is up to UE implementation when to re-send a request for user-plane re-establishment for the associated PDU session after receiving a PDU session reactivation result error cause IE with a 5GMM cause set to #92 "insufficient user-plane resources for the PDU session". For case a and b, - if the AMF has a service area list or LADN information which is applicable to the current TAI of the UE and was not yet provided to the UE, before sending the SERVICE ACCEPT message the AMF shall initiate the generic UE configuration update procedure and include the service area list or LADN information or both in the CONFIGURATION UPDATE COMMAND message; and - if timer T3540 is not started (see subclause 5.3.1.3, item f), and the UE did not receive a CONFIGURATION UPDATE COMMAND message during the service request procedure, the UE may initiate a registration procedure for mobility or periodic registration update. If timer T3540 is started and the UE does not receive a CONFIGURATION UPDATE COMMAND message before the established N1 NAS signalling connection is released by the network or timer T3540 expires or is stopped as specified in subclause 5.3.1.3, the UE may initiate the registration procedure for mobility or periodic registration update upon release of the N1 NAS signalling connection. If the PDU session reactivation result IE is included in the SERVICE ACCEPT message indicating that the user-plane resources cannot be established for a PDU session that was indicated by the UE in the Allowed PDU session status IE as allowed to be re-established over 3GPP access, the UE considers the corresponding PDU session to be associated with the non-3GPP access. For case d) in subclause 5.6.1.1, the UE shall also treat the indication from the lower layers that the RRC connection has been released as successful completion of the procedure. The UE shall reset the service request attempt counter, stop the timer T3517 and enter the state 5GMM-REGISTERED. Upon receipt of the CONTROL PLANE SERVICE REQUEST message with uplink data: - if the DDX field of the Release assistance indication IE or the DDX field of the CIoT small data container IE is set to "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" in the message; - if the AMF decides to forward the uplink data piggybacked in the CONTROL PLANE SERVICE REQUEST message; and - if the AMF decides to activate the congestion control for transport of user data via the control plane, then the AMF shall send SERVICE ACCEPT message with the T3448 value IE included. If the AMF decides to deactivate the congestion control for transport of user data via the control plane, then the AMF shall delete the stored control plane data back-off time for the UE and the AMF shall not include timer T3448 value IE in the SERVICE ACCEPT message. If the T3448 value IE is present in the received SERVICE ACCEPT message and the value indicates that this timer is neither zero nor deactivated, the UE shall: a) stop timer T3448 if it is running; b) consider the transport of user data via the control plane as successful; and c) start timer T3448 with the value provided in the T3448 value IE. If the UE is using 5GS services with control plane CIoT 5GS optimization, the T3448 value IE is present in the SERVICE ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall ignore the T3448 value IE and proceed as if the T3448 value IE was not present. If the UE in 5GMM-IDLE mode initiated the service request procedure by sending a CONTROL PLANE SERVICE REQUEST message and the SERVICE ACCEPT message does not include the T3448 value IE and if timer T3448 is running, then the UE shall stop timer T3448. For case h) in subclause 5.6.1.1, a) the UE shall treat the indication from the lower layers when the UE has changed to S1 mode as successful completion of the procedure and stop timer T3517; b) if a UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access (see subclause 4.9.2); and c) the AMF shall not check for CAG restrictions. If the CONTROL PLANE SERVICE REQUEST message is for emergency services fallback, the AMF triggers the emergency services fallback procedure as specified in subclause 4.13.4.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ]  [9].