SIST EN 300 444 V1.3.3:2003

• Abstract:

  To specify the mandatory frame synchronization requirements for public GAP FP. To specify requirements for a GAP CRFP terminal and requireme nts for GAP FP support of CRFP terminals.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Mandate: T-317
• Ref Project: ETSI EN 300 444 V1.3.3 (1999-05) - Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)

Overview

SIST EN 300 444 V1.3.3:2003, also known as the "Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)", is a European standard that specifies essential requirements for interoperable DECT devices. It has been developed to facilitate communication between DECT Fixed Parts (FP) and Portable Parts (PP) from different manufacturers. A primary goal of this standard is to ensure that cordless telecommunication devices using DECT technology, such as base stations and handsets, can operate together under the Generic Access Profile (GAP).

The standard outlines the mandatory frame synchronization requirements for public GAP Fixed Parts (FP), and sets out the requirements a GAP Cordless RFP (CRFP) terminal must meet. It also details the necessary support that GAP FP must offer to enable interoperability with CRFP terminals.

Key Topics

SIST EN 300 444 V1.3.3:2003 encompasses various critical aspects, including:

• DECT frame synchronization: Defines technical synchronization requirements for public GAP Fixed Parts to ensure reliable communication and device interoperability.
• Terminal requirements: Specifies what is required of a GAP CRFP terminal and the conditions for supporting these terminals within a GAP FP environment.
• Interoperability features: Describes how DECT devices, including handsets and base stations from various vendors, can interoperate using GAP.
• Service definitions: Outlines services managed at the Data Link Control (DLC) and Medium Access Control (MAC) layers.
• Procedural mappings: Provides mapping of features and services to corresponding operational procedures, ensuring seamless operation and compatibility.
• Network layer functions: Covers network features such as call initiation, handling exceptional cases, and information exchange.

GAP compliance makes it possible for users to mix and match DECT portable parts (e.g., handsets) and fixed parts (e.g., base stations) from different manufacturers, leading to flexible, user-friendly cordless telecommunication solutions.

Applications

The practical value of SIST EN 300 444 V1.3.3:2003 lies in its significant support for interoperability and device compatibility in DECT systems. Common applications include:

• Cordless telephony: Enables users to pair handsets and base stations regardless of brand, streamlining deployments in homes, offices, and public areas.
• Public and home environments: Ideal for residential and business cordless telephone systems where easy replacement and upgrading of equipment are required without lock-in to a single vendor.
• Enterprise communication systems: Supports scalable communication setups in office environments, DECT PBX systems, and enterprise-grade wireless telephony.
• Hospitality and healthcare: Facilitates robust, reliable cordless connectivity for hotels, hospitals, and similar facilities where DECT is preferred for wireless voice communication.

Interoperable DECT devices ensure lower costs, easier device replacement, and enhanced service continuity across various environments by following the GAP standard.

Related Standards

To offer a comprehensive DECT solution, SIST EN 300 444 V1.3.3:2003 should be implemented alongside other key standards:

• EN 300 175 series: Core standards defining the DECT Common Interface.
• ETSI EN 300 176: Test specifications for DECT interoperability.
• EN 301 406: Coverage of DECT for public access applications.
• EN 300 403: Additional specifications for DECT transmission and subsystem features.

These related standards work together to ensure that DECT devices are secure, interoperable, and reliable within wireless communication systems.

Keywords: DECT, Generic Access Profile, GAP, cordless telephony, frame synchronization, interoperability, wireless communication, European standard, cordless phone systems, DECT FP, DECT PP, base station, handset compatibility.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 444 Version 1.3.3SIST EN 300 444 V1.3.3:2003en01-december-2003SIST EN 300 444 V1.3.3:2003SLOVENSKI
STANDARD
EN 300 444 V1.3.3 (1999-05)European Standard (Telecommunications series)Digital Enhanced Cordless Telecommunications (DECT);Generic Access Profile (GAP)SIST EN 300 444 V1.3.3:2003

ETSIETSI EN 300 444 V1.3.3 (1999-05)2ReferenceREN/DECT-050111 (44000j20.PDF)KeywordsDECT, access, generic, profile, radio,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 444 V1.3.3:2003

ETSIETSI EN 300 444 V1.3.3 (1999-05)3ContentsIntellectual Property Rights.9Foreword.91Scope.102References.103Definitions, symbols and abbreviations.113.1Definitions.113.2Symbols.133.3Abbreviations.144Feature definitions.154.1Network (NWK) features.154.2Application features.175Service definitions.175.1DLC service definitions.175.2MAC service definitions.186Inter-operability requirements.186.1General.186.2NWK features.196.3DLC services.206.4MAC services.206.5Physical (PHL) layer services.206.6Application features.216.7NWK feature to procedure mapping.216.8Service to procedure mapping.236.8.1DLC service to procedure mapping.236.8.2MAC service to procedure mapping.246.8.3Application feature to procedure mapping.256.9General requirements.256.9.1NWK layer message contents.256.9.2Transaction identifier.256.9.3Length of a NWK layer message.256.9.4Handling of error and exception conditions.256.9.5GAP default setup attributes.266.9.6Coexistence of MM and CC procedures.266.9.7Coding rules for information elements.267Procedure description.268NWK layer procedures.278.1Summary of outgoing call messages, normal cases.278.2Outgoing call request.288.2.1Associated procedures.298.2.1.1Timer P- management.298.2.2Exceptional cases.308.2.2.1Timer P- expiry.308.2.2.2PT releases the outgoing call request.308.2.2.3FT rejects the outgoing call request.318.3Overlap sending.318.3.1Associated procedure.328.3.1.1Timer F- management.328.3.2Exceptional cases.328.3.2.1PT releases the outgoing call request.328.3.2.2FT rejects the outgoing call request.328.3.2.3Timer F- expiry.33SIST EN 300 444 V1.3.3:2003

ETSIETSI EN 300 444 V1.3.3 (1999-05)48.3.2.4FT releases the outgoing call request.338.4Outgoing call proceeding.348.4.1Exceptional cases.348.4.1.1PT releases the outgoing call request.348.4.1.2FT releases the outgoing call request.358.5Outgoing call confirmation.358.5.1Exceptional cases.358.5.1.1PT releases the outgoing call request.358.5.1.2FT releases the outgoing call request.368.6Outgoing call connection.368.7Normal call release.378.7.1Associated procedures.388.7.1.1Timer P- management.388.7.1.2Timer F- management.388.7.2Exceptional cases.388.7.2.1Release collisions.388.7.2.2Timer F- expiry.398.7.2.3Timer P- expiry.398.8Abnormal call release.408.9Partial release.408.10Sending keypad information.418.11Summary of incoming call related messages, normal cases.428.12Incoming call request.438.12.1Associated procedure.448.12.1.1Timer F- management.448.12.2Exceptional cases.458.12.2.1FT releases the incoming call request.458.12.2.2PT rejects the incoming call request.458.12.2.3Timer F- expiry.468.12.3Collective and group ringing.468.13Incoming call confirmation.468.13.1Exceptional cases.478.13.1.1FT releases the incoming call transaction.478.13.1.2PT releases the incoming call transaction.478.14PT alerting.478.15Incoming call connection.488.15.1Associated procedure.498.15.1.1Timer P- management.498.15.2Exceptional cases.498.15.2.1FT releases the incoming call transaction.498.15.2.2PT releases the incoming call transaction.498.15.2.3Timer P- expiry.508.16Display.508.17Terminal capability indication.518.18Internal call setup.528.19Internal call keypad.528.20Service call setup.528.21Service call keypad.538.22Identification of PP.538.22.1Associated procedure.548.22.1.1Timer F- management.548.22.2Exceptional cases.548.22.2.1Identity not existing in the PT.548.22.2.2Timer F- expiry.548.23Authentication of FT.558.23.1Associated procedure.558.23.1.1Timer P- management.558.23.2Exceptional cases.568.23.2.1Authentication algorithm/key not supported.568.23.2.2Authentication challenge RES has wrong value.56SIST EN 300 444 V1.3.3:2003

ETSIETSI EN 300 444 V1.3.3 (1999-05)58.23.2.3Timer P- expiry.568.24Authentication of PP.568.24.1Associated procedure.588.24.1.1Timer F- management.588.24.2Exceptional cases.588.24.2.1Authentication algorithm/key not supported.588.24.2.2Timer F- expiry.588.25Authentication of user.588.25.1Associated procedure.598.25.1.1Timer F- management.598.25.2Exceptional cases.598.25.2.1Authentication algorithm/key not supported.598.25.2.2Timer F- expiry.598.26Incrementing the ZAP value.598.27Storing the DCK.608.28Location registration.608.28.1Associated procedures.628.28.1.1Timer P- management.628.28.1.2Timer F- management.628.28.2Exceptional cases.628.28.2.1FT rejects the location registration procedure.628.28.2.2Failure of location registration procedure.638.28.2.3PT rejects the identity assignment.638.28.2.4Timer F- expiry.638.29Location update.638.30Obtaining access rights.648.30.1Associated procedure.668.30.1.1Timer P- management.668.30.2Exceptional cases.668.30.2.1FT rejects the access rights.668.30.2.2Timer P- expiry.678.31FT terminating access rights.678.31.1Associated procedure.688.31.1.1Timer F- management.688.31.2Exceptional cases.688.31.2.1PT rejects the termination request.688.31.2.2Timer F- expiry.688.32Key allocation.698.32.1Associated procedures.708.32.1.1Timer F- management.708.32.1.2Timer P- management.708.32.2Exceptional cases.708.32.2.1Timer F- expiry.708.32.2.2Timer P- expiry.708.32.2.3Allocation-type element is unacceptable.718.32.2.4Authentication of PT fails.718.32.2.5Authentication of FT fails.728.33Cipher-switching initiated by FT.728.33.1Associated procedure.738.33.1.1Timer F- management.738.33.2Exceptional cases.738.33.2.1PT rejects the cipher request.738.33.2.2Timer F- expiry.738.34Cipher-switching initiated by PT.748.34.1Associated procedure.758.34.1.1Timer P- management.758.34.2Exceptional cases.758.34.2.1FT rejects the cipher request.758.34.2.2Timer P- expiry.758.35Indirect FT initiated link establishment.76SIST EN 300 444 V1.3.3:2003

ETSIETSI EN 300 444 V1.3.3 (1999-05)68.35.1Associated procedure.778.35.1.1Timer F- management.778.35.2Exceptional cases.778.35.2.1The IPUI received in the {LCE-PAGE-RESPONSE} does not match.778.35.2.2Timer expiry.788.35.2.3Release from the higher entity.788.36Direct PT initiated link establishment.788.36.1Exceptional case.808.36.1.1Link establishment failure.808.37Link release "normal".808.37.1Associated procedure.818.37.1.1Timer management.818.37.2Exceptional cases.828.37.2.1Timer expiry.828.37.2.2Outstanding data has been discarded.828.38Link release "abnormal".838.39Link release "maintain".838.39.1Associated procedure.838.39.1.1Timer management.838.40Enhanced FT initiated U- plane connection.839DLC layer procedures.849.1Class A link establishment.849.1.1Associated procedures.869.1.1.1Timer P management.869.1.1.2Re-transmission counter management.869.1.1.3Multiple frame operation variables management.869.1.1.4Lower Layer Management Entity (LLME) establishment of a MAC connection.869.1.2Exceptional cases.879.1.2.1Timer P expiry.879.1.2.2Receipt of a request for link release.889.1.2.3Receipt of an indication for a connection release.889.2Class A Acknowledged Information transfer.889.2.1Acknowledgement with an I_frame.889.2.2Acknowledgement with a RR_frame.899.2.3Class A acknowledged information transfer with segment reassemble.909.2.4Associated procedures.909.2.4.1Timer management.909.2.4.2Re-transmission counter management.909.2.4.3Multiple frame operation variables management.909.2.5Exceptional cases.919.2.5.1Timer expiry.919.2.5.2Receipt of a request for link release.919.2.5.3Receipt of an indication for a connection release.919.2.5.4DLC wants to make a connection handover.919.3Class A link release.919.3.1Associated procedures.929.3.1.1LLME U-plane release.929.3.1.2LLME release a MAC connection.929.4Class A link re-establishment.929.5Cs channel fragmentation and recombination.929.6Normal broadcast.929.7Class A basic connection handover.939.7.1Voluntary handover.949.7.2Associated procedure.949.7.2.1LLME connection handover management.949.7.3Exceptional case.949.7.3.1Receipt of a request for link release.949.8Encryption switching.949.8.1Associated procedure.959.8.1.1Providing Encryption key to the MAC layer.95SIST EN 300 444 V1.3.3:2003

ETSIETSI EN 300 444 V1.3.3 (1999-05)79.8.2Exceptional cases.959.8.2.1Encryption fails.959.8.2.2Connection handover of ciphered connections.959.9U-plane class 0/min delay.959.9.1Associated procedure.959.9.1.1LLME U-plane establishment.959.10FU1 frame operation.9510MAC layer procedures.9610.1General.9610.2Downlink broadcast.9610.2.1Nt message.9710.2.2Qt - static system information.9710.2.3Qt - FP capabilities.9710.2.4Qt - SARI list contents.9810.3Paging broadcast.9810.3.1Short page, normal/extended paging.9810.3.2Zero page normal/extended paging.9910.3.3Blind slot information.9910.3.4Bearer handover information.10010.4Setup of basic connection, basic bearer setup (A-field).10010.4.1Mt message.10010.4.2Associated procedures.10110.4.2.1Timer T200 management.10110.4.2.2Counter N200 management.10110.4.3Exceptional cases.10110.4.3.1Bearer setup attempt fails N200+1 times.10110.4.3.2Timer T200 expiry.10210.5Connection/bearer release.10210.5.1Mt message.10210.6Bearer handover request.10310.6.1Mt message.10310.7Connection handover request.10310.7.1Mt message.10310.8Cs channel data.10410.9Q2 bit setting.10410.10RFPI handshake.10410.11Antenna diversity.10410.12Sliding collision.10410.13Encryption process - initialization and synchronization.10410.14Encryption mode control.10510.14.1Mt message.10510.15Handover encryption process.10510.16Extended frequency allocation.10511PHL layer requirements.10611.1General.10611.2Minimum Normal Transmit Power (NTP).10611.3Radio receiver sensitivity.10611.4Z-field.10611.5Sliding collision detection.10611.6Physical channel availability.10611.7Synchronization window.10612Requirements regarding the speech transmission.10712.1
...