DS/EN 300 444 V2.4.1
Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)
| Organization: | DS |
| Publication Date: | 21 August 2013 |
| Status: | active |
| ICS Code (Telecommunications in general): | 33.020 |
scope:
The 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 Generic Access Profile (GAP). The GAP is applicable to all DECT Portable radio Terminations (PT) and Fixed radio Terminations (FT) which under the scope of EN 300 176-2 [10] (i.e. 3,1 kHz telephony teleservice) and specifies the minimum functionality that is supported by all other 3,1 kHz voice profiles. The objective of the present document is to ensure the Air Interface (AI) inter-operability of DECT equipment capable of 3,1 kHz telephony applications, in such a way that any DECT PT conforming to the procedures described in the present document is inter-operable with any DECT FT conforming to the procedures described in the present document. The profile consists of the minimum mandatory requirements that allow a 3,1 kHz teleservice connection to be established, maintained and released between a FT and a PT with the appropriate access rights, irrespective of whether the FP provides residential, business or public access services. In addition, the present document defines the features, services, procedures etc. for both the FT and the PT, which are provision mandatory either in the PT or in the FT, as well as some elements that are provision optional but still process mandatory. Mobility Management (MM) procedures at the DECT AI to support incoming calls and outgoing calls are included. Inter-working between the FT and the attached network is outside the scope of the present document. The inherent nature of certain situations makes it impossible to make reliable and definitive statements that accessibility requirements have been met. For this reason, the requirements in the present document are not applicable: - to the situation in which the party claiming accessibility exerts no control on the functionality or content; - when the product is in a failure, repair or maintenance state where the ordinary set of input or output functions are not available; - during those parts of start-up, shutdown, and other state transitions that can be completed without user interaction. NOTE: Even in the above situations, it is best practice to apply requirements in the present document wherever it is feasible and safe to do so.
Document History