SIST EN 301 503 V8.4.1:2003
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface layer 3 specification; Radio Resource Control Protocol (GSM 04.18 version 8.4.1 Release 1999)
- Abstract
Added CR history table for SMG#31
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
SIST EN 301 503 V8.4.1:2003 is the Slovenian adoption of ETSI EN 301 503 Version 8.4.1. It specifies the Radio Resource Control Protocol for the GSM mobile radio interface, covering how the mobile station and the network establish, use, modify, and release radio resources on the Um interface. It is written for GSM Phase 2+ systems, including circuit-switched service, GPRS-related procedures, and selected support for VGCS and VBS.
What does SIST EN 301 503 V8.4.1:2003 specify?
SIST EN 301 503 V8.4.1:2003 specifies radio resource management procedures exchanged over the GSM control channels. The document also covers message formats, information element coding, error handling, timers, and the procedures used for packet-related temporary block flow establishment.
The standard is organized into clauses for scope and references, then detailed procedure clauses, message definitions, coding rules, system parameters, and annexes with examples and coding guidance.
| Annex | What it covers |
|---|---|
| A | Example of subaddress information element coding |
| B | Compatibility checking |
| C | Low layer information coding principles |
| D | Examples of bearer capability information element coding |
| E | Comparison of GSM call control procedures with CCITT Recommendation Q.931 |
| F-G | GSM specific cause values for radio resource management and mobility management |
| H-I | GSM specific cause values for call control and session management |
| J | Algorithm to encode frequency list information elements |
| K | Default codings of information elements |
| L | Additional requirements for backward compatibility with PCS1900 for NA revision 0 ME |
| M | Change record |
What are the key requirements of SIST EN 301 503 V8.4.1:2003?
SIST EN 301 503 V8.4.1:2003 defines how a GSM mobile station and network handle control of radio resources in idle, dedicated, group receive, group transmit, packet idle, packet transfer, and dual transfer modes. In practice, this is the signaling layer that decides how a device gets access, stays connected, changes channels, and releases resources.
Radio resource operation
Clause 3 sets out the main radio resource management functions: cell selection and reselection, connection establishment and release, handover, and support for packet services. For implementers, this means the protocol must track the current mode and use the right control channel behavior for each service.
Connection establishment and paging
Clause 3.3 covers RR connection establishment, including immediate assignment, paging, and notification. This is the part that lets a network reach a mobile station and move it from idle operation into an active radio connection.
Dedicated and group procedures
Clause 3.4 covers the procedures used once a connection exists, including measurement reporting, channel assignment, handover, frequency redefinition, ciphering mode setting, additional assignment, partial release, classmark change, and RR connection release. For operators and testers, these are the procedures that keep calls and services moving while radio conditions or service needs change.
Packet-related procedures
Clause 3.5 covers packet paging, packet access, and packet downlink assignment on CCCH. Clause 3.4.19 to 3.4.24 also cover packet data channel assignment, maintenance, and release in dedicated mode and dual transfer mode (DTM). This matters when a GSM device carries packet traffic alongside circuit-switched service.
Error handling
Clause 8 defines how the protocol reacts to short messages, unknown transaction identifiers, unknown message types, malformed information elements, and incomplete rest octets. These rules matter because different vendors must reject or recover from bad signaling in the same way.
Message and information element coding
Clauses 9 and 10 define the functional contents of RR, mobility management, call control, GPRS mobility management, and session management messages, together with the general message format and information element coding. This is the core reference for implementation and conformance work.
What terms does SIST EN 301 503 V8.4.1:2003 define?
- Idle mode - The mobile station has no dedicated channel and listens to CCCH and BCCH.
- Dedicated mode - The mobile station has at least two dedicated channels, with one being a SACCH.
- Group receive mode - Used for VGCS listening or VBS listening, where the mobile station listens to a voice broadcast or voice group call channel.
- Group transmit mode - Used for VGCS talking, where one mobile station transmits in a voice group call using dedicated channels.
- Packet idle mode - The mobile station has no packet radio resource and monitors the packet or common control channels defined for GPRS operation.
- Packet transfer mode - The mobile station has radio resources on one or more packet data physical channels for LLC PDU transfer.
- Temporary Block Flow (TBF) - A physical connection used for one-directional transfer of LLC PDUs on packet data physical channels.
- Service Access Point Identifier (SAPI) - The identifier used on layer 2 to distinguish signaling and short message transfer access points.
Who uses SIST EN 301 503 V8.4.1:2003?
SIST EN 301 503 V8.4.1:2003 is used by GSM mobile station designers, BSS and network equipment vendors, protocol developers, and conformance test engineers. It is also used by operators, quality managers, and integrators who need to verify interoperability for call setup, mobility, paging, handover, ciphering, and packet signaling. Test laboratories use it together with the cited GSM 11.10 and GSM 11.2x test specifications.
What changed in SIST EN 301 503 V8.4.1:2003 from the previous edition?
The standard notes an added CR history table for SMG#31.
Which standards are used with SIST EN 301 503 V8.4.1:2003?
- GSM04.03 - Defines MS-BSS channel structures and access capabilities used by the procedures.
- GSM04.05 and GSM04.06 - Define the data link layer functions and services used by layer 3.
- TS24.007 - Gives the general layer 3 framework, message format, and error handling rules.
- GSM04.60 - Defines RLC/MAC procedures for packet data physical channels and TBF handling.
- TS23.060 - Defines GPRS service and MS operation modes A, B, and C.
- GSM05.02 - Defines the logical control channels referenced throughout the procedures.
- GSM11.10 and GSM11.21 - Define GSM radio interface signaling conformance testing.
- TS24.071 and GSM04.31 - Provide location services-related procedures and RRLP support.
What does the SIST EN 301 503 V8.4.1:2003 document contain?
The document contains detailed procedure descriptions for idle, dedicated, group receive, group transmit, packet idle, packet transfer, and DTM behavior. It also contains the message functional definitions, the coding of information elements and rest octets, and tables of timers and counters used by RR, mobility management, and call control.
Several annexes provide worked examples and coding guidance rather than new procedures. Annex J gives the algorithm for encoding frequency list information elements, Annex K gives default codings, and Annexes F to I collect GSM-specific cause values for different protocol areas.
Get Certified
Connect with accredited certification bodies for this standard

ANCE
Mexican certification and testing association.

Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 301 503 V8.4.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface layer 3 specification; Radio Resource Control Protocol (GSM 04.18 version 8.4.1 Release 1999)". This standard covers: Added CR history table for SMG#31
Added CR history table for SMG#31
SIST EN 301 503 V8.4.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.50 - Global System for Mobile Communication (GSM). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 301 503 V8.4.1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface layer 3 specification; Radio Resource Control Protocol (GSM 04.18 version 8.4.1 Release 1999)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:EN 301 503 Version 8.4.1SIST EN 301 503 V8.4.1:2003en01-december-2003SIST EN 301 503 V8.4.1:2003SLOVENSKI
STANDARD
ETSIEN301503V8.4.1(2000-10)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);Mobileradiointerfacelayer3specification;RadioResourceControlProtocol(GSM04.18version8.4.1Release1999)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 301 503 V8.4.1:2003
ETSIETSIEN301503V8.4.1(2000-10)2(GSM04.18version8.4.1Release1999)ReferenceREN/SMG-020418Q8R1KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM)ETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 301 503 V8.4.1:2003
ETSIETSIEN301503V8.4.1(2000-10)3(GSM04.18version8.4.1Release1999)ContentsIntellectualPropertyRights.14Foreword.141Scope.151.1ScopeoftheTechnicalSpecification.151.2Applicationtotheinterfacestructures.151.3Structureoflayer3procedures.151.4Testprocedures.151.5Useoflogicalchannels.161.6Overviewofcontrolprocedures.161.6.1Listofprocedures.161.7Applicabilityofimplementations.171.7.1VoiceGroupCallService(VGCS)andVoiceBroadcastService(VBS).171.7.2GeneralPacketRadioService(GPRS).182References.182.1Definitionsandabbreviations.222.1.1Randomvalues.222.1.2Vocabulary.223RadioResourcemanagementprocedures.243.1Overview/General.243.1.1General.243.1.2Servicesprovidedtoupperlayers.243.1.2.1Idlemode.243.1.2.2Dedicatedmode.243.1.2.3Groupreceivemode.253.1.2.4Grouptransmitmode.253.1.2.5Packetidlemode.253.1.2.6Packettransfermode.253.1.2.7Dualtransfermode(DTM).263.1.3Servicesrequiredfromdatalinkandphysicallayers.263.1.4Changeofdedicatedchannels.263.1.4.1ChangeofdedicatedchannelsusingSAPI=0.263.1.4.2ChangeofdedicatedchannelsusingotherSAPIsthan0.263.1.4.3Sequencedmessagetransferoperation.273.1.4.3.1Variablesandsequencenumbers.273.1.4.3.1.1SendstatevariableV(SD).273.1.4.3.1.2SendsequencenumberN(SD).273.1.4.3.2Proceduresfortheinitiation,transferexecutionandterminationofthesequencedmessagetransferoperation.273.1.4.3.2.1Initiation.273.1.4.3.2.2TransferExecution.273.1.4.3.2.3Termination.273.1.5ProcedureforServiceRequestandContentionResolution.283.1.6Preemption.283.2Idlemodeproceduresandgeneralproceduresinpacketidleandpackettransfermodes.293.2.1MobileStationside.293.2.2Networkside.303.2.2.1Systeminformationbroadcasting.303.2.2.2Paging.313.3RRconnectionestablishment.313.3.1RRconnectionestablishmentinitiatedbythemobilestation.313.3.1.1Enteringthededicatedmode:immediateassignmentprocedure.313.3.1.1.1Permissiontoaccessthenetwork.323.3.1.1.2Initiationoftheimmediateassignmentprocedure.323.3.1.1.3Answerfromthenetwork.33SIST EN 301 503 V8.4.1:2003
ETSIETSIEN301503V8.4.1(2000-10)4(GSM04.18version8.4.1Release1999)3.3.1.1.3.1OnreceiptofaCHANNELREQUESTmessage.333.3.1.1.3.2Assignmentrejection.343.3.1.1.4Assignmentcompletion.343.3.1.1.4.1Earlyclassmarksending.353.3.1.1.4.2GPRSsuspensionprocedure.353.3.1.1.5Abnormalcases.363.3.1.2Enteringthegrouptransmitmode:uplinkaccessprocedure.363.3.1.2.1Mobilestationside.363.3.1.2.1.1Uplinkinvestigationprocedure.363.3.1.2.1.2Uplinkaccessprocedure.373.3.1.2.2Networkside.373.3.1.2.3Abnormalcases.373.3.1.3DedicatedmodeandGPRS.383.3.2PagingprocedureforRRconnectionestablishment.383.3.2.1Paginginitiationbythenetwork.383.3.2.1.1PaginginitiationusingpagingsubchannelonCCCH.383.3.2.1.2PaginginitiationusingpagingsubchannelonPCCCH.403.3.2.1.3PaginginitiationusingPACCH.403.3.2.2Pagingresponse.403.3.2.3Abnormalcases.403.3.3Notificationprocedure.403.3.3.1Notificationofacall.413.3.3.2JoiningaVGCSorVBScall.413.3.3.3ReducedNCHmonitoringmechanism.413.3.3.4Notificationresponseprocedure.423.4Proceduresindedicatedmodeandingrouptransmitmode.423.4.1SACCHprocedures.433.4.1.1General.433.4.1.2MeasurementreportandEnhancedMeasurementReport.443.4.1.3Extendedmeasurementreport$(MAFA)$.443.4.2Transferofmessagesandlinklayerserviceprovision.453.4.3Channelassignmentprocedure.453.4.3.1Channelassignmentinitiation.453.4.3.2Assignmentcompletion.463.4.3.3Abnormalcases.473.4.4Handoverprocedure.483.4.4.1Handoverinitiation.483.4.4.2Physicalchannelestablishment.493.4.4.2.1Finelysynchronizedcellcase.503.4.4.2.2Nonsynchronizedcellcase.503.4.4.2.3Pseudo-synchronizedcellcase.503.4.4.2.4Pre-synchronizedcellcase.513.4.4.3Handovercompletion.513.4.4.4Abnormalcases.523.4.5Frequencyredefinitionprocedure.533.4.5.1Abnormalcases.533.4.6Channelmodemodifyprocedure.533.4.6.1Normalchannelmodemodifyprocedure.533.4.6.1.1Initiationofthechannelmodemodifyprocedure.533.4.6.1.2Completionofchannelmodemodifyprocedure.543.4.6.1.3Abnormalcases.543.4.6.2Channelmodemodifyprocedureforavoicegroupcalltalker.543.4.6.2.1Initiationofthechannelmodemodifyprocedure.543.4.6.2.2Completionofmodechangeprocedure.543.4.6.2.3Abnormalcases.543.4.7Cipheringmodesettingprocedure.553.4.7.1Cipheringmodesettinginitiation.553.4.7.2Cipheringmodesettingcompletion.553.4.8Additionalchannelassignmentprocedure.563.4.8.1Additionalassignmentprocedureinitiation.563.4.8.2Additionalassignmentprocedurecompletion.563.4.8.3Abnormalcases.56SIST EN 301 503 V8.4.1:2003
ETSIETSIEN301503V8.4.1(2000-10)5(GSM04.18version8.4.1Release1999)3.4.9Partialchannelreleaseprocedure.563.4.9.1Partialreleaseprocedureinitiation.573.4.9.2Abnormalcases.573.4.10Classmarkchangeprocedure.573.4.11Classmarkinterrogationprocedure.573.4.11.1Classmarkinterrogationinitiation.573.4.11.2Classmarkinterrogationcompletion.583.4.12Indicationofnotificationsandpaginginformation.583.4.13RRconnectionreleaseprocedure.583.4.13.1Normalreleaseprocedure.583.4.13.1.1Channelreleaseprocedureinitiationindedicatedmodeandingrouptransmitmode.583.4.13.1.2Abnormalcases.593.4.13.2Radiolinkfailureindedicatedmode.593.4.13.2.1Mobileside.603.4.13.2.2Networkside.603.4.13.3RRconnectionabortionindedicatedmode.603.4.13.4Uplinkreleaseprocedureingrouptransmitmode.603.4.13.5Radiolinkfailureingrouptransmitmode.613.4.13.5.1Mobileside.613.4.13.5.2Networkside.613.4.14ReceivingaRRSTATUSmessagebyaRRentity.613.4.15Groupreceivemodeprocedures.613.4.15.1Mobilestationside.613.4.15.1.1ReceptionoftheVGCSorVBSchannel.613.4.15.1.2Monitoringofdownlinkmessagesandrelatedprocedures.623.4.15.1.2.1Spare.623.4.15.1.2.2Spare.623.4.15.1.2.3Channelmodemodifyprocedure.623.4.15.1.2.4Notificationandpaginginformation.623.4.15.1.2.4.1UseofReducedNCHmonitoring.623.4.15.1.2.5Uplinkstatusmessages.633.4.15.1.2.6Channelreleasemessage.633.4.15.1.2.7Informationonpagingchannelrestructuring.633.4.15.1.3Uplinkreplyprocedure.633.4.15.1.4Leavingthegroupreceivemode.633.4.15.1.4.1Returningtoidlemode.633.4.15.1.4.2Goingtogrouptransmitmode.643.4.15.2Networkside.643.4.15.2.1ProvisionofmessagesontheVGCSorVBSchanneldownlink.643.4.15.2.1.1General.643.4.15.2.1.2Provisionofgeneralinformationmessages.643.4.15.2.1.3Provisionofmessagesrelatedtothevoicegroupcalluplinkchannel.643.4.15.2.2ReleaseoftheVGCSorVBSChannels.653.4.15.3Failurecases.653.4.16Configurationchangeprocedure.653.4.16.1Configurationchangeinitiation.653.4.16.2Configurationchangecompletion.653.4.16.3Abnormalcases.653.4.17Mappingofuserdatasubstreamsontotimeslotsinamultislotconfiguration.663.4.18Handlingofclassmarkinformationatbandchange.663.4.19AssignmenttoaPacketDatachannel.663.4.19.1AssignmenttoPDCHinitiation.673.4.19.2CompletionoftheAssignmenttoPDCHprocedure.683.4.19.3Abnormalcases.683.4.20RR-NetworkCommandedCellChangeOrder.683.4.20.1RR-networkcommandedcellchangeorderinitiation.693.4.20.2Networkcontrolledcellreselectioncompletion.693.4.20.3Abnormalcases.693.4.21ApplicationProcedures.703.4.21.1General.703.4.21.2LocationServices(LCS).703.4.21.3ApplicationInformationTransfer.70SIST EN 301 503 V8.4.1:2003
ETSIETSIEN301503V8.4.1(2000-10)6(GSM04.18version8.4.1Release1999)3.4.21.3.1NormalProcedurewithoutSegmentation.703.4.21.3.2NormalProcedurewithSegmentation.713.4.21.3.3AbnormalCases.713.4.22RRproceduresrelatedtopacketresourceestablishmentwhileindedicatedmode.723.4.22.1Packetrequestprocedurewhileindedicatedmode.723.4.22.1.1Enteringthedualtransfermode.723.4.22.1.1.1Permissiontoaccessthenetwork.723.4.22.1.1.2Initiationofestablishmentofthepacketrequestprocedure.733.4.22.1.1.3Answerfromthenetwork.733.4.22.1.1.3.1Packetassignment.733.4.22.1.1.3.2RRreallocationonly.733.4.22.1.1.3.3Packetrequestrejection.743.4.22.1.1.4Packetrequestcompletion.743.4.22.1.1.5Abnormalcases.743.4.22.2Packetnotificationprocedureindedicatedmode.743.4.22.2.1Packetnotificationinitiationbythenetwork.753.4.22.2.2Packetnotificationresponse.753.4.22.3Packetdownlinkassignmentindedicatedmode.753.4.22.3.1Initiationofthepacketdownlinkassignmentprocedureindedicatedmode.753.4.22.3.2Packetdownlinkassignmentcompletion.763.4.22.3.3Abnormalcases.763.4.22.4ModificationofpacketresourceswhileinDTM.763.4.23RRproceduresrelatedtopacketresourcemaintenancewhileindualtransfermode.763.4.24RRproceduresrelatedtopacketresourcereleasewhileindualtransfermode.773.5RRproceduresonCCCHrelatedtotemporaryblockflowestablishment.773.5.1PacketpagingprocedureusingCCCH.773.5.1.1Packetpaginginitiationbythenetwork.773.5.1.2Onreceiptofapacketpagingrequest.783.5.2PacketaccessprocedureusingCCCH.783.5.2.1Enteringthepackettransfermode:packetaccessprocedure.783.5.2.1.1Permissiontoaccessthenetwork.783.5.2.1.2Initiationofthepacketaccessprocedure:channelrequest.783.5.2.1.3Packetimmediateassignment.803.5.2.1.3.1OnreceiptofaCHANNELREQUESTorEGPRSPACKETCHANNELREQUESTmessage.803.5.2.1.3.2Onephasepacketaccess.813.5.2.1.3.3Singleblockpacketaccess.823.5.2.1.3.3aMultiblockpacketaccess.823.5.2.1.3.4Packetaccessrejection.833.5.2.1.4Packetaccesscompletion.843.5.2.1.5Abnormalcases.843.5.2.2SendinganRLC/MACcontrolmessage:singleblockpacketaccessprocedure.843.5.3PacketdownlinkassignmentprocedureusingCCCH.843.5.3.1Enteringthepackettransfermode:packetdownlinkassignmentprocedure.843.5.3.1.2Initiationofthepacketdownlinkassignmentprocedure.853.5.3.1.3Packetdownlinkassignmentcompletion.863.5.3.1.4Abnormalcases.863.5.3.2SendinganRLC/MACcontrolmessage:singleblockpacketdownlinkassignmentprocedure.874ElementaryproceduresforMobilityManagement.875Elementaryproceduresforcircuit-switchedCallControl.876Supportforpacketservices.877Examplesofstructuredprocedures.888Handlingofunknown,unforeseen,anderroneousprotocoldata.888.1General.888.2Messagetooshort.888.3Unknownorunforeseentransactionidentifier.888.4Unknownorunforeseenmessagetype.898.5Non-semanticalmandatoryinformationelementerrors.898.5.1Radioresourcemanagement.90SIST EN 301 503 V8.4.1:2003
ETSIETSIEN301503V8.4.1(2000-10)7(GSM04.18version8.4.1Release1999)8.6UnknownandunforeseenIEsinthenon-imperativemessagepart.908.6.1IEIsunknowninthemessage.908.6.2OutofsequenceIEs.908.6.3RepeatedIEs.908.7Non-imperativemessageparterrors.908.7.1SyntacticallyincorrectoptionalIEs.908.7.2ConditionalIEerrors.908.8Messageswithsemanticallyincorrectcontents.918.9Incompleterestoctets.919Messagefunctionaldefinitionsandcontents.919.1MessagesforRadioResourcesmanagement.939.1.1Additionalassignment.949.1.1.1MobileAllocation.959.1.1.2StartingTime.959.1.2Assignmentcommand.959.1.2.1ModeoftheFirstChannel(ChannelSet1)andModeofChannelSet"X"(2=
...



