ETSI ETS 300 824 ed.1 (1997-10)

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:ETS 300 824 Edition 13SIST ETS 300 824:1999en01-PDUHF-19993SIST ETS 300 824:1999SLOVENSKI
STANDARD
EUROPEANETS 300 824TELECOMMUNICATIONOctober 1997STANDARDSource: DECTReference: DE/DECT-030080ICS:33.020Key words:CAP, CTM, DECTDigital Enhanced Cordless Telecommunications (DECT);Cordless Terminal Mobility (CTM);CTM Access Profile (CAP)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1997. All rights reserved.SIST ETS 300 824:1999

Page 2ETS 300 824: October 1997Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 824:1999

Page 3ETS 300 824: October 1997ContentsForeword.71Scope.92Normative references.93Definitions, abbreviations and symbols.103.1Definitions.103.2Abbreviations.133.3Symbols.144Introduction.155Feature definitions.155.1Network (NWK) features.155.1.1Application features.156Service definitions.156.1DLC service definitions.156.2Medium Access Control (MAC) service definitions.167Interoperability requirements.167.1General.167.2NWK features.167.3DLC services.167.4MAC services.177.5Physical Layer (PHL) services.177.6Application features.177.7NWK feature to procedure mapping.187.8Service to procedure mapping.197.8.1DLC service to procedure mapping.197.8.2MAC service to procedure mapping.197.8.3Application feature to procedure mapping.197.9General requirements.197.9.1Coexistence of MM and CC procedures.198Procedure description.209NWK layer procedures.209.1External handover procedures.209.1.1Handover candidate procedure.209.1.1.1Handover candidate indication.209.1.1.2Handover candidate retrieval.219.1.1.2.1Exceptional cases.219.1.1.2.1.1Failure of the PP handover candidateretrieval attempt.219.1.2Target FP selection.219.1.3Handover reference procedure.229.1.3.1Handover reference indication.229.1.3.2Handover reference retrieval.229.1.3.2.1Exceptional cases.229.1.3.2.1.1Failure of the PP handover referenceretrieval attempt.229.1.4External handover call setup.239.1.4.1Associated procedures.239.1.4.1.1Transaction identifier handling.23SIST ETS 300 824:1999

Page 4ETS 300 824: October 19979.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.249.1.5Ciphering procedure.249.1.5.1Ciphering procedure PT initiated.249.1.5.2Ciphering procedure FT initiated.249.1.6U-plane handling.249.2Emergency call setup.259.3Display.259.4Terminal capability indication.269.5Detach.269.6Enhanced location registration.279.6.1Exceptional case(s).279.6.1.1Failure of location registration procedure.279.7Message waiting indication.289.7.1MWIIndicate- activation.299.7.2MWIIndicate- deactivation.309.7.3Retrieval of the message.309.8On-air modification of user parameters.309.8.1Exceptional cases.319.8.1.1Collision with normal call procedure.3110DLC layer procedures.3111MAC layer procedures.3211.1General.3211.2Downlink broadcast.3211.3Non-continuous broadcast.3311.3.1Mt message.3311.3.1.1Extended system information.3311.3.1.2TARI message.3411.4RFP status.3511.4.1RFP status information.3511.5Extended fixed part capabilities.3612Physical layer requirements.3612.1General.3612.2External handover.3613Requirements regarding the speech transmission.3613.1General.3613.2Reference to GAP.3614Management procedures.3714.1General.3714.2Location registration initiation.3714.3Assigned individual Temporary Portable User Identity (TPUI) management.3714.4Detach.3814.5External handover.3814.6Emergency call management.3814.7PMID management.3914.8Broadcast attributes management.3914.9Message waiting indication.3915Application procedures.4015.1General.4015.2Subscription control.40Annex A (normative):System parameters.41A.1NWK layer constants.41SIST ETS 300 824:1999

Page 5ETS 300 824: October 1997A.2PHL constants.41Annex B (informative):PP locking procedure for on air subscription.42Annex C (normative):ETS 300 175 changes.43C.1General.43C.2Network layer.43C.2.1New codings in << Duration>> IE.43C.2.2<> IE coding.43C.2.3Modification of access rights.43C.3Identities and addressing.44C.3.1New lock timer user limit.44Annex D (informative):Tones, progress indicator and U-plane connection.45Annex E (informative):PARI and SARI use for CTM roaming.46Annex F (normative):Class 2 synchronization requirements.48Annex G (normative):Synchronization requirements for fixed parts.49Annex H (informative):Coding example for message waiting indication.50History.51SIST ETS 300 824:1999

Page 6ETS 300 824: October 1997Blank pageSIST ETS 300 824:1999

Page 7ETS 300 824: October 1997ForewordThis European Telecommunication Standard (ETS) has been produced by the Digital Enhanced CordlessTelecommunications (DECT) Project of the European Telecommunications Standards Institute (ETSI).This ETS is based on ETS 300 175, parts 1 to 8 [1] to [8] and ETS 300 444 [12].Transposition datesDate of adoption:3 October 1997Date of latest announcement of this ETS (doa):31 January 1998Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 July 1998Date of withdrawal of any conflicting National Standard (dow):31 July 1998SIST ETS 300 824:1999

Page 8ETS 300 824: October 1997Blank pageSIST ETS 300 824:1999

Page 9ETS 300 824: October 19971ScopeThis European Telecommunication Standard (ETS) specifies that set of technical requirements for DigitalEnhanced 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 ETS 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. Whereradio coverage is provided and the cordless terminal has appropriate access rights the user shall be ableto make calls from, and to receive calls at, any location within the fixed public and/or private networks, andmay move without interruption of a call in progress.This ETS covers the DECT access requirements for CTM phase 2 as defined in the CTM phase 2 servicedescription, DE/NA-010061 [14].The main objectives of the CAP are:-maintain compatibility with the DECT Generic Access Profile (GAP), identifying only componentsnot mandatory in the GAP to be added to obtain capabilities needed in the CTM context;-maintain compatibility with ETS 300 175 [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 requirementsfor CTM phase 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.2Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 1: Overview".[2]ETS 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 2: Physical layer (PHL)".[3]ETS 300 175-3: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 3: Medium Access Control (MAC) layer".[4]ETS 300 175-4: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 4: Data Link Control (DLC) layer".[5]ETS 300 175-5: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 5: Network (NWK) layer".[6]ETS 300 175-6: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 6: Identities and addressing".[7]ETS 300 175-7: "Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI); Part 7: Security features".SIST ETS 300 824:1999

Page 10ETS 300 824: October 1997[8]ETS 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 test specification".[10]TBR 6: "Digital Enhanced Cordless Telecommunications (DECT); Generalterminal attachment requirements".[11]TBR 10 (1997): "Digital Enhanced Cordless Telecommunications (DECT);General terminal attachment requirements; Telephony applications".[12]ETS 300 444 (1995): "Digital European Cordless Telecommunications (DECT);Generic Access Profile (GAP)".[13]TBR 22: "Attachment requirements for terminal equipment for Digital EnhancedCordless Telecommunications (DECT) Generic Access Profile (GAP)applications".[14]DEN/NA-010061: "Cordless Terminal Mobility (CTM); Phase 2; ServiceDescription".[15]ETS 300 650: "Integrated Services Digital Network (ISDN); Message WaitingIndication (MWI) supplementary service; Service description".[16]ETS 300 745-1: "Integrated Services Digital Network (ISDN); Message WaitingIndication (MWI) supplementary service; Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Part 1: Protocol specification".[17]ISO/IEC 9646-7 (1995): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 7:Implementation Conformance Statements".[18]ETS 300 196-1: "Integrated Services Digital Network (ISDN); Generic functionalprotocol for the support of supplementary services; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 1: Protocol specification".3Definitions, abbreviations and symbols3.1DefinitionsFor the purposes of this ETS, the following definitions apply:attach: The process whereby a PP within the coverage area of a FP to which it has access rights, notifiesthis FP that it is operative. 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: The process whereby a CTM subscriber is positively verified to be a legitimate user of theCTM service.NOTE 2:Authentication is generally performed at call set-up, but may also be done at any othertime (e.g. during a call).bearer service: A type of telecommunication service that provides a defined capability for thetransmission of signals between user-network interfaces.NOTE 3:The DECT user-network interface corresponds to the top of the network layer (layer 3).SIST ETS 300 824:1999

Page 11ETS 300 824: October 1997C-plane: The control plane of the DECT protocol stacks, which contains all of the internal DECT protocolcontrol, but may also include some external user information.NOTE 4:The C-plane stack always contains protocol entities up to and including the networklayer.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 layerprocesses are implicitly required.DECT network: A network that uses the DECT air interface to interconnect a local network to one ormore portable applications. The logical boundaries of the DECT network are defined to be at the top of theDECT network layer.NOTE 6:A DECT network is a logical grouping that contains one or more fixed radioterminations plus their associated portable radio termination. The boundaries of theDECT network are not physical boundaries.external handover: The process of switching a call in progress from one fixed part to another fixed part.Fixed Part (DECT Fixed Part) (FP): A physical grouping that contains all of the elements in the DECTnetwork between the local network and the DECT air interface.NOTE 7:A DECT FP contains the logical elements of at least one FT, plus additionalimplementation specific elements.Fixed radio Termination (FT): A logical group of functions that contains all of the DECT processes andprocedures on the fixed side of the DECT air interface.NOTE 8:A FT only includes elements that are defined in the DECT Common Interface (CI)standard. This includes radio transmission elements together with a selection of layer2 and layer 3 elements.geographically unique identity: This term relates to FP identities, Primary Access Rights Identities(PARIs) and Radio Fixed Part Identities (RFPIs). It indicates that two systems with the same PARI, orrespectively two Radio Fixed Parts (RFPs) with the same RFPI, can not be reached or listened to at thesame geographical position.NOTE 9:For PARI and RFPI see abbreviations.global network: A telecommunication network capable of offering a long distance telecommunicationservice.NOTE 10:The term does not include legal or regulatory aspects, nor does it indicate if thenetwork is a public or a private network.globally unique identity: The identity is unique within DECT (without geographical or other restrictions).handover: The process of switching a call in progress from one physical channel to another physicalchannel.NOTE 11:There are two physical forms of handover, intra-cell handover and inter-cell handover.incoming call: A call received at a PP.inter-cell handover: The switching of a call in progress from one cell to another cell.SIST ETS 300 824:1999

Page 12ETS 300 824: October 1997internal handover: Handover processes that are completely internal to one FT. Internal handoverreconnects the call at the 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: The capability of FPs and PPs, that enable a PP to obtain access to teleservices in morethan one location area and/or from more than one operator (more than one service provider).interoperator roaming: Roaming between FP coverage areas of different operators (different serviceproviders).Interworking Unit (IWU): A unit that is used to interconnect sub networks.NOTE 13:The IWU will contain the interworking functions necessary to support the required subnetwork interworking.intra-cell handover: The switching of a call in progress from one physical channel of one cell to anotherphysical channel of the same cell.intraoperator roaming: Roaming between different FP coverage areas of the same operator (sameservice provider).Local Network (LNW): A telecommunication network capable of offering local telecommunicationservices.NOTE 14:The term does not include legal or regulatory aspects, nor does it indicate if thenetwork is a public network or a private network.locally unique identity: A unique identity within one FP or location area, depending on application.location area: The domain in which a PP may receive (and/or make) calls as a result of a single locationregistration.location registration: The process whereby the position of a DECT PT is determined to the level of onelocation area, and this position is updated in one or more databases.NOTE 15:These databases are not included within a DECT FT.MAC Connection (CONNECTION): An association between one source MAC Multi-Bearer Control(MBC) entity and one destination Medium Access Control (MAC) Multi-Bearer Control (MBC) entity. Thisprovides a set of related MAC services (a set of logical channels), and it can involve one or moreunderlying MAC bearers.outgoing call: A call originating from a PP.Portable Application (PA): A logical grouping that contains all the elements that lie beyond the DECTnetwork boundary on the portable side.NOTE 16:The functions contained in the PA may be physically distributed, but any suchdistribution is invisible to the DECT network.Portable Part (DECT Portable Part) (PP): A physical grouping that contains all elements between theuser and the DECT 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.SIST ETS 300 824:1999

Page 13ETS 300 824: October 1997Portable radio Termination (PT): A logical group of functions that contains all of the DECT processesand procedures on the portable side of the DECT air interface.NOTE 18:A PT only includes elements that are defined in the DECT CI standard. This includesradio transmission elements (layer 1) together with a selection of layer 2 and layer 3elements.Radio Fixed Part (RFP): One physical sub-group of a FP that contains all the radio end points (one ormore) that are connected to a single system of antennas.roaming: The movement of a PP from one FP coverage area to another FP coverage area, where thecapabilities of the FPs enable the PP to make or receive calls in both areas.NOTE 19:Roaming requires the relevant FPs and PP to be interoperable.subscription registration: The infrequent process whereby a subscriber obtains access rights to one ormore FPs.NOTE 20:Subscription registration is usually required before a user can make or receive calls.supplementary service: A service that modifies or supplements a basic telecommunications service.teleservice: A type of telecommunications service that provides the complete capability, includingterminal equipment functions, for communication between users, according to protocols that areestablished by agreement.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ACAuthentication CodeADPCMAdaptive Differential Pulse Code ModulationARCAccess Rights ClassARDAccess Rights DetailsARIAccess Rights IdentityBBusiness environmentBCDBinary Coded DecimalCAPCTM Access ProfileCCCall ControlCICommon InterfaceCLIPCalling Line Identification PresentationCTMCordless Terminal MobilityDDECT reference pointDECTDigital Enhanced Cordless TelecommunicationsDLCData Link ControlDSAADECT Standard Authentication AlgorithmDSCADECT Standard Cipher AlgorithmDTMFDual Tone Multi-FrequencyEMCEquipment Manufacturer CodeFLENFrame LengthFPFixed PartFTFixed radio TerminationGAPGeneric Access ProtocolIEInformation ElementIPEIInternational Portable Equipment IdentityIPUIInternational Portable User IdentityISDNIntegrated Services Digital NetworkIWUInterworking UnitKS'FP authentication Session KeyKSPP authentication Session KeyLALocation AreaLAILocation Area IdentificationLALLocation Area LevelSIST ETS 300 824:1999

Page 14ETS 300 824: October 1997LCELink Control EntityLNWLocal NetworkMACMedium Access ControlMBCMulti-Bearer ControlMMMobility Management, a NWK layer functional groupingMWIMessage Waiting IndicationNWKNetwork, Layer 3 of the DECT protocol stackPPublic (environment)PAPortable ApplicationPAPPublic Access ProfilePARIPrimary Access Rights IdentityPARKPortable Access Rights KeyPHLPhysical LayerPLIPark Length IndicatorPMIDPortable part MAC IdentityPPPortable PartPSNPortable equipment Serial NumberPTPortable radio TerminationPUNPortable User NumberPUTPortable User TypeRResidential environmentRESA Response calculated by a PPRFPRadio Fixed PartRFPIRadio Fixed Part IdentityRSA value used to establish authentication session keysSAPService Access PointSAPIService Access Point IdentifierSARISecondary Access Rights IdentitySSSupplementary ServicesTARITertiary Access Rights IdentityTITransaction IdentifierTPUITemporary Portable User IdentityUAKUser Authentication KeyUPIUser Personal Identification3.3SymbolsThe symbols defined in this subclause are applied for procedures, features, services in this ETS 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 testing;Cfor 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 beimplemented as described in this ETS, and may be subject to testing.Provision optional, process mandatory means that the indicated feature, service or procedure may beimplemented, and if implemented, the feature, service or procedure shall be implemented as described inthis ETS, and may be subject to testing.NOTE:The used notation is based on the notation proposed in ISO/IEC 9646-7 [17].SIST ETS 300 824:1999

Page 15ETS 300 824: October 19974IntroductionThis profile is an extension of ETS 300 444 [12] covering the requirements for CTM phase 2.In the following clauses only differences with respect to ETS 300 444 [12] are explicitly mentioned.5Feature definitionsFor the purposes of this ETS, 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 ofthis ETS.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 progressfrom one Fixed Part (FP-1) to another Fixed Part (FP-2). This means the handover occurs between twoindependent systems, where each system has its own lower layers of protocol and has an independent setof network layer Service Access Points (SAPs). To make external handover possible, a commonmanagement 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 withouta valid subscription, i.e. a fast and easy means of giving information about an emergency situation to theappropriate emergency organization (e.g. fire service, police and ambulance).Display management (CAP-N.3): This feature enables a user to receive short alphanumeric indicationsdisplayed on the screen terminal. These indications could be associated with supplementary or valueadded services.Message waiting indication (CAP-N.4): This feature enables a user to receive an indication of the statusof a message server (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 atexpected intervals of time.On-air modification of user parameters (CAP-N.7): This feature enables the FT to modify the activesubscription data of the PT.5.1.1Application featuresSee ETS 300 444 [12].6Service definitionsFor the purposes of this ETS, the following service definitions apply.6.1DLC service definitionsSee ETS 300 444 [12].SIST ETS 300 824:1999

Page 16ETS 300 824: October 19976.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 theprimary Access Rights Identity (ARI) and secondary ARIs tertiary ARIs that the FT does not broadcast andare only available to PT as a Yes/No answer upon a request including the wanted ARI. These may beused to reflect an inter-operators agreement allowing a portable to access more than one operator orservices through FT.RFP status (CAP-M.2): A service which indicates to the PP the status (busy or clear) of the RFP or thesystem (FP).Extended fixed part capabilities (CAP-M.3): A service which indicates to the PP the extendedcapabilities of the FP.7Interoperability requirements7.1GeneralThe tables listed in this subclause define all the protocol elements i.e. features, services, and procedureswhich are mandatory, optional, and conditional under the provision of another protocol element, or out ofthe scope of this ETS, or in some context not-applicable according to the definition of the status columnas defined in subclause 3.3 for the CAP FP and PP. All optional elements shall be process mandatoryaccording to the procedures described in this ETS.Protocol elements defined as mandatory, optional or conditional in this subclause shall further be definedin clauses 8, 9, 10, 11, 12, 13 and 14 in detail either explicitly and/or as references to the DECT basestandard, ETS 300 175, parts 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 conformingto this ETS.7.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 Management (note)5.1MOOMCAP-N.4Message Waiting Indication5.1MOOMCAP-N.5Detach5.1MOOMCAP-N.6Periodic location registration5.1MOOMCAP-N.7On-air modification of user parameters5.1MOOONOTE:The PT is not mandated to support a physical display. The PT shall indicate its displaycapabilities within the field of a <> informationelement.7.3DLC servicesSee subclause 6.3 of ETS 300 444 [12].SIST ETS 300 824:1999

Page 17ETS 300 824: October 19977.4MAC servicesTable 2: MAC services statusService supportedStatusItem no.Name of serviceCAPRef.GAPRef.PTFTRBPCAP-M.1TARI support6.2OOOOCAP-M.2RFP status6.2MOMMCAP-M.3Extended fixed part capabilities6.2MOOM7.5Physical Layer (PHL) servicesSee subclause 6.5 of ETS 300 444 [12].7.6Application featuresSee subclause 6.6 of ETS 300 444 [12].SIST ETS 300 824:1999

Page 18ETS 300 824: October 19977.7NWK feature to procedure mappingTable 3: NWK feature to procedure mappingFeature/Procedure mappingStatusFeatureProcedureCAPRef.GAPRef.PTFTRBPN.11 Location registration4.1MOMMN.20 Terminate access rightsFT initiated4.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 setup9.1.4MMMMCiphering procedure PT initiated9.1.5.1OC3C3C3Ciphering procedure FT initiated9.1.5.2MC4C4MU-plane handling9.1.6MOMMCAP-N.2, Emergency call5.1MOOMEmergency call setup9.2MMMMCAP-N.3, DisplayManagement5.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 modificationof user 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 ETS 300 444 [12] THEN M ELSE O.C4IF feature N.17 of ETS 300 444 [12] THEN M ELSE O.SIST ETS 300 824:1999

Page 19ETS 300 824: October 19977.8Service to procedure mapping7.8.1DLC service to procedure mappingSee subclause 6.8.1 of ETS 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.5MMMM7.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/A7.9General requirementsSee subclauses 6.9.1 to 6.9.7 of ETS 300 444 [12].7.9.1Coexistence of MM and CC proceduresIn addition to subclause 6.9.6 of ETS 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) -00SIST ETS 300 824:1999

Page 20ETS 300 824: October 19978Procedure descriptionClauses 9 to 15 define the process mandatory procedures which are in the scope of the CAP. Eachprocedure (if appropriate) is divided into three parts:a)normal (i.e. successful case). This part defines the functions and respective protocol elementvalues in normal operation;b)associated procedure(s). This is an integral part of the actual procedure (if defined in this ETS) i.e.if a procedure is being declared to be supported, the respective entity shall also support theassociated procedures, e.g. timer management, in the subclause following the description of thenormal case;c)exceptional case(s). This is an integral part of the actual procedure (if defined in this ETS) i.e. if aprocedure is being declared to be supported, the respective entity shall also support the exceptionhandling defined in the subclause following the description of the normal case.All protocol elements listed in the following clauses are process mandatory i.e. the FT and PT dependingon their role in the procedure shall send or shall be capable of receiving and processing the relevantprotocol elements as listed in the respective tables if not explicitly stated as being optional.The primitives used in procedure descriptions are defined only for the purpose of describing layer-to-layerinteractions. The primitives are defined as an abstract list of parameters, and their concrete realizationmay vary between implementations. No formal testing of primitives is intended. The primitive definitionshave no normative significance.9NWK layer proceduresThis clause specifies the NWK layer procedures, messages and IEs required in the CAP.This profile does not prevent any PT or FT transmitting or receiving and processing any other NWK layermessage or IE not specified in the profile. A PT or FT receiving an unsupported NWK layer message or IEwhich it does not recognize shall ignore it, as specified in clause 17 of ETS 300 175-5 [5].9.1External handover procedures9.1.1Handover candidate procedureFP-1 shall only indicate handover candidates to which the PP has access using its active subscription.NOTE:The above implies that the PP does not need to analyse the Secondary Access RightsIdentities (SARIs) and/or TARIs supported by FP-2 prior to attempting externalhandover. Likewise, the PP need not analyse the external handover bit broadcast byFP-2 prior to attempting external handover.9.1.1.1Handover candidate indicationThe procedure shall be performed as defined in subclause 15.7.1.2 of ETS 300 175-5 [5]. The followingtext together with the associated subclauses define the mandatory requirements with regard to this ETS.The FP shall only apply CC- messages for the handover candidate indication. The indicated handovercandidates are valid until the release of the call or until the successful completion of an external handover.In case of external handover, FP-2 shall send the <> i.e. within a CC-INFO messageafter successful completion of the external handover procedure. Only one value is requested to be storedin the PP.The PP shall be able to perform external handover between FPs which indicate 2 or 3 in the fieldof the<> .NOTE:Successful completion of an external handover means, that the handover has beenaccepted as defined in subclause 15.7.4.3 of ETS 300 175-5 [5].SIST ETS 300 824:1999

Page 21ETS 300 824: October 1997Table 7: Coding of <> in call establishment CC messagesInformation elementField within theinformation elementStandard valueswithin the field/IENormative action/comment<>0Other fixed part IDs not availableusing parameter retrieval procedure1Other fixed part IDs available usingparameter retrieval procedureAllAll9.1.1.2Handover candidate retrievalThe procedure shall be performed as defined in subclause 15.7.1.3 of ETS 300 175-5 [5]. The followingtext together with the associated subclauses define the mandatory requirements with regard to this ETS.The PP shall not invoke this procedure if the <> has not yet received or if the<> has been received with the OID value set to "0".If the PP sends a {MM-INFO-REQUEST} message with an <> IE indicating "external handoverparameters", the FP shall also include a handover reference in a <> IE unless thehandover reference is not required. In this case the FP shall inform the PP including in the response a<> IE with the value "handover reference not required".9.1.1.2.1Exceptional cases9.1.1.2.1.1Failure of the PP handover candidate retrieval attemptUpon receipt of a {MM_INFO_REJECT} or when an indication for link release is received from the DLClayer or upon expiry of P-, the PP shall consider the procedure as failed. For target FPselection, the PP shall then either:-use the as received during handover candidate indication; or-repeat the handover candidate retrieval procedure.9.1.2Target FP selectionThe procedure shall be performed as defined in subclause 15.7.1.4 of ETS 300 175-5 [5]. The followingtext together with the associated subclauses define the mandatory requirements with regard to this ETS.If the handover candidate retrieval procedure is not allowed (OID = 0) or the PP has already detectedsome candidates for handover, the PP determines which FPs it may attempt external handover to bycomparing the PARI of the FP in use with the PARIs of candidate FPs and determining if they match in thebits indicated by the "ext h/o length indicator" derived from the <> IE.SIST ETS 300 824:1999

Page 22ETS 300 824: October 19979.1.3Handover reference proce
...