– Handover a PDN Connection in EPS to PDU Session in 5GS without N26 interface 4.3.2.2 UE Requested PDU Session Establishment 4.3.2.2.1 Non-roaming and Roaming with Local BreakoutĬlause 4.3.2.2.1 specifies PDU Session establishment in the non-roaming and roaming with local breakout cases. The particular procedures associated with MA PDU Sessions are specified as part of the ATSSS procedures in clause 4.22. The following clause 4.3.2.2 specifies the procedures for establishing PDU Sessions associated with a single access type at a given time. A PDU Session associated with multiple access types is referred to as Multi Access-PDU (MA PDU) Session and it may be requested by ATSSS-capable UEs. either 3GPP access or non-3GPP access, or (b) simultaneously with multiple access types, i.e. If the UE is simultaneously registered to a non-3GPP access via a N3IWF/TNGF/W-AGF located in a PLMN different from the PLMN of the 3GPP access, the functional entities in the following procedures are located in the PLMN of the access used to exchange NAS with the UE for the PDU Session.Īs specified in clause 5.6.1 of TS 23.501 , a PDU Session may be associated either (a) with a single access type at a given time, i.e. Based on that information, the application(s) on the UE side trigger the PDU Session Establishment procedure. The payload included in Device Trigger Request message contains information on which application on the UE side is expected to trigger the PDU Session establishment request.
In this case the network sends the device trigger message to application(s) on the UE side. – a Network triggered PDU Session Establishment procedure. – a UE initiated PDU Session handover from EPS to 5GS. – a UE initiated PDU Session handover between 3GPP and non-3GPP. – a UE initiated PDU Session Establishment procedure. A PDU Session establishment may correspond to:
0 kommentar(er)
