name: MPTCP
full_form: Multi-Path TCP Protocol
context: 5.32.6 of 3GPP TS 23.501 [8], the UE shall set the ATSSS-ST bits to "ATSSS Low-Layer functionality with any steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; b) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501 [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; c) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501 [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode supported" in the 5GSM capability IE of the PDU SESSION
description: Multi-Path TCP Protocol (MPTCP) enables multiple network paths for simultaneous data transmission, enhancing network efficiency and reliability.  As mentioned in 3GPP TS 38.523, MPTCP is a UE (User Equipment) functionality that can be used with ATSSS-LL (Access Traffic Steering, Switching and Splitting - Low-Layer).
explanation: MPTCP is classified as a Protocol because it defines the rules and procedures for data transmission across multiple network paths. The text explicitly states MPTCP's role in enabling this functionality and its support within the UE framework, solidifying its classification.
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,O,B-Specification,I-Specification,I-Specification,O,O,B-Device,O,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,O,B-Device,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,I-Specification,I-Specification,O,O,B-Device,O,O,O,O,O,O,O,O,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,O,B-Device,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,I-Specification,I-Specification,O,O,B-Device,O,O,O,O,O,O,O,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
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,B-Protocol,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O