name: SAPI
full_form: Service Access Point Indicator
context: of the logical link using the negotiated LLC SAPI, the negotiated QoS profile and selected radio priority level stored in the PDP context as in a GSM to GSM Routing Area Update. An UE, which is capable of operating in both GSM and UMTS, shall use a valid LLC SAPI, while an UE which is capable of operating only in UMTS shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network. When the UE uses a valid LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the âLLC SAPI not assignedâ value only when the UE uses the âLLC SAPI not assignedâ value. NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in UMTS, shall be included in the messages, in order to support handover between UMTS and GSM networks. Reference 3GPP TS 24.008 clauses 6.1.3.2 and 6.1.3.2.1. 11.1.4.1.1.3 Test purpose To test the behaviour of the UE when SS responds to a
description: The Service Access Point Indicator (SAPI) is a parameter used in the logical link control (LLC) protocol to identify the type of service being requested or offered by the network. It is an essential attribute for establishing and managing connections between the user equipment (UE) and the network.
explanation: The text explicitly states that SAPI is a parameter used within the PDP context for negotiating QoS profiles and radio priority levels, and it's involved in handover procedures between UMTS and GSM networks. These functions clearly define SAPI as a configurable attribute used to control network behavior, aligning with the definition of a Parameter.
section_title: 11.1.4.1.1QoS Offered by Network is the QoS Requested
biotag_Context: O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Measurement,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Network,O,B-Network,B-Miscellaneous,I-Miscellaneous,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,O,O,O,O,O,O,O,B-Technology,O,O,O,B-Protocol,B-Parameter,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Network,O,O,B-Specification,I-Specification,I-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Miscellaneous,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O