SIST EN 300 824 V1.3.1:2003
(Main)Digital Enhanced Cordless Telecommunications (DECT); Cordless Terminal Mobility (CTM); CTM Access Profile (CAP)
- Abstract
Implementation of pending changes requests
- 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 300 824 V1.3.1:2003 is the Slovenski inštitut za standardizacijo adoption of ETSI EN 300 824 V1.3.1 for Digital Enhanced Cordless Telecommunications (DECT) Cordless Terminal Mobility (CTM) Access Profile (CAP). It specifies the DECT Fixed Part (FP) and DECT Portable Part (PP) requirements needed to support CTM phase 2 and to make CAP interoperable between terminals and fixed parts. The document is aimed at implementers, equipment vendors, and testers for DECT telephony and roaming-related functions.
What does SIST EN 300 824 V1.3.1:2003 specify?
SIST EN 300 824 V1.3.1:2003 specifies the CAP technical requirements for DECT FP and PP equipment that support CTM. The profile is an extension of the DECT Generic Access Profile (GAP) mandatory base, and it keeps compatibility with EN 300 175 and GAP where possible.
The scope focuses on air-interface interoperability, telephony teleservice, and 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM) speech bearer service. CTM supplementary services that do not affect the air interface are outside the CAP focus.
| Annex | What it covers |
|---|---|
| A | System parameters |
| B | PP locking procedure for on-air subscription |
| D | Tones, progress indicator and U-plane connection |
| E | PARI and SARI use for CTM roaming |
| F | Class 2 synchronization requirements |
| G | Synchronization requirements for fixed parts |
| H | Coding example for message waiting indication |
| C | Void |
| I | Bibliography |
What are the key requirements of SIST EN 300 824 V1.3.1:2003?
Clause 7 makes the interoperability rules explicit: optional features are still process mandatory if implemented, and all equipment must meet the listed attachment requirements. In practice, this means a CAP FP or PP cannot claim support unless it follows the defined procedures, messages, and information elements.
Main functional areas
- External handover - Clauses 5, 7, and 9 require the FP to indicate only handover candidates that match the PP's access rights and support external handover. This matters because the PP must be able to move an active call between different FPs without breaking the call.
- Emergency call - Clause 9 allows emergency call setup even without valid subscription, and the FP must accept the setup without checking the identities when access rights are unavailable. In practice, this reduces the setup path for urgent calls.
- Display and terminal capability - Clause 9 requires the PP to process display information without needing prior multikeypad information, and to signal CAP support in terminal capability indication. This lets the FP send short text or status indications safely.
- Detach and location registration - Clauses 9 and 14 define detach and enhanced location registration behavior, including retry timing and the effect of broadcast attributes. This keeps the network informed about whether the PP is ready to receive calls and where it is registered.
- Message waiting indication (MWI) - Clause 9 and Clause 14 define MWI signaling, storage, and deletion behavior. The PP stores the indication in volatile memory and clears it on power-down or subscription change.
- On-air modification of user parameters - Clause 9 requires two linked management transactions and authentication of the FT before the PP accepts new user parameters. That protects the active subscription from unauthorized change.
- MAC and physical layer support - Clauses 11 and 12 cover RFP status, extended fixed part capabilities, prolonged preamble support, and synchronization needs for external handover. These functions matter for access selection, roaming, and link robustness.
What terms does SIST EN 300 824 V1.3.1:2003 define?
- Attach - The process by which a PP tells an FP that it is operative and ready to receive calls.
- Detach - The reverse of attach, where the PP reports itself as inoperative.
- External handover - Switching a call in progress from one FP to another FP.
- Location registration - The process that determines a PT's position to location-area level and updates the databases.
- PARI - Primary Access Rights Identity, used to identify the network operator side in DECT roaming and handover decisions.
- SARI - Secondary Access Rights Identity, used to identify the CTM service provider domain.
- TPUI - Temporary Portable User Identity, an individually assigned identity used by the PT during access and location procedures.
- PMID - Portable part MAC Identity, the identity used for link establishment and related MAC procedures.
Who uses SIST EN 300 824 V1.3.1:2003?
SIST EN 300 824 V1.3.1:2003 is used by DECT terminal and base-station manufacturers, CTM service providers, network operators, and interoperability test labs. It is also relevant for integrators and quality teams that need to verify external handover, emergency calling, roaming, subscription control, and message waiting functions in DECT equipment.
Which standards are used with SIST EN 300 824 V1.3.1:2003?
| Reference | What it contributes |
|---|---|
| EN 300 175-1 to EN 300 175-8 | The DECT Common Interface base: overview, PHL, MAC, DLC, NWK, identities and addressing, security, and speech coding/transmission |
| EN 300 444 | The DECT Generic Access Profile base used throughout for common procedures and requirements |
| EN 301 273 | The CTM phase 2 service description |
| ETS 300 176 | Approval test specification for DECT |
| TBR 6, TBR 10, TBR 22 | Terminal attachment and GAP application requirements |
| EN 300 745-1 | Message Waiting Indication (MWI) supplementary service protocol |
| EN 300 196-1 | DSS1 generic functional protocol for supplementary services |
| ISO/IEC 9646-7 | Conformance testing methodology and implementation conformance statements |
What does the SIST EN 300 824 V1.3.1:2003 document contain?
The document contains feature definitions, service definitions, interoperability requirements, and detailed procedure descriptions for the CAP. Clauses 9 to 15 specify message flows, information-element handling, and exception cases for external handover, emergency calls, display, detach, location registration, MWI, on-air modification, MAC procedures, physical-layer requirements, speech transmission, management procedures, and application procedures.
It also includes several tables that code required values for CC, MM, MAC, and FACILITY messages. These tables are used for implementation, interoperability testing, and conformance checking rather than for general reading.
Annex A gives system parameters for handover and location retry behavior, while Annex F and Annex G define synchronization requirements for fixed parts. Annex H provides an illustrative coding example for MWI signaling, which helps implementers map the abstract procedure to actual protocol encoding.
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 300 824 V1.3.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Enhanced Cordless Telecommunications (DECT); Cordless Terminal Mobility (CTM); CTM Access Profile (CAP)". This standard covers: Implementation of pending changes requests
Implementation of pending changes requests
SIST EN 300 824 V1.3.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 824 V1.3.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.RVWDigital Enhanced Cordless Telecommunications (DECT); Cordless Terminal Mobility (CTM); CTM Access Profile (CAP)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 824 Version 1.3.1SIST EN 300 824 V1.3.1:2003en01-december-2003SIST EN 300 824 V1.3.1:2003SLOVENSKI
STANDARD
ETSIEN300824V1.3.1(2001-08)EuropeanStandard(Telecommunicationsseries)DigitalEnhancedCordlessTelecommunications(DECT);CordlessTerminalMobility(CTM);CTMAccessProfile(CAP)SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)2ReferenceREN/DECT-A0198KeywordsCAP,CTM,DECT,synchronizationETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)3ContentsIntellectualPropertyRights.6Foreword.61Scope.72References.73Definitions,symbolsandabbreviations.83.1Definitions.83.2Symbols.103.3Abbreviations.114Introduction.125Featuredefinitions.125.1Network(NWK)features.125.1.1Applicationfeatures.126Servicedefinitions.136.1DLCservicedefinitions.136.2MediumAccessControl(MAC)servicedefinitions.137Interoperabilityrequirements.137.1General.137.2NWKfeatures.147.3DLCservices.147.4MACservices.147.5PhysicalLayer(PHL)services.147.6Applicationfeatures.147.7NWKfeaturetoproceduremapping.157.8Servicetoproceduremapping.167.8.1DLCservicetoproceduremapping.167.8.2MACservicetoproceduremapping.167.8.3Applicationfeaturetoproceduremapping.167.9Generalrequirements.177.9.1CoexistenceofMMandCCprocedures.178Proceduredescription.179NWKlayerprocedures.189.1Externalhandoverprocedures.189.1.1Handovercandidateprocedure.189.1.1.1Handovercandidateindication.189.1.1.2Handovercandidateretrieval.199.1.1.2.1Exceptionalcases.209.1.2TargetFPselection.209.1.3Handoverreferenceprocedure.209.1.3.1Handoverreferenceindication.209.1.3.2Handoverreferenceretrieval.209.1.3.2.1Exceptionalcases.229.1.4Externalhandovercallset-up.229.1.4.1Associatedprocedures.229.1.4.1.1Transactionidentifierhandling.229.1.4.2Exceptionalcases.239.1.4.2.1AbnormallinkreleaseonFP-1leg.239.1.4.2.2NormalcallreleaseonFP-2leg.239.1.4.2.3AbnormallinkreleaseonFP-2leg.239.1.5Cipheringprocedure.239.1.5.1CipheringprocedurePTinitiated.239.1.5.2CipheringprocedureFTinitiated.23SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)49.1.6U-planehandling.239.2Emergencycallset-up.239.3Display.249.4Terminalcapabilityindication.259.5Detach.259.6Enhancedlocationregistration.259.6.1Exceptionalcase(s).269.6.1.1Failureoflocationregistrationprocedure.269.7Messagewaitingindication.269.7.1MWIIndicate-activation.279.7.2MWIIndicate-deactivation.289.7.3Retrievalofthemessage.299.8On-airmodificationofuserparameters.299.8.1Exceptionalcases.309.8.1.1Collisionwithnormalcallprocedure.3010DLClayerprocedures.3011MAClayerprocedures.3011.1General.3011.2Downlinkbroadcast.3011.3Non-continuousbroadcast.3111.3.1Mtmessage.3111.3.1.1Extendedsysteminformation.3111.3.1.2TARImessage.3211.4RFPstatus.3211.4.1RFPstatusinformation.3311.5Extendedfixedpartcapabilities.3311.6Prolongedpreamble.3411.6.1ProcedureforprolongedpreamblediversityinRFPandprolongedpreambletransmissioninPP.3411.6.2ProcedureforprolongedpreamblediversityinPPandprolongedpreambletransmissioninRFP.3412Physicallayerrequirements.3412.1General.3412.2Externalhandover.3412.3ProlongedPreamble.3413Requirementsregardingthespeechtransmission.3413.1General.3413.2ReferencetoGAP.3414Managementprocedures.3514.1General.3514.2Locationregistrationinitiation.3514.3AssignedindividualTemporaryPortableUserIdentity(TPUI)management.3514.4Detach.3614.5Externalhandover.3614.6Emergencycallmanagement.3614.7PMIDmanagement.3714.8Broadcastattributesmanagement.3714.9Messagewaitingindication.3715Applicationprocedures.3815.1General.3815.2Subscriptioncontrol.38AnnexA(normative):Systemparameters.39A.1NWKlayerconstants.39A.2PHLconstants.39AnnexB(informative):PPlockingprocedureforonairsubscription.40AnnexC(informative):Void.41SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)5AnnexD(informative):Tones,progressindicatorandU-planeconnection.42AnnexE(informative):PARIandSARIuseforCTMroaming.43AnnexF(normative):Class2synchronizationrequirements.45AnnexG(normative):Synchronizationrequirementsforfixedparts.46AnnexH(informative):Codingexampleformessagewaitingindication.47AnnexI(informative):Bibliography.48History.49SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSIProjectDigitalEnhancedCordlessTelecommunications(DECT).ThepresentdocumentisbasedonEN300175,parts1to8[1]to[8]andEN300444[12].NationaltranspositiondatesDateofadoptionofthisEN:10August2001DateoflatestannouncementofthisEN(doa):30November2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31May2002DateofwithdrawalofanyconflictingNationalStandard(dow):31May2002SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)71ScopeThepresentdocumentspecifiesthatsetoftechnicalrequirementsforDigitalEnhancedCordlessTelecommunications(DECT)FixedPart(FP)andDECTPortablePart(PP)necessaryforthesupportoftheCordlessTerminalMobility(CTM)AccessProfile(CAP).TheobjectiveofthepresentdocumentistoensuretheairinterfaceinteroperabilityofDECTCAPPPsandDECTCAPFPsifapplied.TheCTMserviceallowsusersofcordlessterminalstobemobilewithinandbetweennetworks.Whereradiocoverageisprovidedandthecordlessterminalhasappropriateaccessrightstheusershallbeabletomakecallsfrom,andtoreceivecallsat,anylocationwithinthefixedpublicand/orprivatenetworks,andmaymovewithoutinterruptionofacallinprogress.ThepresentdocumentcoverstheDECTaccessrequirementsforCTMphase2asdefinedintheCTMphase2servicedescription,EN301273[14].ThemainobjectivesoftheCAPare:-maintaincompatibilitywiththeDECTGenericAccessProfile(GAP),identifyingonlycomponentsnotmandatoryintheGAPtobeaddedtoobtaincapabilitiesneededintheCTMcontext;-maintaincompatibilitywithEN300175parts1to8[1]to[8],forproceduresnotdefinedintheGAP.TheCTMaccessprofileisseenasanextensionoftheGAPmandatorybasecoveringtherequirementsforCTMphase2.CAPsupportstelephonyteleserviceandprovides32kbit/sAdaptiveDifferentialPulseCodeModulation(ADPCM)speechbearerservice.CTMsupplementaryserviceswithnoimpactontheairinterfacearenotconsideredintheCAP.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN300175-1:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part1:Overview".[2]ETSIEN300175-2:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part2:Physicallayer(PHL)".[3]ETSIEN300175-3:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part3:MediumAccessControl(MAC)layer".[4]ETSIEN300175-4:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part4:DataLinkControl(DLC)layer".[5]ETSIEN300175-5:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part5:Network(NWK)layer".[6]ETSIEN300175-6:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part6:Identitiesandaddressing".SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)8[7]ETSIEN300175-7:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part7:Securityfeatures".[8]ETSIEN300175-8:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part8:Speechcodingandtransmission".[9]ETSIETS300176:"DigitalEnhancedCordlessTelecommunications(DECT);Approvaltestspecification".[10]ETSITBR6:"DigitalEnhancedCordlessTelecommunications(DECT);Generalterminalattachmentrequirements".[11]ETSITBR10(1997):"DigitalEnhancedCordlessTelecommunications(DECT);Generalterminalattachmentrequirements;Telephonyapplications".[12]ETSIEN300444:"DigitalEnhancedCordlessTelecommunications(DECT);GenericAccessProfile(GAP)".[13]ETSITBR22:"RadioEquipmentandSystems(RES);AttachmentrequirementsforterminalequipmentforDigitalEnhancedCordlessTelecommunications(DECT)GenericAccessProfile(GAP)applications".[14]ETSIEN301273:"CordlessTerminalMobility(CTM);Phase2;Servicedescription".[15]ETSIEN300745-1:"IntegratedServicesDigitalNetwork(ISDN);MessageWaitingIndication(MWI)supplementaryservice;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".[16]ISO/IEC9646-7(1995):"Informationtechnology-OpenSystemsInterconnection-Conformancetestingmethodologyandframework-Part7:ImplementationConformanceStatements".[17]ETSIEN300196-1:"IntegratedServicesDigitalNetwork(ISDN);Genericfunctionalprotocolforthesupportofsupplementaryservices;DigitalSubscriberSignallingSystemNo.one(DSS1)protocol;Part1:Protocolspecification".3Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:attach:processwherebyaPPwithinthecoverageareaofaFPtowhichithasaccessrights,notifiesthisFPthatitisoperative.Thereverseprocessisdetach,whichreportsthePPasinoperativeNOTE1:AnoperativePPisassumedtobereadytoreceivecalls.authentication:processwherebyaCTMsubscriberispositivelyverifiedtobealegitimateuseroftheCTMserviceNOTE2:Authenticationisgenerallyperformedatcallset-up,butmayalsobedoneatanyothertime(e.g.duringacall).bearerservice:typeoftelecommunicationservicethatprovidesadefinedcapabilityforthetransmissionofsignalsbetweenuser-networkinterfacesNOTE3:TheDECTuser-networkinterfacecorrespondstothetopofthenetworklayer(layer3).C-plane:controlplaneoftheDECTprotocolstacks,whichcontainsalloftheinternalDECTprotocolcontrol,butmayalsoincludesomeexternaluserinformationNOTE4:TheC-planestackalwayscontainsprotocolentitiesuptoandincludingthenetworklayer.SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)9call:alloftheNetwork(NWK)layerprocessesinvolvedinonenetworklayerpeer-to-peerassociationNOTE5:Callmaysometimesbeusedtorefertoprocessesofalllayers,sincelowerlayerprocessesareimplicitlyrequired.DECTnetwork:networkthatusestheDECTairinterfacetointerconnectalocalnetworktooneormoreportableapplications.ThelogicalboundariesoftheDECTnetworkaredefinedtobeatthetopoftheDECTnetworklayerNOTE6:ADECTnetworkisalogicalgroupingthatcontainsoneormorefixedradioterminationsplustheirassociatedportableradiotermination.TheboundariesoftheDECTnetworkarenotphysicalboundaries.externalhandover:processofswitchingacallinprogressfromonefixedparttoanotherfixedpartFixedPart(DECTFixedPart)(FP):physicalgroupingthatcontainsalloftheelementsintheDECTnetworkbetweenthelocalnetworkandtheDECTairinterfaceNOTE7:ADECTFPcontainsthelogicalelementsofatleastoneFT,plusadditionalimplementationspecificelements.FixedradioTermination(FT):logicalgroupoffunctionsthatcontainsalloftheDECTprocessesandproceduresonthefixedsideoftheDECTairinterfaceNOTE8:AFTonlyincludeselementsthataredefinedintheDECTCommonInterface(CI)standard.Thisincludesradiotransmissionelementstogetherwithaselectionoflayer2andlayer3elements.geographicallyuniqueidentity:termrelatestoFPidentities,PrimaryAccessRightsIdentities(PARIs)andRadioFixedPartIdentities(RFPIs).ItindicatesthattwosystemswiththesamePARI,orrespectivelytwoRadioFixedParts(RFPs)withthesameRFPI,cannotbereachedorlistenedtoatthesamegeographicalpositionNOTE9:ForPARIandRFPIseeabbreviations.globalnetwork:telecommunicationnetworkcapableofofferingalongdistancetelecommunicationserviceNOTE10:Thetermdoesnotincludelegalorregulatoryaspects,nordoesitindicateifthenetworkisapublicoraprivatenetwork.globallyuniqueidentity:identityisuniquewithinDECT(withoutgeographicalorotherrestrictions)handover:processofswitchingacallinprogressfromonephysicalchanneltoanotherphysicalchannelNOTE11:Therearetwophysicalformsofhandover,intra-cellhandoverandinter-cellhandover.incomingcall:callreceivedataPPinter-cellhandover:switchingofacallinprogressfromonecelltoanothercellinternalhandover:handoverprocessesthatarecompletelyinternaltooneFT.Internalhandoverreconnectsthecallatthelowerlayers,whilemaintainingthecallattheNWKlayerNOTE12:ThelowerlayerreconnectioncaneitherbeattheDataLinkControl(DLC)layer(connectionhandover)orattheMAClayer(bearerhandover).interoperability:capabilityofFPsandPPs,thatenableaPPtoobtainaccesstoteleservicesinmorethanonelocationareaand/orfrommorethanoneoperator(morethanoneserviceprovider)interoperatorroaming:roamingbetweenFPcoverageareasofdifferentoperators(differentserviceproviders)InterworkingUnit(IWU):unitthatisusedtointerconnectsubnetworksNOTE13:TheIWUwillcontaintheinterworkingfunctionsnecessarytosupporttherequiredsubnetworkinterworking.intra-cellhandover:switchingofacallinprogressfromonephysicalchannelofonecelltoanotherphysicalchannelofthesamecellintraoperatorroaming:roamingbetweendifferentFPcoverageareasofthesameoperator(sameserviceprovider)SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)10LocalNetwork(LNW):telecommunicationnetworkcapableofofferinglocaltelecommunicationservicesNOTE14:Thetermdoesnotincludelegalorregulatoryaspects,nordoesitindicateifthenetworkisapublicnetworkoraprivatenetwork.locallyuniqueidentity:uniqueidentitywithinoneFPorlocationarea,dependingonapplicationlocationarea:domaininwhichaPPmayreceive(and/ormake)callsasaresultofasinglelocationregistrationlocationregistration:processwherebythepositionofaDECTPTisdeterminedtothelevelofonelocationarea,andthispositionisupdatedinoneormoredatabasesNOTE15:ThesedatabasesarenotincludedwithinaDECTFT.MACConnection(CONNECTION):associationbetweenonesourceMACMulti-BearerControl(MBC)entityandonedestinationMediumAccessControl(MAC)Multi-BearerControl(MBC)entityNOTE16:ThisprovidesasetofrelatedMACservices(asetoflogicalchannels),anditcaninvolveoneormoreunderlyingMACbearers.outgoingcall:calloriginatingfromaPPPortableApplication(PA):logicalgroupingthatcontainsalltheelementsthatliebeyondtheDECTnetworkboundaryontheportablesideNOTE17:ThefunctionscontainedinthePAmaybephysicallydistributed,butanysuchdistributionisinvisibletotheDECTnetwork.PortablePart(DECTPortablePart)(PP):physicalgroupingthatcontainsallelementsbetweentheuserandtheDECTairinterface.PPisagenerictermthatmaydescribeoneorseveralphysicalpiecesNOTE18:ADECTPPislogicallydividedintoonePTplusoneormorePAs.PortableradioTermination(PT):logicalgroupoffunctionsthatcontainsalloftheDECTprocessesandproceduresontheportablesideoftheDECTairinterfaceNOTE19:APTonlyincludeselementsthataredefinedintheDECTCIstandard.Thisincludesradiotransmissionelements(layer1)togetherwithaselectionoflayer2andlayer3elements.RadioFixedPart(RFP):physicalsub-groupofaFPthatcontainsalltheradioendpoints(oneormore)thatareconnectedtoasinglesystemofantennasroaming:movementofaPPfromoneFPcoverageareatoanotherFPcoveragearea,wherethecapabilitiesoftheFPsenablethePPtomakeorreceivecallsinbothareasNOTE20:RoamingrequirestherelevantFPsandPPtobeinteroperable.subscriptionregistration:infrequentprocesswherebyasubscriberobtainsaccessrightstooneormoreFPsNOTE21:Subscriptionregistrationisusuallyrequiredbeforeausercanmakeorreceivecalls.supplementaryservice:servicethatmodifiesorsupplementsabasictelecommunicationsserviceteleservice:typeoftelecommunicationsservicethatprovidesthecompletecapability,includingterminalequipmentfunctions,forcommunicationbetweenusers,accordingtoprotocolsthatareestablishedbyagreement3.2SymbolsForthepurposesofthepresentdocument,thefollowingsymbolsapply.Thesymbolsdefinedinthisclauseareappliedforprocedures,features,andservicesinthepresentdocumentifnotexplicitlyotherwisestated.Theinterpretationofstatuscolumnsinalltablesisasfollows:Mformandatorytosupport(provisionmandatory,processmandatory)Oforoptionaltosupport(provisionoptional,processmandatory)Iforout-of-scope(provisionoptional,processoptional)notsubjectfortestingSIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)11Cforconditionaltosupport(processmandatory)N/Afornot-applicable(inthegivencontextthespecificationmakesitimpossibletousethiscapability)Provisionmandatory,processmandatorymeansthattheindicatedfeature,serviceorprocedureshallbeimplementedasdescribedinthepresentdocument,andmaybesubjecttotesting.Provisionoptional,processmandatorymeansthattheindicatedfeature,serviceorproceduremaybeimplemented,andifimplemented,thefeature,serviceorprocedureshallbeimplementedasdescribedinthepresentdocument,andmaybesubjecttotesting.NOTE:TheusednotationisbasedonthenotationproposedinISO/IEC9646-7[16].3.3AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ADPCMAdaptiveDifferentialPulseCodeModulationARCAccessRightsClassARDAccessRightsDetailsARIAccessRightsIdentityBBusiness(environment)CAPCTMAccessProfileCCCallControlCICommonInterfaceCLIPCallingLineIdentificationPresentationCTMCordlessTerminalMobilityDECTDigitalEnhancedCordlessTelecommunicationsDLCDataLinkControlEMCEquipmentManufacturerCodeFPFixedPartFTFixedradioTerminationGAPGenericAccessProtocolIEInformationElementIPEIInternationalPortableEquipmentIdentityIPUIInternationalPortableUserIdentityISDNIntegratedServicesDigitalNetworkIWUInterworkingUnitLALocationAreaLAILocationAreaIdentificationLALLocationAreaLevelLCELinkControlEntityLNWLocalNetworkMACMediumAccessControlMBCMulti-BearerControlMMMobilityManagement,aNWKlayerfunctionalgroupingMWIMessageWaitingIndicationNWKNetwork,Layer3oftheDECTprotocolstackPPublic(environment)PAPortableApplicationPARIPrimaryAccessRightsIdentityPARKPortableAccessRightsKeyPHLPhysicalLayerPLIParkLengthIndicatorPMIDPortablepartMACIdentityPPPortablePartPSNPortableequipmentSerialNumberPTPortableradioTerminationPUNPortableUserNumberPUTPortableUserTypeRESAResponsecalculatedbyaPPRFPRadioFixedPartRFPIRadioFixedPartIdentitySIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)12RResidential(environment)SAPServiceAccessPointSARISecondaryAccessRightsIdentityTARITertiaryAccessRightsIdentityTPUITemporaryPortableUserIdentity4IntroductionThisprofileisanextensionofEN300444[12]coveringtherequirementsforCTMphase2.InthefollowingclausesonlydifferenceswithrespecttoEN300444[12]areexplicitlymentioned.5FeaturedefinitionsForthepurposesofthepresentdocument,thefeaturedefinitionsinthefollowingclausesapply.Thereferencegiveninparenthesesafterthenameofafeatureistheitemreferenceusedinthetablesofthepresentdocument.5.1Network(NWK)featuresThefollowingdifferencesfromtheGAPareapplicable.DECTexternalhandover(CAP-N.1):ExternalhandoveristheprocessofswitchingacallinprogressfromoneFixedPart(FP-1)toanotherFixedPart(FP-2).Thismeansthehandoveroccursbetweentwoindependentsystems,whereeachsystemhasitsownlowerlayersofprotocolandhasanindependentsetofnetworklayerServiceAccessPoints(SAPs).Tomakeexternalhandoverpossible,acommonmanagemententityabovethetwofixedterminationsisnecessary.Emergencycall(CAP-N.2):Thisservicefeatureenablesausertomakeanemergencycallevenwithoutavalidsubscription,i.e.afastandeasymeansofgivinginformationaboutanemergencysituationtotheappropriateemergencyorganization(e.g.fireservice,policeandambulance).Displaymanagement(CAP-N.3):Thisfeatureenablesausertoreceiveshortalphanumericindicationsdisplayedonthescreenterminal.Theseindicationscouldbeassociatedwithsupplementaryorvalueaddedservices.Messagewaitingindication(CAP-N.4):Thisfeatureenablesausertoreceiveanindicationofthestatusofamessageserver(e.g.avoicemailbox)towhichtheuserhasaccess.Detach(CAP-N.5):ThisfeatureenablesaPTtoreporttotheFTthatthePTisnotreadytoreceivecalls.Enhancedlocationregistration(CAP-N.6):ThisfeatureenablesautomaticlocationregistrationofPTatexpectedintervalsoftime.On-airmodificationofuserparameters(CAP-N.7):ThisfeatureenablestheFTtomodifytheactivesubscriptiondataofthePT.5.1.1ApplicationfeaturesSeeEN300444[12].SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)136ServicedefinitionsForthepurposesofthepresentdocument,thefollowingservicedefinitionsapply.6.1DLCservicedefinitionsSeeEN300444[12].6.2MediumAccessControl(MAC)servicedefinitionsThefollowingdifferencesfromtheGAPareapplicable.TertiaryAccessRightsIdentity(TARI)support(CAP-M.1):TheabilitytosupportinadditiontotheprimaryAccessRightsIdentity(ARI)andsecondaryARIstertiaryARIsthattheFTdoesnotbroadcastandareonlyavailabletoPTasaYes/NoansweruponarequestincludingthewantedARI.Thesemaybeusedtoreflectaninter-operatorsagreementallowingaportabletoaccessmorethanoneoperatororservicesthroughFT.RFPstatus(CAP-M.2):AservicewhichindicatestothePPthestatus(busyorclear)oftheRFPorthesystem(FP).Extendedfixedpartcapabilities(CAP-M.3):AservicewhichindicatestothePPtheextendedcapabilitiesoftheFP.ProlongedpreamblediversityinRFP(CAP-M.4):TheabilityoftheRFPtosupportantennadiversitybasedonthereceptionofaprolongedpreamble.ProlongedpreamblediversityinPP(CAP-M.5):TheabilityofthePPtosupportantennadiversitybasedonthereceptionofaprolongedpreamble.ProlongedpreambletransmissionoftheRFP(CAP-M.6):TheabilityoftheRFPtotransmitprolongedpreambleifthePPsupportsprolongedpreamblediversity.ProlongedpreambletransmissionofthePP(CAP-M.7):TheabilityofthePPtotransmitprolongedpreambleiftheRFPsupportsprolongedpreamblediversity.7Interoperabilityrequirements7.1GeneralThetableslistedinthisclausedefinealltheprotocolelementsi.e.features,services,andprocedureswhicharemandatory,optional,andconditionalundertheprovisionofanotherprotocolelement,oroutofthescopeofthepresentdocument,orinsomecontextnot-applicableaccordingtothedefinitionofthestatuscolumnasdefinedinclause3.3fortheCAPFPandPP.Alloptionalelementsshallbeprocessmandatoryaccordingtotheproceduresdescribedinthepresentdocument.Protocolelementsdefinedasmandatory,optionalorconditionalinthisclauseshallfurtherbedefinedinclauses8to15indetaileitherexplicitlyand/orasreferencestotheDECTbasestandard,EN300175part2[2]topart8[8]andETS300176[9].TherequirementsofTBR6[10],TBR10[11]andTBR22[13]shallbemetbyallequipmentconformingtothepresentdocument.SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)147.2NWKfeaturesTable1:NWKfeaturesstatusFeaturesupportedStatusItemno.NameoffeatureCAPRef.GAPRef.PTFTRBPN.11Locationregistration4.1MOMMN.20TerminateaccessrightsFTinitiated4.1MOOMN.30CallingLineIdentificationPresentation(CLIP)4.1MOOMCAP-N.1DECTExternalhandover5.1MOOMCAP-N.2Emergencycall5.1MOOMCAP-N.3DisplayManagement5.1MOOMCAP-N.4MessageWaitingIndication5.1MOOMCAP-N.5Detach5.1MOOMCAP-N.6Periodiclocationregistration5.1MOOMCAP-N.7On-airmodificationofuserparameters5.1MOOO7.3DLCservicesSeeclause6.3ofEN300444[12].7.4MACservicesTable2:MACservicesstatusServicesupportedStatusItemno.NameofserviceCAPRef.GAPRef.PTFTRBPCAP-M.1TARIsupport6.2OOOOCAP-M.2RFPstatus6.2MOMMCAP-M.3Extendedfixedpartcapabilities6.2MOOMCAP-M.4ProlongedpreamblediversityinRFP6.2N/AOOOCAP-M.5ProlongedpreamblediversityinPP6.2ON/AN/AN/ACAP-M.6ProlongedpreambletransmissioninRFP6.2N/AOOOCAP-M.7ProlongedpreambletransmissioninPP6.2MN/AN/AN/A7.5PhysicalLayer(PHL)servicesSeeclause6.5ofEN300444[12].7.6ApplicationfeaturesSeeclause6.6ofEN300444[12].SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)157.7NWKfeaturetoproceduremappingTable3:NWKfeaturetoproceduremappingFeature/ProceduremappingStatusFeatureProcedureCAPRef.GAPRef.PTFTRBPN.11Locationregistration4.1MOMMN.20TerminateaccessrightsFTinitiated4.1MOOMFTauthentication8.23MMMMN.30,CallingLineIdentificationPresentation(CLIP)4.1MOOMIncomingcallrequest8.12MMMMCAP-N.1,DECTExternalhandover5.1MOOMHandovercandidateindication9.1.1.1MMMMHandovercandidateretrieval9.1.1.2MOOOTargetFPselection9.1.2MN/AN/AN/AHandoverreferenceindication9.1.3.1MC1C1C1Handoverreferenceretrieval9.1.3.2MC2C2C2Externalhandovercallset-up9.1.4MMMMCipheringprocedurePTinitiated9.1.5.1OC3C3C3CipheringprocedureFTinitiated9.1.5.2MC4C4MU-planehandling9.1.6MOMMCAP-N.2,Emergencycall5.1MOOMEmergencycallset-up9.2MMMMCAP-N.3,DisplayManagement5.1MOOMDisplay9.3MMMMTerminalcapabilityindication9.4MMMMCAP-N.4,MessageWaitingIndication5.1MOOMMessagewaitingindication9.7MMMMCAP-N.5,Detach5.1MOOMDetach9.5MMMMCAP-N.6,Periodiclocationregistration5.1MOOMEnhancedlocationregistration9.6MMMMCAP-N.7,On-airmodificationofuserparameters5.1MOOOOn-airmodificationofuserparameters9.8MMMMFTauthentication8.23MMMMC1IFprocedure9.1.3.2supportedTHENOELSEM.C2IFprocedure9.1.3.1supportedTHENOELSEM.C3IFfeatureN.27ofEN300444[12]THENMELSEO.C4IFfeatureN.17ofEN300444[12]THENMELSEO.SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)167.8Servicetoproceduremapping7.8.1DLCservicetoproceduremappingSeeclause6.8.1ofEN300444[12].7.8.2MACservicetoproceduremappingTable4:MACservicetoproceduremappingService/ProceduremappingStatusServiceProcedureCAPRef.GAPRef.PTFTRBPCAP-M.1TARIsupport6.2OOOONon-continuousbroadcast11.3MMMMCAP-M.2RFPstatus6.2MOMMRFPstatus11.4MMMMCAP-M.3Extendedfixedpartcapabilities6.2MOOMExtendedfixedpartcapabilities11.5MMMMCAP-M.4.ProlongedpreamblediversityinRFP6.2N/AOOOProlongedpreamblediversityinRFPandprolongedpreambletransmissioninPP11.6.1N/AMMMCAP-M.5.ProlongedpreamblediversityinPP6.2ON/AN/AN/AProlongedpreamblediversityinPPandprolongedpreambletransmissioninRFP11.6.2MN/AN/AN/ACAP-M.6.ProlongedpreambletransmissioninRFP6.2N/AOOOProlongedpreamblediversityinPPandprolongedpreambletransmissioninRFP11.6.2N/AMMMCAP-M.7.ProlongedpreambletransmissioninPP6.2MN/AN/AN/AProlongedpreamblediversityinRFPandprolongedpreambletransmissioninPP11.6.1MN/AN/AN/A7.8.3ApplicationfeaturetoproceduremappingTable5:ApplicationfeaturetoproceduremappingFeature/ProceduremappingStatusFeatureProcedureCAPRef.GAPRef.PTFTRBPA.2Multiplesubscriptionregistration4.2MN/AN/AN/ASubscriptioncontrol15.214.1MN/AN/AN/ASIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)177.9GeneralrequirementsSeeclauses6.9.1to6.9.7ofEN300444[12].7.9.1CoexistenceofMMandCCproceduresInadditiontoclause6.9.6ofEN300444[12],thefollowingdefinitionregardingfeatures(CAP-N.5)and(CAP-N.7)shallapply.Table6FeatureProcedureMandatorysupportinCCstate(CAP-N.5)DetachAllstates(CAP-N.7)On-airmodificationofuserparametersT(F)-008ProceduredescriptionClauses9to15definetheprocessmandatoryprocedureswhichareinthescopeoftheCAP.Eachprocedure(ifappropriate)isdividedintothreeparts:a)normal(i.e.successfulcase).Thispartdefinesthefunctionsandrespectiveprotocolelementvaluesinnormaloperation;b)associatedprocedure(s).Thisisanintegralpartoftheactualprocedure(ifdefinedinthepresentdocument)i.e.ifaprocedureisbeingdeclaredtobesupported,therespectiveentityshallalsosupporttheassociatedprocedures,e.g.timermanagement,intheclausefollowingthedescriptionofthenormalcase;c)exceptionalcase(s).Thisisanintegralpartoftheactualprocedure(ifdefinedinthepresentdocument)i.e.ifaprocedureisbeingdeclaredtobesupported,therespectiveentityshallalsosupporttheexceptionhandlingdefinedintheclausefollowingthedescriptionofthenormalcase.Allprotocolelementslistedinthefollowingclausesareprocessmandatoryi.e.theFTandPTdependingontheirroleintheprocedureshallsendorshallbecapableofreceivingandprocessingtherelevantprotocolelementsaslistedintherespectivetablesifnotexplicitlystatedasbeingoptional.Theprimitivesusedinproceduredescriptionsaredefinedonlyforthepurposeofdescribinglayer-to-layerinteractions.Theprimitivesaredefinedasanabstractlistofparameters,andtheirconcreterealizationmayvarybetweenimplementations.Noformaltestingofprimitivesisintended.Theprimitivedefinitionshavenonormativesignificance.SIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)189NWKlayerproceduresThisclausespecifiestheNWKlayerprocedures,messagesandIEsrequiredintheCAP.ThisprofiledoesnotpreventanyPTorFTtransmittingorreceivingandprocessinganyotherNWKlayermessageorIEnotspecifiedintheprofile.APTorFTreceivinganunsupportedNWKlayermessageorIEwhichitdoesnotrecognizeshallignoreit,asspecifiedinclause17ofEN300175-5[5].9.1Externalhandoverprocedures9.1.1HandovercandidateprocedureFP-1shallonlyindicatehandovercandidatestowhichthePPhasaccessusingitsactivesubscription.Furthermore,theindicatedcandidatesshallsupportExternalhandoverfromthecurrentFP.IfthecurrentFPsupportsencryption,thentheFPshallensurethattheindicatedcandidateFPssupportencryption.NOTE:TheaboveimpliesthatthePPdoesnotneedtoanalysetheSecondaryAccessRightsIdentities(SARIs)and/orTARIssupportedbyFP-2priortoattemptingexternalhandover.Likewise,thePPneednotanalysetheexternalhandovernorthecipheringsupportbitbroadcastedbyFP-2priortoattemptingexternalhandover.9.1.1.1HandovercandidateindicationTheprocedureshallbeperformedasdefinedinclause15.7.1.2ofEN300175-5[5].Thefollowingtexttogetherwiththeassociatedclausesdefinethemandatoryrequirementswithregardtothepresentdocument.TheFPshallprovidethe<>in{CC-SETUP},{CC-SETUP-ACK},{CC-CONNECT}or{CC-INFO}.Theindicatedhandovercandidatesarevaliduntilthereleaseofthecalloruntilthesuccessfulcompletionofanexternalhandover.Incaseofexternalhandover,FP-2shallsendthe<>i.e.withinaCC-INFOmessageaftersuccessfulcompletionoftheexternalhandoverprocedure.OnlyonevalueisrequestedtobestoredinthePP.ThePPshallbeabletoperformexternalhandoverbetweenFPswhichindicate2or3inthefieldofthe<>.NOTE:Successfulcompletionofanexternalhandovermeans,thatthehandoverhasbeenacceptedasdefinedinclause15.7.4.3ofEN300175-5[5].Table7:Codingof<>incallestablishmentCCmessagesInformationelementFieldwithintheinformationelementStandardvalueswithinthefield/IENormativeaction/comment<>0OtherfixedpartIDsnotavailableusingparameterretrievalprocedure1OtherfixedpartIDsavailableusingparameterretrievalprocedureAllAllSIST EN 300 824 V1.3.1:2003
ETSIETSIEN300824V1.3.1(2001-08)199.1.1.2HandovercandidateretrievalTheprocedureshallbeperformedasdefinedinclause15.7.1.3ofEN300175-5[5].Thefollowingtexttogetherwiththeassociatedclausesdefinethemandatoryrequirementswithregardtothepresentdocument.ThePPshallnotinvokethisprocedureifthe<>hasnotyetreceivedorifthe<>hasbeenreceivedwiththeOIDvaluesetto"0".IfthePPsendsa{MM-INFO-REQUEST}messagewithan<>IEindicating"externalhandoverparameters",theFPshallalsoincludeahandoverreferenceina<>IEunlessthehandoverreferenceisnotrequired.InthiscasetheFPshallinformthePPincludingintheresponsea<>IEwiththevalue"handoverreferencenotrequired".The<>shallalwaysbeincludedintothe{MM-INFO-ACCEPT}messageindicatingwhattypeofsynchronizationthesuggestedFixedPartshave.IfmorethanoneFixedpartisindicated,allofthemshallhaveatleastthetypeofsynchronization,requestedinthe<>.Table8:Valuesusedwithinthe{MM-INFO-REQUEST}messageInformationelementFieldwithintheinformationelementStandardvalueswithinthefield/IENormativeaction/comment<>1Onlyoneparameterperinformationelement8Externalhandoverparameters11MultiframeandPSCNsynchronizedexternalhandovercandidate12Externalhandovercandidate13Multiframesynchronizedexternalhandovercandidate14Nonsynchronizedexternalhandoverca
...