ETSI EN 300 824 V1.2.2 (1999-09)

Digital Enhanced Cordless Telecommunications (DECT); Cordless Terminal Mobility (CTM); CTM Access Profile (CAP)

REN/DECT-030139

Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Mobilnost brezvrvičnega terminala (CTM) – Profil dostopa CTM (CAP)

General Information

• Status: Published
• Publication Date: 06-Sep-1999
• Technical Committee: DECT 3 - Network aspects
• Current Stage: 12 - Completion
• Due Date: 30-Aug-1999
• Completion Date: 07-Sep-1999
• Ref Project: SIST EN 300 824 V1.2.2:2003 - Digital Enhanced Cordless Telecommunications (DECT); Cordless Terminal Mobility (CTM); CTM Access Profile (CAP)

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.2.2SIST EN 300 824 V1.2.2:2003en01-december-2003SIST EN 300 824 V1.2.2:2003SLOVENSKI
STANDARD
ETSIETSI EN 300 824 V1.2.2 (1999-09)2ReferenceREN/DECT-030139 (7mo00ipc.PDF)KeywordsCAP, CTM, DECT, synchronizationETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail] copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: [e-mail] NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)3ContentsIntellectual Property Rights.6Foreword.61Scope.72References.73Definitions, symbols and abbreviations.83.1Definitions.83.2Symbols.113.3Abbreviations.114Introduction.125Feature definitions.125.1Network (NWK) features.125.1.1Application features.136Service definitions.136.1DLC service definitions.136.2Medium Access Control (MAC) service definitions.137Interoperability requirements.137.1General.137.2NWK features.147.3DLC services.147.4MAC services.147.5Physical Layer (PHL) services.147.6Application features.147.7NWK feature to procedure mapping.157.8Service to procedure mapping.167.8.1DLC service to procedure mapping.167.8.2MAC service to procedure mapping.167.8.3Application feature to procedure mapping.167.9General requirements.177.9.1Coexistence of MM and CC procedures.178Procedure description.179NWK layer procedures.189.1External handover procedures.189.1.1Handover candidate procedure.189.1.1.1Handover candidate indication.189.1.1.2Handover candidate retrieval.199.1.1.2.1Exceptional cases.209.1.1.2.1.1Failure of the PP handover candidate retrieval attempt.209.1.2Target FP selection.209.1.3Handover reference procedure.219.1.3.1Handover reference indication.219.1.3.2Handover reference retrieval.219.1.3.2.1Exceptional cases.229.1.3.2.1.1Failure of the PP handover reference retrieval attempt.229.1.4External handover call set-up.239.1.4.1Associated procedures.239.1.4.1.1Transaction identifier handling.239.1.4.2Exceptional cases.239.1.4.2.1Abnormal link release on FP-1 leg.239.1.4.2.2Normal call release on FP-2 leg.239.1.4.2.3Abnormal link release on FP-2 leg.239.1.5Ciphering procedure.24SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)49.1.5.1Ciphering procedure PT initiated.249.1.5.2Ciphering procedure FT initiated.249.1.6U-plane handling.249.2Emergency call set-up.249.3Display.259.4Terminal capability indication.259.5Detach.269.6Enhanced location registration.269.6.1Exceptional case(s).279.6.1.1Failure of location registration procedure.279.7Message waiting indication.279.7.1MWIIndicate- activation.289.7.2MWIIndicate- deactivation.299.7.3Retrieval of the message.299.8On-air modification of user parameters.299.8.1Exceptional cases.309.8.1.1Collision with normal call procedure.3010DLC layer procedures.3111MAC layer procedures.3111.1General.3111.2Downlink broadcast.3111.3Non-continuous broadcast.3211.3.1Mt message.3211.3.1.1Extended system information.3211.3.1.2TARI message.3311.4RFP status.3311.4.1RFP status information.3411.5Extended fixed part capabilities.3411.6Prolonged preamble.3511.6.1Procedure for prolonged preamble diversity in RFP and prolonged preamble transmission in PP.3511.6.2Procedure for prolonged preamble diversity in PP and prolonged preamble transmission in RFP.3512Physical layer requirements.3512.1General.3512.2External handover.3512.3Prolonged Preamble.3513Requirements regarding the speech transmission.3613.1General.3613.2Reference to GAP.3614Management procedures.3614.1General.3614.2Location registration initiation.3614.3Assigned individual Temporary Portable User Identity (TPUI) management.3714.4Detach.3714.5External handover.3714.6Emergency call management.3814.7PMID management.3814.8Broadcast attributes management.3814.9Message waiting indication.3915Application procedures.3915.1General.3915.2Subscription control.39SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)5Annex A (normative):System parameters.40A.1NWK layer constants.40A.2PHL constants.40Annex B (informative):PP locking procedure for on air subscription.41Annex C (informative):Void.42Annex D (informative):Tones, progress indicator and U-plane connection.43Annex E (informative):PARI and SARI use for CTM roaming.44Annex F (normative):Class 2 synchronization requirements.46Annex G (normative):Synchronization requirements for fixed parts.47Annex H (informative):Coding example for message waiting indication.48Bibliography.49History.50SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)6Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server(http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Project Digital Enhanced CordlessTelecommunications (DECT).The present document is based on EN 300 175, parts 1 to 8 [1] to [8] and EN 300 444 [12].National transposition datesDate of adoption of this EN:27 August 1999Date of latest announcement of this EN (doa):30 November 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 May 2000Date of withdrawal of any conflicting National Standard (dow):31 May 2000SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)71ScopeThe present document specifies that set of technical requirements for Digital Enhanced Cordless Telecommunications(DECT) Fixed Part (FP) and DECT Portable Part (PP) necessary for the support of the Cordless Terminal Mobility(CTM) Access Profile (CAP).The objective of the present document is to ensure the air interface interoperability of DECT CAP PPs and DECT CAPFPs if applied.The CTM service allows users of cordless terminals to be mobile within and between networks. Where radio coverage isprovided and the cordless terminal has appropriate access rights the user shall be able to make calls from, and to receivecalls at, any location within the fixed public and/or private networks, and may move without interruption of a call inprogress.The present document covers the DECT access requirements for CTM phase 2 as defined in the CTM phase 2 servicedescription, EN 301 273 [14].The main objectives of the CAP are:-maintain compatibility with the DECT Generic Access Profile (GAP), identifying only components notmandatory in the GAP to be added to obtain capabilities needed in the CTM context;-maintain compatibility with EN 300 175 parts 1 to 8 [1] to [8], for procedures not defined in the GAP.The CTM access profile is seen as an extension of the GAP mandatory base covering the requirements for CTMphase 2.CAP supports telephony teleservice and provides 32 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)speech bearer service.CTM supplementary services with no impact on the air interface are not considered in the CAP.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, the latest version applies.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 1: Overview".[2]EN 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 2: Physical layer (PHL)".[3]EN 300 175-3: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 3: Medium Access Control (MAC) layer".[4]EN 300 175-4: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 4: Data Link Control (DLC) layer".[5]EN 300 175-5: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 5: Network (NWK) layer".SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)8[6]EN 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 6: Identities and addressing".[7]EN 300 175-7: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 7: Security features".[8]EN 300 175-8: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);Part 8: Speech coding and transmission".[9]ETS 300 176: "Digital Enhanced Cordless Telecommunications (DECT); Approval testspecification".[10]TBR 6: "Digital Enhanced Cordless Telecommunications (DECT); General terminal attachmentrequirements".[11]TBR 10 (1997): "Digital Enhanced Cordless Telecommunications (DECT); General terminalattachment requirements; Telephony applications".[12]EN 300 444: "Digital European Cordless Telecommunications (DECT); Generic Access Profile(GAP)".[13]TBR 22: "Radio Equipment and Systems (RES); Attachment requirements for terminal equipmentfor Digital Enhanced Cordless Telecommunications (DECT) Generic Access Profile (GAP)applications".[14]EN 301 273: "Cordless Terminal Mobility (CTM); Phase 2 Service description".[15]EN 300 745-1: "Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI)supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1:Protocol specification".[16]ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 7: Implementation Conformance Statements".[17]EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for thesupport of supplementary services; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".3Definitions, symbols and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply:attach: process whereby a PP within the coverage area of a FP to which it has access rights, notifies this FP that it isoperative. The reverse process is detach, which reports the PP as inoperative.NOTE 1:An operative PP is assumed to be ready to receive calls.authentication: process whereby a CTM subscriber is positively verified to be a legitimate user of the CTM service.NOTE 2:Authentication is generally performed at call set-up, but may also be done at any other time (e.g. duringa call).bearer service: type of telecommunication service that provides a defined capability for the transmission of signalsbetween user-network interfaces.NOTE 3:The DECT user-network interface corresponds to the top of the network layer (layer 3).SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)9C-plane: control plane of the DECT protocol stacks, which contains all of the internal DECT protocol control, but mayalso include some external user information.NOTE 4:The C-plane stack always contains protocol entities up to and including the network layer.call: all of the Network (NWK) layer processes involved in one network layer peer-to-peer association.NOTE 5:Call may sometimes be used to refer to processes of all layers, since lower layer processes are implicitlyrequired.DECT network: network that uses the DECT air interface to interconnect a local network to one or more portableapplications. The logical boundaries of the DECT network are defined to be at the top of the DECT network layer.NOTE 6:A DECT network is a logical grouping that contains one or more fixed radio terminations plus theirassociated portable radio termination. The boundaries of the DECT network are not physicalboundaries.external handover: process of switching a call in progress from one fixed part to another fixed part.Fixed Part (DECT Fixed Part) (FP): physical grouping that contains all of the elements in the DECT network betweenthe local network and the DECT air interface.NOTE 7:A DECT FP contains the logical elements of at least one FT, plus additional implementation specificelements.Fixed radio Termination (FT): logical group of functions that contains all of the DECT processes and procedures onthe fixed side of the DECT air interface.NOTE 8:A FT only includes elements that are defined in the DECT Common Interface (CI) standard. Thisincludes radio transmission elements together with a selection of layer 2 and layer 3 elements.geographically unique identity: term relates to FP identities, Primary Access Rights Identities (PARIs) and RadioFixed Part Identities (RFPIs). It indicates that two systems with the same PARI, or respectively two Radio Fixed Parts(RFPs) with the same RFPI, can not be reached or listened to at the same geographical position.NOTE 9:For PARI and RFPI see abbreviations.global network: telecommunication network capable of offering a long distance telecommunication service.NOTE 10:The term does not include legal or regulatory aspects, nor does it indicate if the network is a public or aprivate network.globally unique identity: identity is unique within DECT (without geographical or other restrictions).handover: process of switching a call in progress from one physical channel to another physical channel.NOTE 11:There are two physical forms of handover, intra-cell handover and inter-cell handover.incoming call: call received at a PP.inter-cell handover: switching of a call in progress from one cell to another cell.internal handover: handover processes that are completely internal to one FT. Internal handover reconnects the call atthe lower layers, while maintaining the call at the NWK layer.NOTE 12:The lower layer reconnection can either be at the Data Link Control (DLC) layer (connection handover)or at the MAC layer (bearer handover).interoperability: capability of FPs and PPs, that enable a PP to obtain access to teleservices in more than one locationarea and/or from more than one operator (more than one service provider).interoperator roaming: roaming between FP coverage areas of different operators (different service providers).SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)10Interworking Unit (IWU): unit that is used to interconnect sub networks.NOTE 13:The IWU will contain the interworking functions necessary to support the required sub networkinterworking.intra-cell handover: switching of a call in progress from one physical channel of one cell to another physical channel ofthe same cell.intraoperator roaming: roaming between different FP coverage areas of the same operator (same service provider).Local Network (LNW): telecommunication network capable of offering local telecommunication services.NOTE 14:The term does not include legal or regulatory aspects, nor does it indicate if the network is a publicnetwork or a private network.locally unique identity: unique identity within one FP or location area, depending on application.location area: domain in which a PP may receive (and/or make) calls as a result of a single location registration.location registration: process whereby the position of a DECT PT is determined to the level of one location area, andthis position is updated in one or more databases.NOTE 15:These databases are not included within a DECT FT.MAC Connection (CONNECTION): association between one source MAC Multi-Bearer Control (MBC) entity andone destination Medium Access Control (MAC) Multi-Bearer Control (MBC) entity. This provides a set of relatedMAC services (a set of logical channels), and it can involve one or more underlying MAC bearers.outgoing call: call originating from a PP.Portable Application (PA): logical grouping that contains all the elements that lie beyond the DECT network boundaryon the portable side.NOTE 16:The functions contained in the PA may be physically distributed, but any such distribution is invisible tothe DECT network.Portable Part (DECT Portable Part) (PP): physical grouping that contains all elements between the user and theDECT air interface. PP is a generic term that may describe one or several physical pieces.NOTE 17:A DECT PP is logically divided into one PT plus one or more PAs.Portable radio Termination (PT): logical group of functions that contains all of the DECT processes and procedureson the portable side of the DECT air interface.NOTE 18:A PT only includes elements that are defined in the DECT CI standard. This includes radio transmissionelements (layer 1) together with a selection of layer 2 and layer 3 elements.Radio Fixed Part (RFP): one physical sub-group of a FP that contains all the radio end points (one or more) that areconnected to a single system of antennas.roaming: movement of a PP from one FP coverage area to another FP coverage area, where the capabilities of the FPsenable the PP to make or receive calls in both areas.NOTE 19:Roaming requires the relevant FPs and PP to be interoperable.subscription registration: infrequent process whereby a subscriber obtains access rights to one or more FPs.NOTE 20:Subscription registration is usually required before a user can make or receive calls.supplementary service: service that modifies or supplements a basic telecommunications service.teleservice: type of telecommunications service that provides the complete capability, including terminal equipmentfunctions, for communication between users, according to protocols that are established by agreement.SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)113.2SymbolsThe symbols defined in this subclause are applied for procedures, features, services in the present document if notexplicitly otherwise stated. The interpretation of status columns in all tables is as follows:Mfor mandatory to support (provision mandatory, process mandatory)Ofor optional to support (provision optional, process mandatory)Ifor out-of-scope (provision optional, process optional) not subject for testingCfor conditional to support (process mandatory)N/Afor not-applicable (in the given context the specification makes it impossible to use this capability)Provision mandatory, process mandatory means that the indicated feature, service or procedure shall be implemented asdescribed in the present document, and may be subject to testing.Provision optional, process mandatory means that the indicated feature, service or procedure may be implemented, andif implemented, the feature, service or procedure shall be implemented as described in the present document, and maybe subject to testing.NOTE:The used notation is based on the notation proposed in ISO/IEC 9646-7 [16].3.3AbbreviationsFor the purposes of the present document, the following abbreviations apply:ADPCMAdaptive Differential Pulse Code ModulationARCAccess Rights ClassARDAccess Rights DetailsARIAccess Rights IdentityBBusiness (environment)CAPCTM Access ProfileCCCall ControlCICommon InterfaceCLIPCalling Line Identification PresentationCTMCordless Terminal MobilityDECTDigital Enhanced Cordless TelecommunicationsDLCData Link ControlEMCEquipment Manufacturer CodeFPFixed PartFTFixed radio TerminationGAPGeneric Access ProtocolIEInformation ElementIPEIInternational Portable Equipment IdentityIPUIInternational Portable User IdentityISDNIntegrated Services Digital NetworkIWUInterworking UnitLALocation AreaLAILocation Area IdentificationLALLocation Area LevelLCELink Control EntityLNWLocal NetworkMACMedium Access ControlMBCMulti-Bearer ControlMMMobility Management, a NWK layer functional groupingMWIMessage Waiting IndicationNWKNetwork, Layer 3 of the DECT protocol stackPPublic (environment)PAPortable ApplicationPARIPrimary Access Rights IdentityPARKPortable Access Rights KeyPHLPhysical LayerSIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)12PLIPark Length IndicatorPMIDPortable part MAC IdentityPPPortable PartPSNPortable equipment Serial NumberPTPortable radio TerminationPUNPortable User NumberPUTPortable User TypeRESA Response calculated by a PPRFPRadio Fixed PartRFPIRadio Fixed Part IdentityRResidential (environment)SAPService Access PointSARISecondary Access Rights IdentityTARITertiary Access Rights IdentityTPUITemporary Portable User Identity4IntroductionThis profile is an extension of EN 300 444 [12] covering the requirements for CTM phase 2.In the following clauses only differences with respect to EN 300 444 [12] are explicitly mentioned.5Feature definitionsFor the purposes of the present document, the feature definitions in the following subclauses apply.The reference given in parentheses after the name of a feature is the item reference used in the tables of the presentdocument.5.1Network (NWK) featuresThe following differences from the GAP are applicable.DECT external handover (CAP-N.1): External handover is the process of switching a call in progress from one FixedPart (FP-1) to another Fixed Part (FP-2). This means the handover occurs between two independent systems, where eachsystem has its own lower layers of protocol and has an independent set of network layer Service Access Points (SAPs).To make external handover possible, a common management entity above the two fixed terminations is necessary.Emergency call (CAP-N.2): This service feature enables a user to make an emergency call even without a validsubscription, i.e. a fast and easy means of giving information about an emergency situation to the appropriate emergencyorganization (e.g. fire service, police and ambulance).Display management (CAP-N.3): This feature enables a user to receive short alphanumeric indications displayed onthe screen terminal. These indications could be associated with supplementary or value added services.Message waiting indication (CAP-N.4): This feature enables a user to receive an indication of the status of a messageserver (e.g. a voice mailbox) to which the user has access to.Detach (CAP-N.5): This feature enables a PT to report to the FT that the PT is not ready to receive calls.Enhanced location registration (CAP-N.6): This feature enables automatic location registration of PT at expectedintervals of time.On-air modification of user parameters (CAP-N.7): This feature enables the FT to modify the active subscriptiondata of the PT.SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)135.1.1Application featuresSee EN 300 444 [12].6Service definitionsFor the purposes of the present document, the following service definitions apply.6.1DLC service definitionsSee EN 300 444 [12].6.2Medium Access Control (MAC) service definitionsThe following differences from the GAP are applicable.Tertiary Access Rights Identity (TARI) support (CAP-M.1): The ability to support in addition to the primary AccessRights Identity (ARI) and secondary ARIs tertiary ARIs that the FT does not broadcast and are only available to PT as aYes/No answer upon a request including the wanted ARI. These may be used to reflect an inter-operators agreementallowing a portable to access more than one operator or services through FT.RFP status (CAP-M.2): A service which indicates to the PP the status (busy or clear) of the RFP or the system (FP).Extended fixed part capabilities (CAP-M.3): A service which indicates to the PP the extended capabilities of the FP.Prolonged preamble diversity in RFP (CAP-M.4): The ability of the RFP to support antenna diversity based on thereception of a prolonged preamble.Prolonged preamble diversity in PP (CAP-M.5): The ability of the PP to support antenna diversity based on thereception of a prolonged preamble.Prolonged preamble transmission of the RFP (CAP-M.6): The ability of the RFP to transmit prolonged preamble ifthe PP supports prolonged preamble diversity.Prolonged preamble transmission of the PP (CAP-M.7): The ability of the PP to transmit prolonged preamble if theRFP supports prolonged preamble diversity.7Interoperability requirements7.1GeneralThe tables listed in this subclause define all the protocol elements i.e. features, services, and procedures which aremandatory, optional, and conditional under the provision of another protocol element, or out of the scope of the presentdocument, or in some context not-applicable according to the definition of the status column as defined in subclause 3.3for the CAP FP and PP. All optional elements shall be process mandatory according to the procedures described in thepresent document.Protocol elements defined as mandatory, optional or conditional in this subclause shall further be defined in clauses 8, 9,10, 11, 12, 13, 14 and 15 in detail either explicitly and/or as references to the DECT base standard, EN 300 175parts 2 to 8, [2] to [8] and ETS 300 176 [9].The requirements of TBR 6 [10], TBR 10 [11] and TBR 22 [13] shall be met by all equipment conforming to the presentdocument.SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)147.2NWK featuresTable 1: NWK features statusFeature supportedStatusItem no.Name of featureCAPRef.GAPRef.PTFTRBPN.11Location registration4.1MOMMN.20Terminate access rights FT initiated4.1MOOMN.30Calling Line Identification Presentation (CLIP)4.1MOOMCAP-N.1DECT External handover5.1MOOMCAP-N.2Emergency call5.1MOOMCAP-N.3Display Management5.1MOOMCAP-N.4Message Waiting Indication5.1MOOMCAP-N.5Detach5.1MOOMCAP-N.6Periodic location registration5.1MOOMCAP-N.7On-air modification of user parameters5.1MOOO7.3DLC servicesSee subclause 6.3 of EN 300 444 [12].7.4MAC servicesTable 2: MAC services statusService supportedStatusItem no.Name of serviceCAP Ref.GAP Ref.PTFTRBPCAP-M.1TARI support6.2OOOOCAP-M.2RFP status6.2MOMMCAP-M.3Extended fixed part capabilities6.2MOOMCAP-M.4Prolonged preamble diversity in RFP6.2N/AOOOCAP-M.5Prolonged preamble diversity in PP6.2ON/AN/AN/ACAP-M.6Prolonged preamble transmission in RFP6.2N/AOOOCAP-M.7Prolonged preamble transmission in PP6.2MN/AN/AN/A7.5Physical Layer (PHL) servicesSee subclause 6.5 of EN 300 444 [12].7.6Application featuresSee subclause 6.6 of EN 300 444 [12].SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)157.7NWK feature to procedure mappingTable 3: NWK feature to procedure mappingFeature/Procedure mappingStatusFeatureProcedureCAPRef.GAPRef.PTFTRBPN.11 Location registration4.1MOMMN.20 Terminate access rights FTinitiated4.1MOOMFT authentication8.23MMMMN.30, Calling Line IdentificationPresentation (CLIP)4.1MOOMIncoming call request8.12MMMMCAP-N.1, DECT Externalhandover5.1MOOMHandover candidate indication9.1.1.1MMMMHandover candidate retrieval9.1.1.2MOOOTarget FP selection9.1.2MN/AN/AN/AHandover reference indication9.1.3.1MC1C1C1Handover reference retrieval9.1.3.2MC2C2C2External handover call set-up9.1.4MMMMCiphering procedure PT initiated9.1.5.1OC3C3C3Ciphering procedure FT initiated9.1.5.2MC4C4MU-plane handling9.1.6MOMMCAP-N.2, Emergency call5.1MOOMEmergency call set-up9.2MMMMCAP-N.3, Display Management5.1MOOMDisplay9.3MMMMTerminal capability indication9.4MMMMCAP-N.4, Message WaitingIndication5.1MOOMMessage waiting indication9.7MMMMCAP-N.5, Detach5.1MOOMDetach9.5MMMMCAP-N.6, Periodic locationregistration5.1MOOMEnhanced location registration9.6MMMMCAP-N.7, On-air modification ofuser parameters5.1MOOOOn-air modification of userparameters9.8MMMMFT authentication8.23MMMMC1IF procedure 9.1.3.2 supported THEN O ELSE M.C2IF procedure 9.1.3.1 supported THEN O ELSE M.C3IF feature N.27 of EN 300 444 [12] THEN M ELSE O.C4IF feature N.17 of EN 300 444 [12] THEN M ELSE O.SIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)167.8Service to procedure mapping7.8.1DLC service to procedure mappingSee subclause 6.8.1 of EN 300 444 [12].7.8.2MAC service to procedure mappingTable 4: MAC service to procedure mappingService/Procedure mappingStatusServiceProcedureCAPRef.GAPRef.PTFTRBPCAP-M.1 TARI support6.2OOOO Non-continuous broadcast11.3MMMMCAP-M.2 RFP status6.2MOMMRFP status11.4MMMMCAP-M.3 Extended fixed partcapabilities6.2MOOMExtended fixed part capabilities11.5MMMMCAP-M.4. Prolonged preamblediversity in RFP6.2N/AOOOProlonged preamble diversity in RFP andprolonged preamble transmission in PP11.6.1N/AMMMCAP-M.5. Prolonged preamblediversity in PP6.2ON/AN/AN/AProlonged preamble diversity in PP andprolonged preamble transmission in RFP11.6.2MN/AN/AN/ACAP-M.6. Prolonged preambletransmission in RFP6.2N/AOOOProlonged preamble diversity in PP andprolonged preamble transmission in RFP11.6.2N/AMMMCAP-M.7. Prolonged preambletransmission in PP6.2MN/AN/AN/AProlonged preamble diversity in RFP andprolonged preamble transmission in PP11.6.1MN/AN/AN/A7.8.3Application feature to procedure mappingTable 5: Application feature to procedure mappingFeature/Procedure mappingStatusFeatureProcedureCAPRef.GAPRef.PTFTRBPA.2 Multiple subscriptionregistration4.2MN/AN/AN/ASubscription control15.214.1MN/AN/AN/ASIST EN 300 824 V1.2.2:2003

ETSIETSI EN 300 824 V1.2.2 (1999-09)177.9General requirementsSee subclauses 6.9.1 to 6.9.7 of EN 300 444 [12].7.9.1Coexistence of MM and CC proceduresIn addition to subclause 6.9.6 of EN 300 444 [12], the following definition regarding features (CAP-N.5) and(CAP-N.7) shall apply.Table 6FeatureProcedureMandatory support in CC state(CAP-N.5)DetachAll states(CAP-N.7)On-air modification of user parametersT (F) -008Procedure descriptionClauses 9 to 15 define the process mandatory procedures which are in the scope of the CAP. Each procedure (ifappropriate) is divided into three parts:a) normal (i.e. successful case). This part defines the functions and respective protocol element values in normaloperation;b) associated procedure(s). This is an integral part of the actual procedure (if defined in the present document) i.e. ifa procedure is being declared to be supported, the respective entity shall also support the associated procedures,e.g. timer management, in the subclause following the description of the normal case;c) exceptional case(s). This is an integral part of the actual procedure (if defined in the present document) i.e. if aprocedure is being declared to be supported, the respective entity shall
...