ETSI EN 300 444 V1.4.2 (2003-02)
Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)
Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)
REN/DECT-000219
Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Profil generičnega dostopa (GAP)
General Information
Standards Content (Sample)
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.4.2SIST EN 300 444 V1.4.2:2003en01-december-2003SIST EN 300 444 V1.4.2:2003SLOVENSKI
STANDARD
ETSI ETSI EN 300 444 V1.4.2 (2003-02) 2
Reference REN/DECT-000219 Keywords access, DECT, generic, profile, radio, synchronization ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88
Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editor@etsi.org Copyright Notification No 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 2003. All rights reserved.
DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. SIST EN 300 444 V1.4.2:2003
ETSI ETSI EN 300 444 V1.4.2 (2003-02) 3
Contents Intellectual Property Rights.9 Foreword.9 1 Scope.10 2 References.10 3 Definitions, symbols and abbreviations.11 3.1 Definitions.11 3.2 Symbols.13 3.3 Abbreviations.14 4 Feature definitions.15 4.1 Network (NWK) features.15 4.2 Application features.16 5 Service definitions.17 5.1 DLC service definitions.17 5.2 MAC service definitions.17 6 Inter-operability requirements.18 6.1 General.18 6.2 NWK features.19 6.3 DLC services.20 6.4 MAC services.20 6.5 Physical layer (PHL) services.20 6.6 Application features.21 6.7 NWK feature to procedure mapping.21 6.8 Service to procedure mapping.23 6.8.1 DLC service to procedure mapping.23 6.8.2 MAC service to procedure mapping.24 6.8.3 Application feature to procedure mapping.25 6.9 General requirements.25 6.9.1 NWK layer message contents.25 6.9.2 Transaction identifier.25 6.9.3 Length of a NWK layer message.25 6.9.4 Handling of error and exception conditions.25 6.9.5 GAP default setup attributes.26 6.9.6 Coexistence of MM and CC procedures.26 6.9.7 Coding rules for information elements.26 7 Procedure description.26 8 NWK layer procedures.27 8.1 Summary of outgoing call messages, normal cases.27 8.2 Outgoing call request.28 8.2.1 Associated procedures.29 8.2.1.1 Timer P- management.29 8.2.2 Exceptional cases.30 8.2.2.1 Timer P- expiry.30 8.2.2.2 PT releases the outgoing call request.30 8.2.2.3 FT rejects the outgoing call request.31 8.3 Overlap sending.31 8.3.1 Associated procedure.32 8.3.1.1 Timer F- management.32 8.3.2 Exceptional cases.32 8.3.2.1 PT releases the outgoing call request.32 8.3.2.2 FT rejects the outgoing call request.32 8.3.2.3 Timer F- expiry.33 SIST EN 300 444 V1.4.2:2003
ETSI ETSI EN 300 444 V1.4.2 (2003-02) 4
8.3.2.4 FT releases the outgoing call request.33 8.4 Outgoing call proceeding.34 8.4.1 Exceptional cases.34 8.4.1.1 PT releases the outgoing call request.34 8.4.1.2 FT releases the outgoing call request.35 8.5 Outgoing call confirmation.35 8.5.1 Exceptional cases.36 8.5.1.1 PT releases the outgoing call request.36 8.5.1.2 FT releases the outgoing call request.36 8.6 Outgoing call connection.37 8.7 Normal call release.37 8.7.1 Associated procedures.38 8.7.1.1 Timer P- management.38 8.7.1.2 Timer F- management.38 8.7.2 Exceptional cases.39 8.7.2.1 Release collisions.39 8.7.2.2 Timer F- expiry.39 8.7.2.3 Timer P- expiry.40 8.8 Abnormal call release.40 8.9 Partial release.41 8.10 Sending keypad information.42 8.11 Summary of incoming call related messages, normal cases.43 8.12 Incoming call request.43 8.12.1 Associated procedure.44 8.12.1.1 Timer F- management.44 8.12.2 Exceptional cases.45 8.12.2.1 FT releases the incoming call request.45 8.12.2.2 PT rejects the incoming call request.45 8.12.2.3 Timer F- expiry.46 8.12.3 Collective and group ringing.46 8.13 Incoming call confirmation.46 8.13.1 Exceptional cases.47 8.13.1.1 FT releases the incoming call transaction.47 8.13.1.2 PT releases the incoming call transaction.47 8.14 PT alerting.48 8.15 Incoming call connection.48 8.15.1 Associated procedure.49 8.15.1.1 Timer P- management.49 8.15.2 Exceptional cases.49 8.15.2.1 FT releases the incoming call transaction.49 8.15.2.2 PT releases the incoming call transaction.50 8.15.2.3 Timer P- expiry.50 8.16 Display.50 8.17 Terminal capability indication.51 8.18 Internal call setup.52 8.19 Internal call keypad.52 8.20 Service call setup.53 8.21 Service call keypad.53 8.22 Identification of PP.53 8.22.1 Associated procedure.54 8.22.1.1 Timer F- management.54 8.22.2 Exceptional cases.54 8.22.2.1 Identity not existing in the PT.54 8.22.2.2 Timer F- expiry.54 8.23 Authentication of FT.55 8.23.1 Associated procedure.55 8.23.1.1 Timer P- management.55 8.23.2 Exceptional cases.56 8.23.2.1 Authentication algorithm/key not supported.56 8.23.2.2 Authentication challenge RES has wrong value.56 8.23.2.3 Timer P- expiry.56 8.24 Authentication of PP.57 SIST EN 300 444 V1.4.2:2003
ETSI ETSI EN 300 444 V1.4.2 (2003-02) 5
8.24.1 Associated procedure.58 8.24.1.1 Timer F- management.58 8.24.2 Exceptional cases.58 8.24.2.1 Authentication algorithm/key not supported.58 8.24.2.2 Timer F- expiry.58 8.25 Authentication of user.58 8.25.1 Associated procedure.59 8.25.1.1 Timer F- management.59 8.25.2 Exceptional cases.59 8.25.2.1 Authentication algorithm/key not supported.59 8.25.2.2 Timer F- expiry.59 8.26 Incrementing the ZAP value.59 8.27 Storing the DCK.60 8.28 Location registration.60 8.28.1 Associated procedures.62 8.28.1.1 Timer P- management.62 8.28.1.2 Timer F- management.62 8.28.2 Exceptional cases.62 8.28.2.1 FT rejects the location registration procedure.62 8.28.2.2 Failure of location registration procedure.63 8.28.2.3 PT rejects the identity assignment.63 8.28.2.4 Timer F- expiry.63 8.29 Location update.64 8.30 Obtaining access rights.65 8.30.1 Associated procedure.67 8.30.1.1 Timer P- management.67 8.30.2 Exceptional cases.67 8.30.2.1 FT rejects the access rights.67 8.30.2.2 Timer P- expiry.67 8.31 FT terminating access rights.68 8.31.1 Associated procedure.69 8.31.1.1 Timer F- management.69 8.31.2 Exceptional cases.69 8.31.2.1 PT rejects the termination request.69 8.31.2.2 Timer F- expiry.69 8.32 Key allocation.69 8.32.1 Associated procedures.71 8.32.1.1 Timer F- management.71 8.32.1.2 Timer P- management.71 8.32.2 Exceptional cases.71 8.32.2.1 Timer F- expiry.71 8.32.2.2 Timer P- expiry.71 8.32.2.3 Allocation-type element is unacceptable.71 8.32.2.4 Authentication of PT fails.72 8.32.2.5 Authentication of FT fails.72 8.33 Cipher-switching initiated by FT.72 8.33.1 Associated procedure.73 8.33.1.1 Timer F- management.73 8.33.2 Exceptional cases.74 8.33.2.1 PT rejects the cipher request.74 8.33.2.2 Timer F- expiry.74 8.34 Cipher-switching initiated by PT.75 8.34.1 Associated procedure.76 8.34.1.1 Timer P- management.76 8.34.2 Exceptional cases.76 8.34.2.1 FT rejects the cipher request.76 8.34.2.2 Timer P- expiry.76 8.35 Indirect FT initiated link establishment.76 8.35.1 Associated procedure.77 8.35.1.1 Timer F- management.77 8.35.2 Exceptional cases.78 8.35.2.1 The IPUI received in the {LCE-PAGE-RESPONSE} does not match.78 SIST EN 300 444 V1.4.2:2003
ETSI ETSI EN 300 444 V1.4.2 (2003-02) 6
8.35.2.2 Timer expiry.78 8.35.2.3 Release from the higher entity.79 8.36 Direct PT initiated link establishment.79 8.36.1 Exceptional case.80 8.36.1.1 Link establishment failure.80 8.37 Link release "normal".80 8.37.1 Associated procedure.82 8.37.1.1 Timer management.82 8.37.2 Exceptional cases.82 8.37.2.1 Timer expiry.82 8.37.2.2 Outstanding data has been discarded.82 8.38 Link release "abnormal".83 8.39 Link release "maintain".83 8.39.1 Associated procedure.83 8.39.1.1 Timer management.83 8.40 Enhanced FT initiated U- plane connection.84 9 DLC layer procedures.84 9.1 Class A link establishment.84 9.1.1 Associated procedures.86 9.1.1.1 Timer P management.86 9.1.1.2 Re-transmission counter management.86 9.1.1.3 Multiple frame operation variables management.86 9.1.1.4 Lower Layer Management Entity (LLME) establishment of a MAC connection.86 9.1.2 Exceptional cases.87 9.1.2.1 Timer P expiry.87 9.1.2.2 Receipt of a request for link release.88 9.1.2.3 Receipt of an indication for a connection release.88 9.2 Class A Acknowledged Information transfer.88 9.2.1 Acknowledgement with an I_frame.88 9.2.2 Acknowledgement with a RR_frame.89 9.2.3 Class A acknowledged information transfer with segment reassemble.90 9.2.4 Associated procedures.90 9.2.4.1 Timer management.90 9.2.4.2 Re-transmission counter management.90 9.2.4.3 Multiple frame operation variables management.90 9.2.5 Exceptional cases.91 9.2.5.1 Timer expiry.91 9.2.5.2 Receipt of a request for link release.91 9.2.5.3 Receipt of an indication for a connection release.91 9.2.5.4 DLC wants to make a connection handover.91 9.3 Class A link release.91 9.3.1 Associated procedures.92 9.3.1.1 LLME U-plane release.92 9.3.1.2 LLME release a MAC connection.92 9.4 Class A link re-establishment.92 9.5 CS channel fragmentation and recombination.92 9.6 Normal broadcast.92 9.7 Class A basic connection handover.93 9.7.1 Voluntary handover.94 9.7.2 Associated procedure.94 9.7.2.1 LLME connection handover management.94 9.7.3 Exceptional case.94 9.7.3.1 Receipt of a request for link release.94 9.8 Encryption switching.94 9.8.1 Associated procedure.95 9.8.1.1 Providing Encryption key to the MAC layer.95 9.8.2 Exceptional cases.95 9.8.2.1 Encryption fails.95 9.8.2.2 Connection handover of ciphered connections.95 9.9 U-plane class 0/min delay.95 9.9.1 Associated procedure.95 SIST EN 300 444 V1.4.2:2003
ETSI ETSI EN 300 444 V1.4.2 (2003-02) 7
9.9.1.1 LLME U-plane establishment.95 9.10 FU1 frame operation.96 10 MAC layer procedures.96 10.1 General.96 10.2 Downlink broadcast.97 10.2.1 NT message.97 10.2.2 QT - static system information.97 10.2.3 QT - FP capabilities.98 10.2.4 QT - SARI list contents.98 10.3 Paging broadcast.98 10.3.1 Short page, normal/extended paging.99 10.3.2 Zero page normal/extended paging.99 10.3.3 Blind slot information.99 10.3.4 Bearer handover information.100 10.4 Setup of basic connection, basic bearer setup (A-field).100 10.4.1 MT message.101 10.4.2 Associated procedures.101 10.4.2.1 Timer T200 management.101 10.4.2.2 Counter N200 management.101 10.4.3 Exceptional cases.102 10.4.3.1 Bearer setup attempt fails N200+1 times.102 10.4.3.2 Timer T200 expiry.103 10.5 Connection/bearer release.103 10.5.1 MT message.104 10.6 Bearer handover request.104 10.6.1 MT message.104 10.7 Connection handover request.104 10.7.1 MT message.105 10.8 CS channel data.105 10.9 Q2 bit setting.105 10.10 RFPI handshake.105 10.11 Antenna diversity.105 10.12 Sliding collision.105 10.13 Encryption process - initialization and synchronization.105 10.14 Encryption mode control.106 10.14.1 MT message.106 10.15 Handover encryption process.
...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...