Section: 4.11.1.4.3 EPS bearer ID revocation
Content: Following procedures are updated to revoke the EPS bearer ID(s) assigned to the QoS flow(s): - UE or network requested PDU Session Release for Non-roaming and Roaming with Local Breakout (clause 4.3.4.2). - UE or network requested PDU Session Release for Home-routed Roaming (clause 4.3.4.3). - UE or network requested PDU Session Modification (non-roaming and roaming with local breakout) (clause 4.3.3.2). - UE or network requested PDU Session Modification (home-routed roaming) (clause 4.3.3.3). - Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout) (clause 4.9.2.2) - Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (home routed roaming) (clause 4.9.2.4 When the PDU Session is released as described in clauses 4.3.4.2 or 4.3.4.3, 4.9.2.2, or 4.9.2.4 and the SMF invokes Nsmf_PDUSession_StatusNotify to notify AMF that the SM context for this PDU Session is released, the AMF releases the association between the SMF ID and the PDU Session ID and releases the EBIs assigned for this PDU Session. When all the PDU sessions which are allocated with EBIs are released in the same SMF, the AMF may revoke DNN and SMF+PGW-C FQDN for S5/S8 interface in the UDM using Nudm_UECM_Update service operation. NOTE 1: If the SMF+PGW-C in which the PDU sessions support EPS interworking is changed for the same DNN, the AMF can update the DNN and new SMF+PGW-C FQDN for S5/S8 interface in the UDM using Nudm_UECM_Update service operation. When the UE initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 and the SMF needs to release the assigned EBI from a QoS flow (e.g. when the QoS flow is released), the SMF can indicate the Released EBI list in the Nsmf_PDUSession_UpdateSMContext Response to the AMF. The AMF releases the corresponding EBI allocation for this PDU Session. When the AMF decides to revoke some EBI(s), e.g. when the AMF receives a new EBI allocation request but there is no EBI available, the AMF may decide to revoke EBI(s) for another PDU Session, the AMF initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 and includes EBI list to be revoked in the Nsmf_PDUSession_UpdateSMContext Request. The SMF releases the indicated EBI(s) for the PDU Session. When the AMF initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 to change the status of EPS interworking with N26 to "not supported", the AMF releases the EBIs assigned for this PDU Session and SMF release the assigned EBIs from the QoS Flows belonging to this PDU Session. When the SMF initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 and the SMF needs to release the assigned EBI from a QoS flow (e.g. when the QoS flow is released), the SMF invokes Namf_Communication_EBIAssignment and indicates the Released EBI list to the AMF. The AMF releases the corresponding EBI allocation for this PDU Session. When the handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access is performed in clause 4.9.2.2 or clause 4.9.2.4.1, the AMF, the SMF and the UE releases locally the EBI(s) allocated for this PDU Session. When the handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access is performed in clause 4.9.2.4.2, the H-SMF invokes Nsmf_PDUSession_StatusNotify to notify V-AMF to release the association between the SMF ID and the PDU Session ID and as a result, the EBI(s) assigned for this PDU Session are released. The UE releases locally the EBI(s) allocated for this PDU Session.