name: AAL
full_form: ATM Adaptation Layer
context: The ACDC feature allows network to control new PS domain access attempts from particular applications in the UE in idle mode to prevent/mitigate overload of the access network and/or the core network. The applications on the UE may be associated with an ACDC category. At subscription, at least four ACDC categories, and up to 16 ACDC categories, are allocated to the subscriber and stored in the ACDC Management Object (MO) or USIM [9]. The access barring information for each ACDC category is broadcast in SIB. The ACDC capable UE controls the access attempt for a certain application based on the broadcast barring information and the configuration of ACDC categories in the UE. The following guidelines define the behaviour of a UE configured with ACDC when other access control mechanisms (ACB, EAB and DSAC) are co-existing: - When DSAC and ACDC are configured together, the PS domain DSAC will be ignored by the UEs. - When EAB and ACDC are configured together, the UE will first check EAB and
description: The ATM Adaptation Layer (AAL) is a protocol layer that enables the transport of ATM cells over various networks. AAL type 2 is a specific type of AAL connection that supports the selection of a succeeding AAL type 2 path or underlying VC according to the requested path type. The AAL type 2 endpoints and switching nodes deploy this capability, which allows for the establishment of an AAL type 2 connection within a series of AAL type 2 paths aligned with the requested path type.
explanation: AAL is classified as a Protocol because it defines rules and procedures for adapting ATM cells for transport over different network types. The description details how AAL type 2 specifically manages connections and path selection, demonstrating its function as a set of standardized communication protocols.
section_title: 6.1.1	Path type capability
biotag_Context: O,B-Protocol,O,O,O,O,O,O,B-Mode,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Protocol,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Parameter,O,B-Protocol,O,O,O,O,B-Mode,O,B-Parameter,O,O,O,O,O,O,O,O,B-Procedure,O,B-Protocol,O,O,O,O,B-Device,O,O,O,B-Procedure,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O