name: SL-RLC0
full_form: Sidelink Radio Link Control 0
context: The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information, or for sidelink communication as specified in clause 5.3.3.1a. The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. Upon initiation of the procedure, the UE shall: 1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment of an RRC connection: 2> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers; 3> if the access attempt is barred, the procedure ends; 1> if the upper layers provide NSAG information and one or more S-NSSAI(s) triggering the access attempt (TS 23.501[ System architecture for the 5G System (5GS) ]  [32] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ]  [23]): 2> apply the NSAG with highest NSAG priority among the NSAGs that are included in SIB1 (i.e., in FeatureCombination and/or in RA-PrioritizationSliceInfo), and that are associated with the S-NSSAI(s) triggering the access attempt, in the Random Access procedure (TS 38.321[ NR; Medium Access Control (MAC) protocol specification ]  [3], clause 5.1); NOTE: If there are multiple NSAGs with the same highest NAS-provided NSAG priority identified for access attempt as above, it is left to UE implementation to select the NSAG to be applied in the Random Access procedure. 1> if the UE is acting as L2 U2N Remote UE: 2> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ]  [66], if no SRAP entity has been established; 2> apply the specified configuration of SL-RLC0 as specified in 9.1.1.4; 2> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> apply the CCCH configuration as specified in 9.1.1.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 1> start timer T300; 1> initiate transmission of the RRCSetupRequest message in accordance with 5.3.3.3;
description: SL-RLC0 refers to a specific configuration for Sidelink Radio Link Control, which is part of the sidelink communication protocol specified in clause 5.3.3.1a of the 3GPP TS 38.331 document. This protocol is used for direct device-to-device communication and plays a crucial role in managing radio resources and controlling data transmission between devices.
explanation: SL-RLC0 is classified as a Protocol because it defines rules and procedures for sidelink communication, specifically focusing on the configuration of Radio Link Control for sidelink operations. This aligns with the definition of protocols within the context of 3GPP specifications.
section_title: 5.3.3.2 Initiation
biotag_Context: O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,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,O,O,O,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,O,O,O,O,O,O,B-Parameter,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,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,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,B-Specification,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,B-Message,O,O,B-Message,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Message,O,O,O,O,O,B-Procedure,I-Procedure,O,O,O,O,B-Device,O,O,O,B-Protocol,B-Interface,O,O,O,O,O,B-Protocol,O,O,O,O,B-Specification,O,O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Connection,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
biotag_Description: B-Protocol,O,O,O,O,O,O,B-Technology,B-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,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