name: ATSSS
full_form: Access Traffic Steering, Switching, Splitting
context: the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message. The SMF shall set the content of the ATSSS container IE as specified in 3GPP TS 24.193 [13B]. If the UE requests to establish user plane resources over the second access of an MA PDU session which has already been established over the first access and the parameters associated with ATSSS previously provided to the UE are not to be updated, the "ATSSS container contents" shall not be included in the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message. If the PDU session is a single access PDU session containing the MA PDU session information IE with the value set to "MA PDU session network upgrade is allowed" and: a) if the SMF decides to establish a single access PDU session, the SMF shall not include the ATSSS container IE in the PDU SESSION ESTABLISHMENT ACCEPT message; or b) if the SMF decides to establish an MA PDU session, the SMF shall include the ATSSS container IE in the PDU SESSION
description: Access Traffic Steering, Switching, Splitting (ATSSS) is a procedure related to the establishment of Multi-Access (MA) PDU sessions. It involves the management of user plane resources and the exchange of specific information elements between the UE and the SMF.
explanation: The context describes ATSSS as part of the PDU session establishment process, specifically in relation to MA PDU sessions and the handling of ATSSS container IEs in the PDU SESSION ESTABLISHMENT ACCEPT message. This indicates that ATSSS is a procedure for managing access traffic steering, switching, and splitting during PDU session establishment.
section_title: 10.4.1.1UE-requested MA PDU session establishment / ATSSS / Registered to same PLMNs over 3GPP and non-3GPP accesses simultaneously / Success
biotag_Context: O,B-Procedure,O,B-Message,O,O,B-Connection,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,O,B-Message,O,O,O,B-Organization,B-Specification,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,B-Message,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,B-Technology,B-Connection,O,O,B-Message,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Connection,O,O,B-Network Function,O,O,O,O,B-Procedure,O,B-Message,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Technology,B-Connection,O,O,B-Network Function,O,O,O,B-Procedure,O,B-Message,O,O,B-Connection,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O