SIST EN 302 406 V8.0.1:2003
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification (GSM 04.56 version 8.0.1 Release 1999)
- Abstract
To be provided Cordless Telephoney System Stage 3 description
- 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 302 406 V8.0.1:2003 is the Slovenian adoption of ETSI EN 302 406 version 8.0.1 for the GSM Cordless Telephony System (CTS) Phase 1. It specifies CTS radio interface layer 3 procedures at Reference Point Um* for Call Control (CC), Mobility Management (MM) and Radio Resource (RR) management. It is intended for implementations of CTS Mobile Stations (MSs) and Fixed Parts (FPs) that exchange signalling over the CTS control channels.
What does SIST EN 302 406 V8.0.1:2003 specify?
SIST EN 302 406 V8.0.1:2003 defines the layer 3 signalling procedures used on the CTS radio interface for circuit-switched services over CTS. The procedures are expressed as message exchanges on the control channels, and the document is organized around elementary procedures, structured procedures, message definitions, error handling and system parameters.
The scope covers RR, MM and circuit-switched CC for CTS. Supplementary services and point-to-point SMS are handled by other GSM specifications named in the references.
| Annex | What it covers |
|---|---|
| Annex A | Default codings of information elements |
| Annex B | Change history |
What are the key requirements of SIST EN 302 406 V8.0.1:2003?
Radio resource handling
SIST EN 302 406 V8.0.1:2003 requires the MS to monitor the CTSBCH and, when requested, the CTSPCH in CTS-idle mode, and it defines alive check, hunting, group alerting and CTS system information broadcasting on the FP side. In practice, this is the idle-state behaviour that lets a terminal find a known FP, react to paging, and learn the cell information it needs before access.
The standard also defines RR connection establishment by immediate assignment or paging. The MS sends CTSACCESSREQUEST on the CTSARCH, while the FP can answer with CTSIMMEDIATEASSIGNMENT or CTSIMMEDIATEASSIGNMENTREJECT on the CTSAGCH. This is the core access-and-grant exchange that creates a dedicated signalling path.
Dedicated-mode procedures
When an RR connection exists, the standard uses the SACCH for regular CTSMEASUREMENTREPORT signalling from the MS. It also specifies channel assignment, channel mode modify, ciphering mode setting, classmark change and classmark interrogation. In practice, these procedures let the FP reconfigure the radio link, switch ciphering, and collect the information needed to keep the connection usable.
The RR connection release procedure returns the MS to idle mode. The document also defines radio link failure handling, so both sides know how to react if the signalling path is lost during a dedicated connection.
Duplicate protection
The standard defines sequenced message transfer for upper-layer messages sent over RR transport. It uses the send state variable V(SD) and the send sequence number N(SD) so the FP can detect duplicated requests after a channel change. This matters because some messages can be retransmitted when the radio link is moved, and the receiving side must ignore repeats.
Mobility management and identity control
SIST EN 302 406 V8.0.1:2003 defines CTS detach, de-enrolment, mutual authentication, CTSMSI update, enrolment, attach, re-attach and periodic attach update. These procedures control how a MS becomes associated with an FP, proves identity, and keeps its identity data current.
Enrolment uses the CTS-PIN and a physical action on the FP, while mutual authentication can use CTSMSI or IMSI. In practice, this is the part of the system that controls who is allowed to use a given FP and how that permission is verified.
Message handling and protocol robustness
Clause 8 defines actions for messages that are too short, use an unknown transaction identifier or message type, or contain invalid information elements. This makes the signalling behaviour predictable when implementations face malformed or unexpected protocol data.
Clause 11 collects timers and counters for RR, MM and circuit-switched CC. That gives implementers the timeout and retry framework they need for interoperability.
What terms does SIST EN 302 406 V8.0.1:2003 define?
- CTS-idle mode - The MS is not on a dedicated channel and listens to the CTSBCH and, when requested, the CTSPCH.
- CTS-RR connection - The physical connection used by peer entities to carry upper-layer signalling and information flows.
- SAPI - Service Access Point Identifier; the document uses SAPI 0 for signalling and SAPI 3 for short messages.
- CTS-MSI - The CTS Mobile Subscriber Identity used in CTS procedures and updated by the FP when required.
- FPBI - Fixed Part Broadcast Identity, the identity the MS uses to recognize a known FP in idle mode.
- TFH - Total Frequency Hopping, the set of parameters used to define hopping behaviour.
- V(SD) - The send state variable for numbered messages, used to detect duplication.
- N(SD) - The send sequence number assigned to an individual numbered message.
Who uses SIST EN 302 406 V8.0.1:2003?
SIST EN 302 406 V8.0.1:2003 is used by CTS MS and FP designers, protocol stack developers, and integration engineers who need to implement radio access, enrolment, attachment, authentication and call setup. It is also used by test laboratories and quality teams checking signalling behaviour, timers and error handling.
Buyers and technical reviewers use it to confirm that a product supports the CTS procedures they need. That is especially relevant when deciding whether a terminal, base unit or chipset can participate in CTS call control and mobility management.
Which standards are used with SIST EN 302 406 V8.0.1:2003?
- GSM03.52 - Gives the overall description of the CTS radio interface and its stage 2 structure.
- GSM03.56 - Provides the CTS service description and the reference context for Um*.
- GSM04.03 - Defines the MS-BSS interface channel structures and access capabilities used by layer 3.
- GSM04.05 and GSM04.06 - Provide the data link layer services and procedures used underneath layer 3.
- GSM04.07 - Gives the general layer 3 description, including message format and error handling principles.
- GSM04.08 - Supplies shared mobile radio interface layer 3 procedures such as authentication and identity request handling.
- GSM05.08 - Covers radio subsystem link control, including lower-layer failure detection.
- GSM11.10 and GSM11.56 - Define the CTS radio interface signalling test procedures.
What does the SIST EN 302 406 V8.0.1:2003 document contain?
The document includes structured procedure sequences for paging, immediate assignment, alive check, hunting, group alerting, authentication, enrolment, attachment, detachment and call-related signalling. It also shows how RR, MM and CC procedures are built from elementary message exchanges.
Clause 9 defines the functional content of the RR and MM messages, and clause 10 defines the general message format and the coding of protocol discriminator, sub-protocol discriminator, transaction identifier, message type and information elements. Clause 11 lists the system timers and counters used by the procedures.
Annex A gives the default codings of common, RR, MM and CC information elements. Annex B records the change history.
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 302 406 V8.0.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital cellular telecommunications system (Phase 2+) (GSM); GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification (GSM 04.56 version 8.0.1 Release 1999)". This standard covers: To be provided Cordless Telephoney System Stage 3 description
To be provided Cordless Telephoney System Stage 3 description
SIST EN 302 406 V8.0.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 302 406 V8.0.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); GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification (GSM 04.56 version 8.0.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 302 406 Version 8.0.1SIST EN 302 406 V8.0.1:2003en01-december-2003SIST EN 302 406 V8.0.1:2003SLOVENSKI
STANDARD
ETSIEN302406V8.0.1(2000-08)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);GSMCordlessTelephonySystem(CTS),Phase1;CTSradiointerfacelayer3specification(GSM04.56version8.0.1Release1999)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 302 406 V8.0.1:2003
ETSIETSIEN302406V8.0.1(2000-08)2(GSM04.56version8.0.1Release1999)ReferenceREN/SMG-030456Q8KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM),GSMCordlessTelephonySystem(CTS)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 302 406 V8.0.1:2003
ETSIETSIEN302406V8.0.1(2000-08)3(GSM04.56version8.0.1Release1999)ContentsIntellectualPropertyRights.9Foreword.91Scope.101.1ScopeoftheTechnicalSpecification.101.2Applicationtotheinterfacestructures.101.3Structureoflayer3procedures.101.4Testprocedures.101.5Useoflogicalchannels.101.6Overviewofcontrolprocedures.111.6.1Listofprocedures.111.7Applicabilityofimplementations.122References.123Definitions,abbreviationsandRandomvalues.163.1Definitions.163.2Abbreviations.163.3Randomvalues.164Overview/General.164.1Overview.164.1.1General.164.1.2Servicesprovidedtoupperlayers.164.1.2.1CTS-Idlemode.174.1.2.2Dedicatedmode.174.1.3Servicesrequiredfromdatalinkandphysicallayers.174.1.4Changeofdedicatedchannels.174.1.4.1ChangeofdedicatedchannelsusingSAPI=0.174.1.4.2ChangeofdedicatedchannelsusingotherSAPIsthan0.184.1.4.3Sequencedmessagetransferoperation.184.1.4.3.1Variablesandsequencenumbers.184.1.4.3.1.1SendstatevariableV(SD).184.1.4.3.1.2SendsequencenumberN(SD).184.1.4.3.2Proceduresfortheinitiation,transferexecutionandterminationofthesequencedmessagetransferoperation.184.1.4.3.2.1Initiation.184.1.4.3.2.2TransferExecution.194.1.4.3.2.3Termination.194.1.5ProcedureforServiceRequestandContentionResolution.194.2Idlemodeprocedures.194.2.1MobileStationside.194.2.1.1CTSBCHandCTSPCHmonitoring.194.2.1.2Alivecheckresponse.194.2.2CTS-FPside.204.2.2.1CTSBCHinformationbroadcasting.204.2.2.2CTSPCHinformationbroadcasting.204.2.2.3Alivecheck.204.2.2.4Hunting.214.2.2.5Connectionlessgroupalerting.214.2.2.5CTSsysteminformationbroadcasting.234.3RRconnectionestablishment.234.3.1RRconnectionestablishmentinitiatedbythemobilestation.234.3.1.1Enteringthededicatedmode:immediateassignmentprocedure.234.3.1.1.1PermissiontoaccesstheCTS-FP.244.3.1.1.2Initiationoftheimmediateassignmentprocedure.244.3.1.1.3AnswerfromtheCTS-FP.244.3.1.1.3.1OnreceiptofaCTSACCESSREQUESTmessage.24SIST EN 302 406 V8.0.1:2003
ETSIETSIEN302406V8.0.1(2000-08)4(GSM04.56version8.0.1Release1999)4.3.1.1.3.2Assignmentrejection.244.3.1.1.4Assignmentcompletion.244.3.1.1.4.1Earlyclassmarksending.254.3.1.1.5Abnormalcases.254.3.2PagingprocedureforRRconnectionestablishment.254.3.2.1PaginginitiationbytheCTS-FP.254.3.2.2Pagingresponse.254.3.2.3Abnormalcases.254.4Proceduresindedicatedmode.264.4.1SACCHprocedures.264.4.1.1General.264.4.1.2Measurementreport.264.4.2Transferofmessagesandlinklayerserviceprovision.264.4.3Intracellhandoverprocedure.274.4.3.1Intracellhandoverinitiation.274.4.3.2Intracellhandovercompletion.274.4.3.3Abnormalcases.274.4.4Intercellhandoverprocedure.284.4.5Frequencyhoppingdefinitionprocedure.284.4.6Channelmodemodifyprocedure.284.4.6.1Normalchannelmodemodifyprocedure.284.4.6.1.1Initiationofthechannelmodemodifyprocedure.284.4.6.1.2Completionofchannelmodemodifyprocedure.284.4.6.1.3Abnormalcases.284.4.7Cipheringmodesettingprocedure.294.4.7.1Cipheringmodesettinginitiation.294.4.7.2Cipheringmodesettingcompletion.294.4.8[Reserved:Additionalchannelassignmentprocedure].294.4.9[Reserved:Partialchannelreleaseprocedure].294.4.10Classmarkchangeprocedure.304.4.11Classmarkinterrogationprocedure.304.4.12[Reserved].304.4.13RRconnectionreleaseprocedure.304.4.13.1Normalreleaseprocedure.304.4.13.1.1Channelreleaseprocedureinitiation.304.4.13.1.2Abnormalcase.304.4.13.2Radiolinkfai2lureindedicatedmode.304.4.13.2.1Mobileside.314.4.13.2.2CTS-FPside.314.4.13.3RRconnectionabortionindedicatedmode.314.4.14ReceivingCTSRRSTATUSmessagebyaCTS-RRentity.314.4.15CTSRRparametersupdate.315ElementaryproceduresforMobilityManagement.325.1General.325.1.1TypeofCTS-MMprocedures.325.1.2CTS-MMsublayerstates.335.1.2.1CTS-MMsublayerstatesinthemobilestation.335.1.2.1.1Mainstates.335.1.2.1.2SubstatesoftheCTS-MMIDLEstate.335.1.2.2CTS-MMsublayerstatesinthefixedpart.335.2CTS-MMcommonprocedures.345.2.1CTSdetachprocedure.345.2.1.1CTSdetachinitiationbythemobilestation.345.2.1.2CTSdetachprocedureinthefixedpart.345.2.1.3CTSdetachcompletionbythemobilestation.345.2.1.4Abnormalcases.345.2.2CTSde-enrolmentprocedure.345.2.2.1CTSde-enrolmentinitiationbythefixedpart.355.2.2.2CTSde-enrolmentprocedureinthemobilestation.355.2.2.3Abnormalcases.355.2.3CTSmutualauthenticationprocedure.35SIST EN 302 406 V8.0.1:2003
ETSIETSIEN302406V8.0.1(2000-08)5(GSM04.56version8.0.1Release1999)5.2.3.1CTSauthenticationinitiationbythefixedpart.355.2.3.2CTSauthenticationresponsebythemobilestation.355.2.3.3CTSauthenticationprocessingbythefixedpart.365.2.3.4CTSauthenticationcompletionbythemobilestation.365.2.3.5Unsuccessfulauthentication.365.2.3.6Abnormalcases.365.2.4CTSMSIupdateprocedure.365.2.4.1CTSMSIupdateinitiationbythefixedpart.375.2.4.2CTSMSIupdateresponsebythemobilestation.375.2.4.3CTSMSIupdatecompletioninthefixedpart.375.2.4.4Abnormalcases.375.3CTS-MMspecificprocedures.375.3.1CTSenrolmentprocedure.375.3.1.1CTSenrolmentinitiationbythemobilestation.385.3.1.2CTSenrolmentcompletionbythefixedpart.385.3.1.3CTSenrolmentcompletionbythemobilestation.385.3.1.4Unsuccessfulenrolment.385.3.1.5Abnormalcases.385.3.2CTSattachprocedure.385.3.2.1CTSattachinitiationbythemobilestation.385.3.2.2CTSattachcompletionbythefixedpart.385.3.2.3CTSattachcompletionbythemobilestation.395.3.2.4CTSattachrejectiontreatmentbythemobilestation.395.3.2.5Abnormalcases.395.3.3CTSre-attachprocedure.395.3.3.1CTSre-attachinitiationbythemobilestation.395.3.3.2CTSre-attachcompletionbythefixedpart.395.3.3.3Abnormalcases.405.3.4CTSperiodicattachupdateprocedure.405.3.4.1CTSperiodicattachupdateprocedurebehaviourinthefixedpart.405.3.4.2Abnormalcases.406Elementaryproceduresforcircuit-switchedCallControl.406.1Overview.406.1.1General.406.2Hookflashprocedure.416.2.1Hookflashrequestbythemobilestation.416.2.2Hookflashresponsebythefixedpart.416.2.3Stophookflashrequestbythemobilestation.416.2.4Stophookflashresponsebyfixedpart.416.3Internalcallprocedure.417Examplesofstructuredprocedures.417.1General.417.1.1CTSpagingrequest.427.1.2CTSimmediateassignment.427.1.3CTSmutualauthentication.427.2Abnormalcases.427.3Selectedexamples.427.3.1Enrolment.437.3.1.1EnrolmentwithCTS-MSidentityauthenticationdoneonlybytheCTS-FP.437.3.1.2EnrolmentwithCTSMSauthenticationdonebyCTSoperator.447.3.2Attachment.447.3.3Detachment.457.3.4De-enrolment.467.3.5Mobileoriginatingcallestablishment.468Handlingofunknown,unforeseen,anderroneousprotocoldata.478.1General.478.2Messagetooshort.488.3Unknownorunforeseentransactionidentifier.488.4Unknownorunforeseenmessagetype.488.5Non-semanticalmandatoryinformationelementerrors.49SIST EN 302 406 V8.0.1:2003
ETSIETSIEN302406V8.0.1(2000-08)6(GSM04.56version8.0.1Release1999)8.5.1Radioresourcemanagement.498.5.2Mobilitymanagement.498.5.3Callcontrol.498.6UnknownandunforeseenIEsinthenon-imperativemessagepart.508.6.1IEIsunknowninthemessage.508.6.2OutofsequenceIEs.508.6.3RepeatedIEs.508.7Non-imperativemessageparterrors.508.7.1SyntacticallyincorrectoptionalIEs.508.7.2ConditionalIEerrors.508.8Messageswithsemanticallyincorrectcontents.519Messagefunctionaldefinitionsandcontents.519.1MessagesforRadioResourcesmanagement.529.1.1CTSaccessrequest.529.1.2CTSAFAmonitoringcommand.539.1.3CTSAFAmonitoringenquiry.539.1.4CTSAFAmonitoringreport.549.1.5CTSBCCHdetectioncommand.549.1.6CTSBCCHdetectionenquiry.549.1.7CTSBCCHdetectionreport.559.1.8CTSbeaconchannelsynchronisationburstinformation.559.1.9CTSchannelmodemodify.569.1.10CTSchannelmodemodifyacknowledge.569.1.11CTSchannelrelease.569.1.12CTScipheringmodecommand.579.1.13CTScipheringmodecomplete.579.1.14CTSclassmarkchange.589.1.15CTSclassmarkenquiry.589.1.16CTSfrequencyhoppingdefinition.589.1.16.1Referencetime.589.1.17CTSgroupalertingrequest.589.1.17.1RestOctets.599.1.18CTShuntingrequest.599.1.18.1RestOctets.599.1.19CTSimmediateassignment.609.1.20CTSimmediateassignmentextended.609.1.21CTSimmediateassignmentreject.619.1.21.1UseofIndexes.629.1.21.2Fillingofthemessage.629.1.22CTSintracellhandovercommand.629.1.23CTSintracellhandovercomplete.639.1.24CTSintracellhandoverfailure.639.1.25CTSmeasurementreport.649.1.25.1Measurementresults.649.1.26CTSOFOmeasurementcommand.649.1.27CTSOFOmeasurementenquiry.659.1.28CTSOFOMeasurementreport.659.1.29CTSpagingrequest.659.1.29.1Pagingtype.669.1.30CTSpagingresponse.669.1.30.1CipheringKeySequence.679.1.31CTSsysteminformationtype1.679.1.31.1StartingTime.679.1.32CTSsysteminformationtype2.689.1.33CTSsysteminformationtype3.689.1.34CTSRRparametersupdate.689.2Messagesformobilitymanagement.699.2.1CTSattachrequest.699.2.2CTSattachaccept.709.2.3CTSattachreject.709.2.4CTSdetachmentindication.71SIST EN 302 406 V8.0.1:2003
ETSIETSIEN302406V8.0.1(2000-08)7(GSM04.56version8.0.1Release1999)9.2.5CTSenrolmentrequest.719.2.6CTSenrolmentaccept.729.2.7CTSenrolmentreject.729.2.8CTSde-enrolmentindication.739.2.9CTSMSauthenticationrequest.739.2.10CTSMSauthenticationresponse.749.2.11CTSFPauthenticationresponse.749.2.12CTSMSauthenticationreject.759.2.13CTSMSIupdatecommand.759.2.14CTSMSIupdatecomplete.7610Generalmessageformatandinformationelementscoding.7610.1Overview.7610.2ProtocolDiscriminator.7610.3Sub-ProtocolDiscriminatorandtransactionidentifier.7610.3.1Sub-ProtocolDiscriminator.7610.3.2Transactionidentifier.7610.4MessageType.7610.5Otherinformationelements.7810.5.1Commoninformationelements.7810.5.1.1MobileIdentity.7810.5.2RadioResourcemanagementinformationelements.7810.5.2.1CTSMSI.7810.5.2.2TFHGeneralParameters.7910.5.2.3TFHCurrentParameters.7910.5.2.4CTSChannelDescription.8010.5.2.5CTSAccessRequestReference.8010.5.2.6CTSL1information.8110.5.2.7InformationTransfertCapability.8110.5.2.8BCDDisplay.8210.5.2.9AFAInterferenceLevel.8210.5.2.10AFAMonitoringCycles.8310.5.2.11OFOMeasurementResults.8310.5.2.12Pagingtype.8410.5.2.13CTSselectionparameters.8410.5.2.14CTSRRparameters.8510.5.2.15Timeslotshiftingparameters.8510.5.3Mobilitymanagementinformationelements.8610.5.3.1AuthenticationparameterRIMS.8610.5.3.2AuthenticationparameterRIFP.8710.5.3.3AuthenticationparameterCH.8710.5.3.4AuthenticationparameterXRES.8810.5.3.5AuthenticationparameterKax.8810.5.3.6FixedpartIdentity.8910.5.3.7CTSmobilegrouplist.8910.5.3.8Followingattachrequest.9010.5.3.9Accessrightidentity.9010.5.3.10TC3252.9110.5.3.11Attachtype.9110.5.4Callcontrolinformationelements.9210.5.4.1CalledpartyBCDnumber.9210.5.4.2CallingpartyBCDnumber.9210.5.4.3Keypadfacility.
...