SIST ETS 300 175-5 E1:2003
(Main)Radio Equipment and Systems (RES); Digital European Cordless Telecommunications (DECT) Common Interface Part 5: Network layer
- Abstract
..
- Status
- Published
- Publication Date
- 30-Nov-2003
- 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-176
SIST ETS 300 175-5 E1:2003 is the Slovenian version of ETS 300 175-5 Edition 1, published by SIST. It specifies the DECT Common Interface network layer, which is layer 3 of the DECT protocol stack, for the control plane between Fixed Termination (FT) and Portable Termination (PT). The document is for engineers, system integrators, and test teams working on DECT equipment, interworking units, and network-side support functions.
What does SIST ETS 300 175-5 E1:2003 specify?
SIST ETS 300 175-5 E1:2003 specifies the DECT network layer, with the focus on the C-plane (control plane). It defines how DECT signalling is organized, how messages are structured, and how the main network-layer procedures operate between FT and PT.
The document is organized into a short overview, then message definitions and structures, followed by procedure clauses for call control, supplementary services, COMS, CLMS, MM, LCE, management, primitives, and error handling. Annexes provide timers, state transitions, character sets, and IWU-related material.
| Annex | What it covers |
|---|---|
| Annex A | Timers and network layer constants |
| Annex B | Call Control state transitions at PT side and FT side |
| Annex D | DECT standard 8-bit characters and DECT standard 4-bit characters |
| Annex G | Sending and rejection of <<IWU-PACKET>> and <<IWU-TO-IWU>> elements |
What are the key requirements of SIST ETS 300 175-5 E1:2003?
Clause 1 limits this part to the DECT network layer and states that the U-plane is null at this layer. In practice, that means the document is about signalling and control behavior, not user payload transport.
Clause 4 groups the network layer into six entities: LCE, CC, CISS, COMS, CLMS, and MM, with the LLME coordinating them. This matters because implementers have to map software functions and interfaces to these entities, not treat the network layer as one single block.
Message structure and coding
Clauses 6 to 8 define the message families and the coding rules for S-FORMAT and B-FORMAT messages. They cover protocol discrimination, transaction identifiers, message types, information elements, fixed-length and variable-length content, and the structure of CLMS-FIXED messages. In practice, this is the part that tells a developer how to build and parse DECT network-layer messages correctly.
Clause 7 also defines the coding of many information elements, including display, keypad, release reason, cipher info, connection attributes, end-to-end compatibility, feature activate, IWU attributes, and portable identity fields. That matters because interworking and interoperability depend on consistent field coding, not just on the message name.
Call control
Clause 9 defines Call Control (CC) states for PT and FT and the procedures for outgoing and incoming call establishment, call information, call release, service change, and packet mode. Annex B expands the CC state transitions, while Annex A provides the timers used in the procedures. For a product team, this is the operational model for how calls move from setup to active use and release.
Supplementary services
Clause 10 covers the keypad protocol, feature key management protocol, and functional protocol. It also describes how multiple protocols coexist and names application protocols for DECT standard functional supplementary services and DECT specific supplementary services such as queue management, subscriber number indication, echo control functions, and cost information. In practice, this is the part used when a handset or base station has to support service features beyond simple call setup.
Connection-oriented and connectionless messaging
Clause 11 defines COMS states and procedures for establishment, data transfer, suspend and resume, and release. Clause 12 does the same for CLMS, including fixed length and variable length messages, plus separate PT and FT procedures. This matters when equipment must carry non-call signalling or data-like exchanges through DECT in a controlled way.
Mobility, link control, and management
Clause 13 covers MM procedures for identity, authentication, location registration and update, access rights, key allocation, parameter retrieval, and ciphering. Clause 14 covers LCE procedures for link establishment, re-establishment, release, suspend and resume, message routing, and broadcast announce. Clause 15 adds management for LLME, service mapping and negotiation, resource management, call ciphering management, external handover management, and test management. Together, these clauses define how DECT handles identity, access, paging, mobility, and operational control.
Error handling and primitives
Clause 17 defines protocol error and exception handling for cases such as short messages, transaction identifier errors, message sequence errors, missing or invalid information elements, data link reset, and data link failure. Clause 16 lists the primitives exchanged with the DLC layer and the IWU, including MNCC, MNSS, MNCO, MNCL, and MM primitives. In practice, these clauses are what developers use to design interfaces, logging, and error recovery.
What terms does SIST ETS 300 175-5 E1:2003 define?
- Portable Termination (PT) - the portable side of the DECT connection, used for the handset or mobile unit behavior.
- Fixed Termination (FT) - the fixed side of the DECT connection, used for base-station or network-side behavior.
- Control plane (C-plane) - the signalling plane that carries DECT internal control information.
- User plane (U-plane) - the traffic plane for user data, which is null at the DECT network layer in this part.
- Link Control Entity (LCE) - the entity that establishes, maintains, and releases the C-plane link.
- Lower Layer Management Entity (LLME) - the coordination entity for operations between network-layer entities and the lower layers.
- Connection Oriented Message Service (COMS) - the network-layer service for connected message exchange with connect, transfer, suspend, resume, and release behavior.
- ConnectionLess Message Service (CLMS) - the network-layer service for connectionless messages, including fixed-length and variable-length forms.
Who uses SIST ETS 300 175-5 E1:2003?
SIST ETS 300 175-5 E1:2003 is used by DECT equipment designers, protocol engineers, and interoperability test teams. It is also relevant to vendors of fixed parts, portable parts, and interworking units that have to exchange call, mobility, and message-control signalling.
Typical users include:
- DECT terminal and base-station developers
- Network and protocol software implementers
- Interworking unit (IWU) designers
- Test laboratories and conformance teams
- Quality and integration teams validating call control, mobility, and supplementary services
- Buyers and technical evaluators checking support for DECT Common Interface network-layer behavior
Which standards are used with SIST ETS 300 175-5 E1:2003?
The standard is used with the other parts of the DECT Common Interface series, especially:
- ETS 300 175-1 - overview, definitions, symbols, and abbreviations
- ETS 300 175-2 - physical layer context
- ETS 300 175-3 - medium access control layer context, including bearer and packet-related attributes
- ETS 300 175-4 - data link control layer context and U-plane link numbering
- ETS 300 175-6 - identities and addressing, including portable identity and equipment identity coding
- ETS 300 175-7 - security features used alongside MM and ciphering
- ETS 300 175-8 - speech coding and transmission, also referenced by echo-control and service-related coding
- ETS 300 175-9 - public access profile context
It also relies on external standards and recommendations for modelling and coding, including:
- CCITT Recommendation X.200 and X.210 - OSI layering model and service conventions
- ETS 300 102-1 and ETS 300 102-2 - basic call control background and SDL diagrams
- CCITT Recommendation T.50 and ISO Publication 2022 - character-set and code-extension techniques
- ETS 300 133-1 to -7 - ERMES character-set references used in coding tables
- I-ETS 300 176 - approval test specification
- Several ISDN, GSM, packet, and signalling references that supply coding models used in CC, MM, CLMS, COMS, and IWU interworking
What does the SIST ETS 300 175-5 E1:2003 document contain?
The document contains procedure descriptions, message summaries, message formats, state tables, coding rules, and detailed information-element definitions. It gives the structure of S-FORMAT and B-FORMAT messages, including how information elements are arranged and encoded, and it describes the sequence of signalling actions for call control, supplementary services, COMS, CLMS, MM, and LCE.
It also contains the tables that define release reasons, ciphering and connection attributes, end-to-end compatibility, rate parameters, identity coding, and service change information. Annex A collects timers and constants, Annex B gives state transitions for Call Control, Annex D defines the standard character sets, and Annex G covers IWU packet and IWU-to-IWU element handling.
For implementers and test teams, the document functions as a coding and behavior reference: what to send, how to encode it, how to react to each procedure, and how to handle error and exception cases.
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
NYCE
Mexican standards and certification body.
ANCE
Mexican certification and testing association.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 175-5 E1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Radio Equipment and Systems (RES); Digital European Cordless Telecommunications (DECT) Common Interface Part 5: Network layer". This standard covers: ..
..
SIST ETS 300 175-5 E1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT); 35.100.30 - Network layer. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 175-5 E1:2003 is associated with the following European legislation: Standardization Mandates: T-176. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST ETS 300 175-5 E1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
5DGLMVNDRSUHPDLQVLVWHPL 5(6 ±'LJLWDOQHHYURSVNHEUH]YUYLþQH
WHOHNRPXQLNDFLMH '(&7 ±6NXSQLYPHVQLN±GHO 2PUHåQDSODVW
Radio Equipment and Systems (RES); Digital European Cordless Telecommunications
(DECT) Common Interface Part 5: Network layer
Ta slovenski standard je istoveten z: ETS 300 175-5 Edition 1
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
35.100.30 Omrežni sloj Network layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 175-5
TELECOMMUNICATION October 1992
STANDARD
Source: ETSI TC-RES Reference: DE/RES 3001-5
ICS: 33.060
DECT
Key words:
Radio Equipment and Systems (RES);
Digital European Cordless Telecommunications (DECT)
Common Interface
Part 5: Network layer
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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 1992. All rights reserved.
New presentation - see History box
Page 2
ETS 300 175-5: October 1992
Whilst 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.
Page 3
ETS 300 175-5: October 1992
Contents
Foreword.13
1 Scope .15
2 Normative references .15
3 Definitions, symbols and abbreviations .19
3.1 Network layer definitions.19
3.2 Network layer abbreviations.24
4 Overview of the network layer.27
5 Overview of procedures.29
5.1 General.29
5.2 Overview of Call Control (CC).29
5.2.1 General . 29
5.2.2 Call establishment .30
5.2.2.1 Call set-up .30
5.2.3 Call connect.30
5.2.4 Call information .31
5.2.5 Service change .31
5.2.6 Call release .31
5.3 Overview of supplementary services.31
5.3.1 General . 31
5.3.2 Keypad protocol. 32
5.3.3 Feature key management protocol.32
5.3.4 Functional protocol .32
5.4 Overview of Connection Oriented Message Service (COMS).33
5.4.1 General . 33
5.4.2 COMS establishment.33
5.4.3 Service negotiation.33
5.4.4 COMS connect .33
5.4.5 COMS data transfer. 34
5.4.6 COMS suspend and resume .34
5.4.7 COMS release. 34
5.5 Overview of ConnectionLess Message Service (CLMS).34
5.5.1 Fixed length message service.34
5.5.2 Variable length message service .35
5.6 Overview of Mobility Management (MM).35
5.6.1 General . 35
5.6.2 Identity procedures. 35
5.6.3 Authentication procedures.36
5.6.4 Location procedures.36
5.6.5 Access rights procedures. 36
5.6.6 Key allocation procedure.37
5.6.7 Parameter retrieval procedure. 37
5.6.8 Ciphering related procedure.37
5.7 Overview of Link Control Entity (LCE).37
5.7.1 General. 37
5.7.2 Data Link Endpoint Identifier (DLEI).37
5.7.3 Data link establishment .38
5.7.4 Data link re-establishment.38
5.7.5 Data link release .39
5.7.6 Data link suspend and resume. 39
Page 4
ETS 300 175-5: October 1992
5.7.7 Queuing of messages .39
5.7.8 Request paging .39
6 Message functional definitions .40
6.1 Overview of message structures .40
6.1.1 Messages.40
6.1.2 Information elements .40
6.2 Message summaries .41
6.2.1 Summary of CC messages.41
6.2.2 Summary of CISS messages.41
6.2.3 Summary of COMS messages .42
6.2.4 Summary of CLMS messages .42
6.2.5 Summary of MM messages.43
6.2.6 Summary of LCE messages.43
6.3 S-FORMAT message functional contents .44
6.3.1 S-FORMAT message overview .44
6.3.2 CC-messages.45
6.3.2.1 CC-SETUP.45
6.3.2.2 CC-INFOrmation.47
6.3.2.3 CC-SETUP-ACKnowledge.48
6.3.2.4 CC-CALL-PROCeeding.49
6.3.2.5 CC-ALERTING .50
6.3.2.6 CC-CONNECT.51
6.3.2.7 CC-CONNECT-ACKnowledge.51
6.3.2.8 CC-RELEASE .52
6.3.2.9 CC-RELEASE-COMplete .52
6.3.2.10 CC-SERVICE-CHANGE .53
6.3.2.11 CC-SERVICE-ACCEPT.53
6.3.2.12 CC-SERVICE-REJECT .54
6.3.2.13 CC-NOTIFY .54
6.3.2.14 IWU-INFOrmation .54
6.3.3 Supplementary services messages (call related and call independent).55
6.3.3.1 FACILITY.55
6.3.3.2 HOLD .55
6.3.3.3 HOLD-ACKnowledge .56
6.3.3.4 HOLD-REJECT .56
6.3.3.5 RETRIEVE.56
6.3.3.6 RETRIEVE-ACKnowledge .57
6.3.3.7 RETRIEVE-REJECT.57
6.3.3.8 CISS-REGISTER.57
6.3.3.9 CISS-RELEASE-COMplete .58
6.3.4 COMS-messages.58
6.3.4.1 COMS-SETUP .58
6.3.4.2 COMS-INFOrmation .59
6.3.4.3 COMS-ACKnowledge .59
6.3.4.4 COMS-CONNECT .59
6.3.4.5 COMS-RELEASE .60
6.3.4.6 COMS-RELEASE-COMplete.60
6.3.5 CLMS-message .61
6.3.5.1 CLMS-VARIABLE.61
6.3.6 MM-messages .62
6.3.6.1 ACCESS-RIGHTS-ACCEPT .62
6.3.6.2 ACCESS-RIGHTS-REJECT.62
6.3.6.3 ACCESS-RIGHTS-REQUEST.63
6.3.6.4 ACCESS-RIGHTS-TERMINATE-ACCEPT .63
6.3.6.5 ACCESS-RIGHTS-TERMINATE-REJECT.63
6.3.6.6 ACCESS-RIGHTS-TERMINATE-REQUEST.64
6.3.6.7 AUTHentication-REJECT .64
6.3.6.8 AUTHentication-REPLY.65
6.3.6.9 AUTHentication-REQUEST .66
Page 5
ETS 300 175-5: October 1992
6.3.6.10 CIPHER-REJECT .66
6.3.6.11 CIPHER-REQUEST .67
6.3.6.12 CIPHER-SUGGEST.67
6.3.6.13 DETACH.68
6.3.6.14 IDENTITY-REPLY.68
6.3.6.15 IDENTITY-REQUEST .69
6.3.6.16 KEY-ALLOCATE.69
6.3.6.17 LOCATE-ACCEPT.70
6.3.6.18 LOCATE-REJECT.70
6.3.6.19 LOCATE-REQUEST .71
6.3.6.20 MM-INFO-ACCEPT .71
6.3.6.21 MM-INFO-REJECT.72
6.3.6.22 MM-INFO-REQUEST.72
6.3.6.23 MM-INFO-SUGGEST .73
6.3.6.24 TEMPORARY-IDENTITY-ASSIGN .73
6.3.6.25 TEMPORARY-IDENTITY-ASSIGN-ACKnowledge.74
6.3.6.26 TEMPORARY-IDENTITY-ASSIGN-REJect.74
6.3.7 LCE-messages .74
6.3.7.1 LCE-PAGE-RESPONSE .74
6.3.7.2 LCE-PAGE-REJECT.75
6.4 B-FORMAT message functional contents.75
6.4.1 B-FORMAT message overview .75
6.4.2 LCE-REQUEST-PAGE .76
6.4.3 CLMS-FIXED.76
7 S-FORMAT message structures.77
7.1 Overview.77
7.2 Protocol Discrimination (PD) element.77
7.3 Transaction Identifier (TI) element .78
7.4 Message type element .79
7.4.1 Messages for Call Control (CC). 79
7.4.2 Messages for Supplementary Services (SS).79
7.4.3 Messages for Connection Oriented Message Service (COMS) .80
7.4.4 Messages for ConnectionLess Message Service .80
7.4.5 Messages for Mobility Management (MM) .80
7.4.6 Messages for Link Control Entity .81
7.5 Other information elements.81
7.5.1 Coding rules.81
7.5.2 Extensions of codesets.83
7.5.3 Locking shift procedure.83
7.5.4 Non-locking shift procedure.83
7.5.5 Display and keypad elements.84
7.5.6 Repeated elements .84
7.6 Fixed length information elements.85
7.6.1 Summary.85
7.6.2 Sending complete and delimiter request .85
7.6.3 Repeat indicator.85
7.6.4 Basic service .86
7.6.5 Single display.86
7.6.6 Single keypad .87
7.6.7 Release reason.87
7.6.8 Signal.88
7.6.9 Timer restart.89
7.6.10 Test hook control . 89
7.7 Variable length information elements.89
7.7.1 Summary.89
7.7.2 Allocation type .91
7.7.3 Alphanumeric .91
7.7.4 Auth type.92
7.7.5 Call attributes.94
Page 6
ETS 300 175-5: October 1992
7.7.6 Call identity .96
7.7.7 Called party number .96
7.7.8 Called party subaddress .97
7.7.9 Calling party number.98
7.7.10 Cipher info .99
7.7.11 Connection attributes .100
7.7.12 Connection identity .102
7.7.13 Duration.103
7.7.14 End-to-end compatibility.104
7.7.15 Facility. 107
7.7.16 Feature activate . 107
7.7.17 Feature indicate .109
7.7.18 Fixed identity.112
7.7.19 Identity type.113
7.7.20 Info type.114
7.7.21 InterWorking Unit (IWU) attributes .115
7.7.22 IWU packet. 118
7.7.23 IWU to IWU . 119
7.7.24 Key . 121
7.7.25 Location area. 121
7.7.26 Multi-display. 122
7.7.27 Multi-keypad . 123
7.7.28 NetWorK (NWK) assigned identity .123
7.7.29 Network parameter.124
7.7.30 Portable identity . 125
7.7.31 Progress indicator . 129
7.7.32 Rand . 129
7.7.33 Rate parameters .130
7.7.34 Reject reason. 131
7.7.35 RES . 132
7.7.36 RS . 132
7.7.37 Segmented info .132
7.7.38 Service change info .133
7.7.39 Service class.134
7.7.40 Set-up capability. 134
7.7.41 Terminal capability.135
7.7.42 Transit delay . 137
7.7.43 Window size.137
7.7.44 ZAP field.137
8 B-FORMAT message structures.138
8.1 General .138
8.2 LCE request paging messages.138
8.2.1 Short format message . 139
8.2.2 Long format message.140
8.3 CLMS-FIXED messages.141
8.3.1 General message structure .141
8.3.2 Message elements .142
8.3.3 Standard message structures.143
8.3.3.1 General.143
8.3.3.3 Messages using 8-bit characters.144
9 Call Control (CC) procedures . 144
9.1 General .144
9.2 Call Control (CC) states.147
9.2.1 States at PT .147
9.2.1.1 State T-00: "NULL" .147
9.2.1.2 State T-19: "RELEASE PENDING". 147
9.2.1.3 State T-10: "ACTIVE" . 147
9.2.1.4 State T-01: "CALL INITIATED" . 147
Page 7
ETS 300 175-5: October 1992
9.2.1.5 State T-02: "OVERLAP SENDING". 147
9.2.1.6 State T-03: "CALL PROCEEDING". 147
9.2.1.7 State T-04: "CALL DELIVERED" . 147
9.2.1.8 State T-06: "CALL PRESENT". 147
9.2.1.9 State T-07: "CALL RECEIVED" . 147
9.2.1.10 State T-08: "CONNECT PENDING". 147
9.2.2 States at FT . 147
9.2.2.1 State F-00: "NULL". 147
9.2.2.2 State F-19: "RELEASE PENDING" . 148
9.2.2.3 State F-10: "ACTIVE" . 148
9.2.2.4 State F-01: "CALL-INITIATED". 148
9.2.2.5 State F-02: "OVERLAP SENDING". 148
9.2.2.6 State F-03: "CALL PROCEEDING". 148
9.2.2.7 State F-04: "CALL DELIVERED" . 148
9.2.2.8 State F-06: "CALL PRESENT". 148
9.2.2.9 State F-07: "CALL RECEIVED" . 148
9.2.3 Optional states (PT and FT). 148
9.2.3.1 States T-22 and F-22: "OVERLAP RECEIVING". 148
9.2.3.2 States T-23 and F-23: "INCOMING CALL PROCEEDING"148
9.3 Call establishment procedures. 149
9.3.1 PT initiated call establishment (outgoing call). 149
9.3.1.1 Call request. 149
9.3.1.2 Call accept or reject. 150
9.3.1.3 Selection of lower layer resources . 150
9.3.1.4 Connection of U-plane. 151
9.3.1.5 Overlap sending . 151
9.3.1.6 Call proceeding . 152
9.3.1.7 Call confirmation. 153
9.3.1.8 Call connection . 153
9.3.1.9 Expiry of timer . 153
9.3.2 FT initiated call establishment (incoming call). 153
9.3.2.1 Call request. 153
9.3.2.2 Call accept or reject. 154
9.3.2.3 Selection of lower layer resources . 155
9.3.2.4 Connection of U-plane. 155
9.3.2.5 Overlap receiving. 155
9.3.2.6 Call proceeding . 155
9.3.2.7 Call confirmation. 156
9.3.2.8 Call connection . 156
9.3.2.9 Sending of <>. 156
9.3.2.10 Expiry of timer . 156
9.4 Call information procedures. 156
9.5 Call release procedures. 157
9.5.1 Normal call release. 157
9.5.2 Abnormal call release . 157
9.5.3 Release collisions. 158
9.6 Service change procedures. 158
9.6.1 General . 158
9.6.2 Bandwidth changes (including reversals) . 159
9.6.3 Service rerouting . 159
9.6.4 Service suspension and resumption . 159
9.7 Packet mode procedures. 159
9.7.1 General . 159
9.7.2 PT initiated access. 160
9.7.3 FT initiated access . 160
9.7.4 Packet mode suspend and resume . 160
9.7.4.1 General . 160
9.7.4.2 C-plane suspend and resume . 161
9.7.4.3 U-plane suspend and resume. 161
Page 8
ETS 300 175-5: October 1992
10 Supplementary Services procedures.161
10.1 General .161
10.2 Keypad protocol.162
10.3 Feature key management protocol.162
10.4 Functional protocol .163
10.4.1 Separate messages category.163
10.4.1.1 Hold procedures .163
10.4.1.2 Retrieve procedures.163
10.4.1.3 Auxiliary states for hold and retrieve.164
10.4.2 Common information element category.164
10.4.2.1 Call related procedures . 164
10.4.2.2 Call independent procedures.164
10.5 Co-existence of multiple protocols .164
10.6 Application protocols .165
10.6.1 DECT standard functional supplementary services .165
10.6.2 DECT specific supplementary services.166
10.6.2.1 Queue management.166
10.6.2.2 Indication of subscriber number.166
10.6.2.3 Control of echo control functions .167
10.6.2.4 Cost information .167
11 Connection Oriented Message Service (COMS) .168
11.1 General .168
11.2 COMS states.168
11.2.1 States at PT .168
11.2.1.1 State TS-0: "NULL".168
11.2.1.2 State TS-1: "CONNECT PENDING" .168
11.2.1.3 State TS-2: "RELEASE PENDING" .168
11.2.1.4 State TS-3: "ACTIVE" .168
11.2.2 States at FT.168
11.2.2.1 State FS-0: NULL .168
11.2.2.2 State FS-1: "CONNECT PENDING" .168
11.2.2.3 State FS-2: "RELEASE PENDING" .168
11.2.2.4 State FS-3: "ACTIVE" .169
11.3 COMS establishment procedures .169
11.3.1 PT initiated COMS establishment.169
11.3.1.1 COMS request . 169
11.3.1.2 COMS connection.169
11.3.2 FT initiated COMS establishment.170
11.3.2.1 COMS request . 170
11.3.2.2 COMS connection.170
11.4 COMS data transfer procedures .170
11.4.1 Procedure at the sending side .170
11.4.2 Procedure at the receiving side. 171
11.5 COMS suspend and resume procedures.172
11.6 COMS release procedures .172
11.6.1 Normal COMS release. 172
11.6.2 Release collisions.172
12 ConnectionLess Message Service (CLMS).173
12.1 General .173
12.2 CLMS states.173
12.3 CLMS message transmission procedures.173
12.3.1 Fixed length messages .173
12.3.1.1 Procedure in the Fixed radio Termination (FT).173
12.3.1.2 Procedure in the Portable radio Termination (PT) .174
12.3.2 Variable length messages .174
12.3.2.1 Procedure at the sending side.174
12.3.2.2 Procedure at the receiving side.174
12.3.2.3 Restrictions for portable side initiated messages.175
Page 9
ETS 300 175-5: October 1992
13 Mobility Management (MM) procedures . 175
13.1 General. 175
13.2 Identity procedures . 176
13.2.1 Procedure for identification of PT. 176
13.2.2 Procedure for temporary identity assignment. 176
13.3 Authentication procedures. 178
13.3.1 Authentication of a PT. 178
13.3.2 Authentication of the user. 179
13.3.3 Authentication of a FT. 180
13.4 Location procedures. 181
13.4.1 Location registration. 181
13.4.2 Detach . 182
13.4.3 Location update . 182
13.5 Access rights procedure. 183
13.5.1 Obtaining the access rights. 183
13.5.2 Termination of access rights. 184
13.6 Key allocation procedure . 185
13.7 Parameter retrieval procedure. 186
13.8 Ciphering related procedure. 188
14 Link Control Entity (LCE) procedures. 190
14.1 General. 190
14.2 Connection oriented link control procedures. 191
14.2.1 Link establishment. 191
14.2.2 Direct PT initiated link establishment . 192
14.2.3 Indirect (paged) FT initiated link establishment. 192
14.2.4 Direct FT initiated link establishment (optional). 194
14.2.5 Link maintenance. 194
14.2.6 Link suspend and resume. 194
14.2.6.1 Link suspend. 195
14.2.6.2 Link resume . 195
14.2.7 Link release. 195
14.3 Connectionless link control procedures. 196
14.3.1 Message routing . 196
14.3.2 Broadcast announce procedure. 197
15 Management procedures . 197
15.1 Lower Layer Management Entity (LLME). 197
15.2 Service mapping and negotiation . 198
15.2.1 General . 198
15.2.2 Prioritised list negotiation . 198
15.2.3 Exchanged attribute negotiation. 198
15.2.4 Operating parameter negotiation . 199
15.3 Service modification procedures. 199
15.4 Resource management. 199
15.5 Management of MM procedures. 199
15.6 Call ciphering management . 200
15.7 External handover management. 201
15.7.1 General . 201
15.7.2 External handover procedure. 201
15.8 Test management procedures. 202
15.8.1 Test call back procedure. 202
15.8.2 Test hook control procedures. 202
15.8.3 Upper tester procedure. 203
16 Primitives. 203
16.1 Primitive types . 203
16.2 Primitives to lower layer (DLC layer). 204
16.3 Primitives to higher entity (IWU) . 204
16.3.1 Parameter definitions. 204
Page 10
ETS 300 175-5: October 1992
16.3.2 MNCC primitives.204
16.3.2.1 MNCC-SETUP primitive.205
16.3.2.2 MNCC-SETUP-ACK primitive.205
16.3.2.3 MNCC-REJECT primitive.206
16.3.2.4 MNCC-CALL-PROC primitive.206
16.3.2.5 MNCC-ALERT primitive.206
16.3.2.6 MNCC-CONNECT primitive.207
16.3.2.7 MNCC-RELEASE primitive .207
16.3.2.8 MNCC-FACILITY primitive.207
16.3.2.9 MNCC-INFO primitive.208
16.3.2.10 MNCC-MODIFY primitive . 208
16.3.2.11 MNCC-HOLD primitive .208
16.3.2.12 MNCC-RETRIEVE primitive .209
16.3.2.13 MNCC-IWU-INFO primitive.
...