name: SR
full_form: Scheduling Request
context: The IE SchedulingRequestConfig is used to configure the parameters, for the dedicated scheduling request (SR) resources. SchedulingRequestConfig information element -- ASN1START -- TAG-SCHEDULINGREQUESTCONFIG-START SchedulingRequestConfig ::= SEQUENCE { schedulingRequestToAddModList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod OPTIONAL, -- Need N schedulingRequestToReleaseList SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId OPTIONAL -- Need N } SchedulingRequestToAddMod ::= SEQUENCE { schedulingRequestId SchedulingRequestId, sr-ProhibitTimer ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms32, ms64, ms128} OPTIONAL, -- Need S sr-TransMax ENUMERATED { n4, n8, n16, n32, n64, spare3, spare2, spare1} } SchedulingRequestConfig-v1700 ::= SEQUENCE { schedulingRequestToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddModExt-v1700 OPTIONAL -- Need N } SchedulingRequestToAddModExt-v1700 ::= SEQUENCE { sr-ProhibitTimer-v1700 ENUMERATED { ms192, ms256, ms320, ms384, ms448, ms512, ms576, ms640, ms1082, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL -- Need R } -- TAG-SCHEDULINGREQUESTCONFIG-STOP -- ASN1STOP
description: The Scheduling Request (SR) is a control message used in the context of LTE and 5G networks to manage uplink scheduling requests. It is utilized by the User Equipment (UE) to request uplink transmission resources from the eNodeB or gNodeB, which are the base stations in LTE and 5G networks respectively. The SR message contains information such as the Scheduling Request ID and configuration parameters like sr-ProhibitTimer and sr-TransMax, which help in managing the scheduling process efficiently.
explanation: SR is classified as a Message because it is used for signaling between the UE and the base station to manage uplink scheduling requests. The provided context details its usage within the network, highlighting its role in facilitating communication between different network elements.
section_title: â SchedulingRequestConfig
biotag_Context: O,B-Message,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,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,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
biotag_Description: O,B-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Technology,O,B-Technology,O,O,O,B-Procedure,O,O,O,O,O,O,B-Procedure,I-Procedure,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O