SIST ETS 300 175-5 E2:2003
(Main)Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network (NWK) layer
- Abstract
To update ETS 300 175 based upon experiences from the development of TBR 6 & 10 and comments received.
- 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
SIST ETS 300 175-5 E2:2003 is the SIST adoption of ETS 300 175-5 Edition 2 for Digital Enhanced Cordless Telecommunications (DECT) Common Interface, Part 5: the Network (NWK) layer. It specifies the DECT NWK control plane between portable and fixed terminations, including call control, supplementary services, connection-oriented and connectionless message services, mobility management, and link control. Engineers, quality teams, and test labs use it to implement and verify DECT layer 3 message coding and procedures.
What does SIST ETS 300 175-5 E2:2003 specify?
SIST ETS 300 175-5 E2:2003 specifies the C-plane of the DECT NWK layer. It does not specify the U-plane, because the U-plane is null for all services at the DECT NWK layer.
The document organizes the NWK layer into functional entities and then describes their messages, structures, procedures, primitives, and error handling.
| Annex | What it covers |
|---|---|
| Annex A | System parameters, including timers, constants, and restart behavior |
| Annex B | Call Control (CC) state transition tables |
| Annex D | DECT standard 8-bit and 4-bit character coding |
| Annex E | Default coding of <> and <> for basic speech |
| Annex F | Broadcast attributes coding |
| Annex G | Use of <> and <> information elements |
| Annex H | Nested procedures and stand-alone procedures |
The main clauses cover scope, normative references, definitions and abbreviations, an overview of the NWK layer, message definitions and formats, detailed procedures for CC, Supplementary Services (SS), Connection Oriented Message Service (COMS), ConnectionLess Message Service (CLMS), Mobility Management (MM), Link Control Entity (LCE), management procedures, primitives, and error handling.
What are the key requirements of SIST ETS 300 175-5 E2:2003?
SIST ETS 300 175-5 E2:2003 defines how the DECT NWK layer carries control information, how its procedures run, and how messages are coded and interpreted. In practice, this is the part that tells implementers what to send, when to send it, and how to react when the peer responds.
The NWK layer is split into named entities
Clause 4 groups the NWK layer into LCE, CC, CISS, COMS, CLMS, and MM. Each entity has its own role, but all of them share the same DECT C-plane foundation and interface to the Lower Layer Management Entity (LLME).
For implementers, this means the software cannot treat the NWK layer as one undifferentiated message pipe. It has to route each message to the right entity and keep each transaction separate.
S-FORMAT messages have a fixed structure
Clause 7 defines S-FORMAT messages as a combination of Protocol Discriminator (PD), Transaction Identifier (TI), Message Type, and information elements. The PD identifies the entity, and the TI distinguishes parallel transactions for one Portable Termination (PT).
This matters because parsers and conformance tests must check the structure before they check the service meaning. The same transaction value can be used by different protocol entities at the same time, so the PD and TI have to be interpreted together.
B-FORMAT messages are fixed-length broadcast messages
Clause 8 defines B-FORMAT messages for LCE request paging and CLMS-FIXED messages. They are fixed length and are sent through the broadcast service, which makes them suitable for paging and other broadcast-oriented control.
In practice, this means paging and fixed broadcast messaging have a separate coding model from the normal S-FORMAT control messages. Equipment has to handle the short, long, and extended layouts and apply the default values defined for request paging when fields are omitted.
Call Control supports call setup, in-call changes, and release
Clause 9 states that Call Control (CC) supports circuit oriented and packet oriented services, but it always establishes circuit oriented lower resources. It covers call setup, call connect, call information, service change, packet mode, and call release.
The PT and FT each have defined CC states, including active, call initiated, call proceeding, call delivered, call present, and connect pending. For a product team, this means call handling is state driven and must respond correctly to both outgoing and incoming call flows.
Supplementary Services use three generic protocols
Clause 10 defines three ways to invoke supplementary services: keypad protocol, feature key management protocol, and functional protocol. The keypad protocol uses <> and <> elements, while the functional protocol uses either separate hold/retrieve messages or the <> information element.
The document says the functional protocol is the preferred method when there is a choice. That matters because products should support more than one invocation method where the profile expects it, but they should also converge on the functional path where possible.
COMS and CLMS serve different message services
Clause 11 defines COMS as the connection oriented message service for packet switched connections. It requires a reliable C-plane DLC link before use, and it includes establishment, data transfer, suspend/resume, and release.
Clause 12 defines CLMS as a connectionless message service for point-to-point or point-to-multipoint transfer. It supports fixed length messages on the broadcast service and variable length messages on LAPC services, with messages handled sequentially and independently.
In practice, this means COMS is for session-like packet exchange, while CLMS is for one-off control messages. Implementers need to keep the two service models separate.
Mobility Management controls identity, location, access, and ciphering
Clause 13 groups MM into identity, authentication, location, access rights, key allocation, parameter retrieval, and ciphering-related procedures. Each MM procedure is a separate transaction with a single TI, and the initiator assigns that TI.
This is important for interoperability and security. The same clause also explains that MM handles PT identity, temporary identity assignment, location registration, detach, and location update, so portable part movement has to be reflected in the signaling state.
LCE provides link control and routing
Clause 14 makes LCE the lowest entity in the NWK layer and the routing point for all higher-entity messages. It controls link establishment, maintenance, suspend/resume, release, message routing, message paging, and collective or group ringing.
For implementations, LCE is the place where message delivery rules meet actual link availability. It also depends on local routing data linking IPUI and TPUI, so systems must manage those associations consistently.
Management, primitives, and errors complete the behavior model
Clause 15 covers service mapping and negotiation, resource management, MM procedure management, call ciphering management, external handover, and test management. Clause 16 defines the primitives to lower layers and to the interworking unit. Clause 17 defines protocol error handling, including short messages, transaction identifier errors, message sequence errors, information element errors, data link reset, and data link failure.
This part matters during integration and test because it tells the implementation how to behave under mismatch, overload, reset, or malformed input conditions. Annex A and Annex B then give the timers, constants, and CC state transitions needed to make those procedures executable.
What terms does SIST ETS 300 175-5 E2:2003 define?
- Portable Termination (PT) - the portable part of the DECT system that initiates and receives network procedures.
- Fixed Termination (FT) - the fixed side of the DECT system that interacts with the portable part over the radio interface.
- Call Control (CC) - the NWK entity that manages call establishment, maintenance, and release.
- Connection Oriented Message Service (COMS) - the packet service for connection-based message transfer.
- ConnectionLess Message Service (CLMS) - the packet service for connectionless message transfer.
- Mobility Management (MM) - the entity that manages identities, authentication, location, access rights, key allocation, and ciphering-related procedures.
- Link Control Entity (LCE) - the lowest NWK entity, responsible for link control and message routing.
- Call Independent Supplementary Services (CISS) - supplementary services that operate outside any CC call.
Who uses SIST ETS 300 175-5 E2:2003?
SIST ETS 300 175-5 E2:2003 is used by DECT equipment designers, protocol developers, test laboratories, and quality or conformity teams that work on cordless telephony and related radio systems. It is also relevant to buyers and integrators who need to confirm that a DECT product supports the required NWK-layer signaling, paging, mobility, and supplementary-service behavior.
What changed in SIST ETS 300 175-5 E2:2003 from the previous edition?
SIST ETS 300 175-5 E2:2003 updates ETS 300 175 based on experience from the development of TBR 6 and TBR 10 and on comments received.
Which standards are used with SIST ETS 300 175-5 E2:2003?
SIST ETS 300 175-5 E2:2003 relies on the other DECT Common Interface parts, especially ETS 300 175-1, ETS 300 175-2, ETS 300 175-3, ETS 300 175-4, ETS 300 175-6, and ETS 300 175-8. These parts provide the overview, physical and lower-layer context, U-plane coding, and related DECT mechanisms that this NWK part builds on.
It also uses ETS 300 102-1 for the general message-coding principles behind S-FORMAT messages, and prI-ETS 300 022 for similar coding modifications. For character sets, data rates, and interworking coding, the document refers to standards and recommendations such as ISO Publication 2022, ISO Publication 1745, CCITT Recommendations T.50, V.110, X.30, Q.921/I.441, X.25, and V.42.
What does the SIST ETS 300 175-5 E2:2003 document contain?
The document contains the NWK layer overview, entity-by-entity message definitions, detailed procedure descriptions, and the coding rules for the messages and information elements. It includes protocol discriminator coding, transaction identifier rules, message type tables, fixed and variable length information elements, and special codings for items such as release reason, cipher info, service change info, and terminal capability.
It also gives detailed state models for CC, COMS, and related procedures, plus the primitives that connect the NWK layer to lower layers and to the interworking unit. For test and conformance work, the annexes supply timers, constants, state transition tables, default attribute codings, broadcast attribute codings, and the handling of nested and stand-alone procedures.
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 E2:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network (NWK) layer". This standard covers: To update ETS 300 175 based upon experiences from the development of TBR 6 & 10 and comments received.
To update ETS 300 175 based upon experiences from the development of TBR 6 & 10 and comments received.
SIST ETS 300 175-5 E2: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 E2: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
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH '(&7 ±6NXSQLYPHVQLN &, ±
GHO 2PUHåQDSODVW 1:.
Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5:
Network (NWK) layer
Ta slovenski standard je istoveten z: ETS 300 175-5 Edition 2
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 September 1996
STANDARD Second Edition
Source: ETSI TC-RES Reference: RE/RES-03027-5
ICS: 33.060.50
Key words: DECT, radio
Radio Equipment and Systems (RES);
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI);
Part 5: Network (NWK) layer
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
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 1996. All rights reserved.
Page 2
ETS 300 175-5: September 1996
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: September 1996
Contents
Foreword .15
1 Scope.17
2 Normative references.17
3 Definitions and abbreviations .21
3.1 Definitions.21
3.2 Abbreviations .23
4 Overview of the NWK layer .25
5 Overview of procedures .26
5.1 General .26
5.2 Overview of Call Control (CC) .27
5.2.1 General .27
5.2.2 Call establishment.27
5.2.2.1 Call set-up.27
5.2.2.2 Service negotiation.28
5.2.3 Call connect .29
5.2.4 Call information.29
5.2.5 Service change.29
5.2.6 Call release.29
5.3 Overview of Supplementary Services (SS) .29
5.3.1 General .29
5.3.2 Keypad protocol.30
5.3.3 Feature key management protocol.30
5.3.4 Functional protocol.30
5.4 Overview of Connection Oriented Message Service (COMS).31
5.4.1 General .31
5.4.2 COMS establishment.31
5.4.3 Service negotiation .31
5.4.4 COMS connect.32
5.4.5 COMS data transfer .32
5.4.6 COMS suspend and resume.32
5.4.7 COMS release .32
5.5 Overview of ConnectionLess Message Service (CLMS) .32
5.5.1 Fixed length message service.32
5.5.2 Variable length message service.33
5.6 Overview of Mobility Management (MM) .33
5.6.1 General .33
5.6.2 Identity procedures.33
5.6.3 Authentication procedures .34
5.6.4 Location procedures .34
5.6.5 Access rights procedures.34
5.6.6 Key allocation procedure.35
5.6.7 Parameter retrieval procedure .35
5.6.8 Ciphering related procedure .35
5.7 Overview of Link Control Entity (LCE) .35
5.7.1 General .35
5.7.2 Data Link Endpoint Identifier (DLEI) .36
5.7.3 Data link establishment .36
5.7.4 Data link re-establishment .37
5.7.5 Data link release.37
Page 4
ETS 300 175-5: September 1996
5.7.6 Data link suspend and resume .37
5.7.7 Queuing of messages .37
5.7.8 Request paging .37
6 Message functional definitions.38
6.1 Overview of message structures.38
6.1.1 Messages .38
6.1.2 Information elements.38
6.2 Message summaries.39
6.2.1 Summary of CC messages.39
6.2.2 Summary of CISS messages.39
6.2.3 Summary of COMS messages.40
6.2.4 Summary of CLMS messages .40
6.2.5 Summary of MM messages.41
6.2.6 Summary of LCE messages .41
6.3 S-FORMAT message functional contents .42
6.3.1 S-FORMAT message overview.42
6.3.2 CC-messages .43
6.3.2.1 {CC-SETUP}.43
6.3.2.2 {CC-INFO}.45
6.3.2.3 {CC-SETUP-ACK}.46
6.3.2.4 {CC-CALL-PROC}.47
6.3.2.5 {CC-ALERTING}.48
6.3.2.6 {CC-CONNECT}.49
6.3.2.7 {CC-CONNECT-ACK}.50
6.3.2.8 {CC-RELEASE} .50
6.3.2.9 {CC-RELEASE-COM} .51
6.3.2.10 {CC-SERVICE-CHANGE} .52
6.3.2.11 {CC-SERVICE-ACCEPT}.52
6.3.2.12 {CC-SERVICE-REJECT} .53
6.3.2.13 {CC-NOTIFY} .53
6.3.2.14 {IWU-INFO}.54
6.3.3 SS-messages (call related and call independent).55
6.3.3.1 {FACILITY}.55
6.3.3.2 {HOLD} .55
6.3.3.3 {HOLD-ACK} .56
6.3.3.4 {HOLD-REJECT} .56
6.3.3.5 {RETRIEVE}.57
6.3.3.6 {RETRIEVE-ACK}.57
6.3.3.7 {RETRIEVE-REJECT}.58
6.3.3.8 {CISS-REGISTER}.58
6.3.3.9 {CISS-RELEASE-COM} .59
6.3.4 COMS-messages.59
6.3.4.1 {COMS-SETUP} .59
6.3.4.2 {COMS-INFO} .60
6.3.4.3 {COMS-ACK} .60
6.3.4.4 {COMS-CONNECT} .61
6.3.4.5 {COMS-RELEASE} .61
6.3.4.6 {COMS-RELEASE-COM} .62
6.3.4.7 {COMS-NOTIFY}.62
6.3.5 CLMS-message.63
6.3.5.1 {CLMS-VARIABLE}.63
6.3.6 MM-messages .64
6.3.6.1 {ACCESS-RIGHTS-ACCEPT}.64
6.3.6.2 {ACCESS-RIGHTS-REJECT}.64
6.3.6.3 {ACCESS-RIGHTS-REQUEST}.65
6.3.6.4 {ACCESS-RIGHTS-TERMINATE-ACCEPT}.65
6.3.6.5 {ACCESS-RIGHTS-TERMINATE-REJECT}.66
6.3.6.6 {ACCESS-RIGHTS-TERMINATE-REQUEST}.66
6.3.6.7 {AUTHENTICATION-REJECT} .67
Page 5
ETS 300 175-5: September 1996
6.3.6.8 {AUTHENTICATION-REPLY}.67
6.3.6.9 {AUTHENTICATION-REQUEST}.68
6.3.6.10 {CIPHER-REJECT}.68
6.3.6.11 {CIPHER-REQUEST}.69
6.3.6.12 {CIPHER-SUGGEST}.69
6.3.6.13 {DETACH}.70
6.3.6.14 {IDENTITY-REPLY}.70
6.3.6.15 {IDENTITY-REQUEST} .71
6.3.6.16 {KEY-ALLOCATE} .71
6.3.6.17 {LOCATE-ACCEPT}.72
6.3.6.18 {LOCATE-REJECT}.72
6.3.6.19 {LOCATE-REQUEST}.73
6.3.6.20 {MM-INFO-ACCEPT} .73
6.3.6.21 {MM-INFO-REJECT}.74
6.3.6.22 {MM-INFO-REQUEST}.74
6.3.6.23 {MM-INFO-SUGGEST} .75
6.3.6.24 {TEMPORARY-IDENTITY-ASSIGN} .75
6.3.6.25 {TEMPORARY-IDENTITY-ASSIGN-ACK}.76
6.3.6.26 {TEMPORARY-IDENTITY-ASSIGN-REJ}.76
6.3.7 LCE-messages.77
6.3.7.1 {LCE-PAGE-RESPONSE} .77
6.3.7.2 {LCE-PAGE-REJECT}.77
6.4 B-FORMAT message functional contents .77
6.4.1 B-FORMAT message overview.77
6.4.2 {LCE-REQUEST-PAGE} .78
6.4.3 {CLMS-FIXED}.79
7 S-FORMAT message structures.79
7.1 Overview .79
7.2 Protocol Discrimination (PD) element .80
7.3 Transaction Identifier (TI) element .80
7.4 Message type element.81
7.4.1 Messages for CC .82
7.4.2 Messages for SS.82
7.4.3 Messages for COMS.82
7.4.4 Messages for CLMS.82
7.4.5 Messages for MM .83
7.4.6 Messages for LCE.83
7.5 Other information elements .83
7.5.1 Coding rules.83
7.5.2 Extensions of codesets .85
7.5.3 Locking shift procedure.86
7.5.4 Non-locking shift procedure .86
7.5.5 Display and keypad elements .87
7.5.6 Repeated elements.87
7.6 Fixed length information elements .88
7.6.1 Summary .88
7.6.2 Sending complete and delimiter request .88
7.6.3 Repeat indicator.88
7.6.4 Basic service.89
7.6.5 Single display.89
7.6.6 Single keypad.90
7.6.7 Release reason.90
7.6.8 Signal .91
7.6.9 Timer restart.92
7.6.10 Test hook control.92
7.7 Variable length information elements .93
7.7.1 Summary .93
7.7.2 Allocation type.94
7.7.3 Alphanumeric.94
Page 6
ETS 300 175-5: September 1996
7.7.4 Auth type .96
7.7.5 Call attributes.97
7.7.6 Call identity .99
7.7.7 Called party number.100
7.7.8 Called party subaddress.101
7.7.9 Calling party number .102
7.7.10 Cipher info.103
7.7.11 Connection attributes .104
7.7.12 Connection identity.106
7.7.13 Duration.107
7.7.14 End-to-end compatibility.108
7.7.15 Facility.111
7.7.16 Feature activate.111
7.7.17 Feature indicate.114
7.7.18 Fixed identity.116
7.7.19 Identity type .117
7.7.20 Info type .118
7.7.21 InterWorking Unit (IWU) attributes.119
7.7.22 IWU packet .124
7.7.23 IWU to IWU.125
7.7.24 Key.127
7.7.25 Location area .128
7.7.26 Multi-display.129
7.7.27 Multi-keypad.129
7.7.28 NetWorK (NWK) assigned identity.129
7.7.29 Network parameter.130
7.7.30 Portable identity.131
7.7.31 Progress indicator.135
7.7.32 Rand.136
7.7.33 Rate parameters .136
7.7.34 Reject reason.138
7.7.35 RES.139
7.7.36 RS.139
7.7.37 Segmented info .140
7.7.38 Service change info.140
7.7.39 Service class.142
7.7.40 Set-up capability.142
7.7.41 Terminal capability.143
7.7.42 Transit delay .147
7.7.43 Window size.147
7.7.44 ZAP field.148
7.7.45 Escape to proprietary .148
7.7.46 Model identifier.149
7.7.47 MMS Generic Header .149
7.7.48 MMS Object Header.149
7.7.49 MMS Extended header.150
7.7.50 Time-Date.150
7.7.51 Ext h/o indicator.151
8 B-FORMAT message structures .152
8.1 General .152
8.2 LCE request paging messages.152
8.2.1 Short format message.154
8.2.2 Long format message .156
8.3 CLMS-FIXED messages.158
8.3.1 General message structure .158
8.3.2 Message elements.159
8.3.3 Standard message structures .160
8.3.3.1 General.160
8.3.3.2 Messages using 4-bit characters.160
Page 7
ETS 300 175-5: September 1996
8.3.3.3 Messages using 8-bit characters. 161
9 Call Control (CC) procedures. 161
9.1 General . 161
9.2 Call Control (CC) states. 164
9.2.1 States at PT. 164
9.2.1.1 State T-00: "NULL" . 164
9.2.1.2 State T-19: "RELEASE PENDING". 164
9.2.1.3 State T-10: "ACTIVE". 164
9.2.1.4 State T-01: "CALL INITIATED" . 164
9.2.1.5 State T-02: "OVERLAP SENDING" . 164
9.2.1.6 State T-03: "CALL PROCEEDING" . 164
9.2.1.7 State T-04: "CALL DELIVERED". 164
9.2.1.8 State T-06: "CALL PRESENT". 164
9.2.1.9 State T-07: "CALL RECEIVED". 164
9.2.1.10 State T-08: "CONNECT PENDING". 164
9.2.2 States at FT. 164
9.2.2.1 State F-00: "NULL" . 164
9.2.2.2 State F-19: "RELEASE PENDING". 165
9.2.2.3 State F-10: "ACTIVE". 165
9.2.2.4 State F-01: "CALL-INITIATED" . 165
9.2.2.5 State F-02: "OVERLAP SENDING" . 165
9.2.2.6 State F-03: "CALL PROCEEDING" . 165
9.2.2.7 State F-04: "CALL DELIVERED". 165
9.2.2.8 State F-06: "CALL PRESENT". 165
9.2.2.9 State F-07: "CALL RECEIVED". 165
9.2.3 Optional states (PT and FT). 166
9.2.3.1 States T-22 and F-22: "OVERLAP RECEIVING" . 166
9.2.3.2 States T-23 and F-23: "INCOMING CALL PROCEEDING"166
9.3 Call establishment procedures. 166
9.3.1 PT initiated call establishment (outgoing call) . 166
9.3.1.1 Call request. 166
9.3.1.2 Call accept or reject. 167
9.3.1.3 Selection of lower layer resources. 168
9.3.1.4 Connection of U-plane . 169
9.3.1.5 Overlap sending. 169
9.3.1.6 Call proceeding. 170
9.3.1.7 Call confirmation . 170
9.3.1.8 Call connection . 171
9.3.1.9 Expiry of timer . 171
9.3.2 FT initiated call establishment (incoming call) . 171
9.3.2.1 Call request. 171
9.3.2.2 Call accept or reject. 171
9.3.2.3 Selection of lower layer resources. 172
9.3.2.4 Connection of U-plane . 173
9.3.2.5 Overlap receiving. 173
9.3.2.6 Call proceeding. 173
9.3.2.7 Call confirmation . 173
9.3.2.8 Call connection . 174
9.3.2.9 Sending of <> . 174
9.3.2.10 Expiry of timer . 174
9.4 Call information procedures. 174
9.5 Call release procedures . 174
9.5.1 Normal call release. 174
9.5.2 Abnormal call release. 175
9.5.3 Release collisions. 176
9.6 Service change procedures. 176
9.6.1 General . 176
9.6.2 Bandwidth changes (including reversals). 177
9.6.3 Service rerouting . 177
Page 8
ETS 300 175-5: September 1996
9.6.4 Service suspension and resumption.177
9.7 Packet mode procedures .178
9.7.1 General.178
9.7.2 PT initiated access.178
9.7.3 FT initiated access.178
9.7.4 Packet mode suspend and resume.179
9.7.4.1 General.179
9.7.4.2 C-plane suspend and resume.179
9.7.4.3 U-plane suspend and resume.179
10 Supplementary Services procedures .180
10.1 General .180
10.2 Keypad protocol.180
10.3 Feature key management protocol.181
10.4 Functional protocol.181
10.4.1 Separate messages approach.181
10.4.1.1 Hold procedures.181
10.4.1.2 Retrieve procedures.182
10.4.1.3 Auxiliary states for hold and retrieve .182
10.4.2 Common information element approach.182
10.4.2.1 Call related procedures .182
10.4.2.2 Call independent procedures.183
10.4.2.3. Connectionless Supplementary Service (CLSS) procedure183
10.5 Co-existence of multiple protocols.184
10.6 Application protocols.184
10.6.1 DECT standard functional supplementary services.184
10.6.2 DECT specific supplementary services .185
10.6.2.1 Queue management.185
10.6.2.2 Indication of subscriber number.186
10.6.2.3 Control of echo control functions.186
10.6.2.4 Cost information.186
11 Connection Oriented Message Service (COMS).187
11.1 General .187
11.2 COMS states .187
11.2.1 States at PT.187
11.2.1.1 State TS-0: "NULL" .187
11.2.1.2 State TS-1: "CONNECT PENDING".187
11.2.1.3 State TS-2: "RELEASE PENDING".187
11.2.1.4 State TS-3: "ACTIVE" .187
11.2.2 States at FT.188
11.2.2.1 State FS-0: “NULL” .188
11.2.2.2 State FS-1: "CONNECT PENDING".188
11.2.2.3 State FS-2: "RELEASE PENDING".188
11.2.2.4 State FS-3: "ACTIVE" .188
11.3 COMS establishment procedures.188
11.3.1 PT initiated COMS establishment.188
11.3.1.1 COMS request.188
11.3.1.2 COMS connection.189
11.3.2 FT initiated COMS establishment.189
11.3.2.1 COMS request.189
11.3.2.2 COMS connection.189
11.4 COMS data transfer procedures.190
11.4.1 Procedure at the sending side.190
11.4.2 Procedure at the receiving side.190
11.5 COMS suspend and resume procedures .191
11.6 COMS release procedures.191
11.6.1 Normal COMS release .191
11.6.2 Release collisions .192
Page 9
ETS 300 175-5: September 1996
12 ConnectionLess Message Service (CLMS). 192
12.1 General . 192
12.2 CLMS states. 192
12.3 CLMS message transmission procedures. 192
12.3.1 Fixed length messages. 192
12.3.1.1 Procedure in the Fixed radio Termination (FT). 193
12.3.1.2 Procedure in the Portable radio Termination (PT) . 193
12.3.2 Variable length messages . 193
12.3.2.1 Procedure at the sending side. 193
12.3.2.2 Procedure at the receiving side. 194
12.3.2.3 Restrictions for portable side initiated messages . 194
13 Mobility Management (MM) procedures . 194
13.1 General . 194
13.2 Identity procedures. 195
13.2.1 Procedure for identification of PT. 195
13.2.2 Procedure for temporary identity assignment. 196
13.3 Authentication procedures. 197
13.3.1 Authentication of a PT. 198
13.3.2 Authentication of the user. 199
13.3.3 Authentication of a FT. 199
13.4 Location procedures. 200
13.4.1 Location registration . 200
13.4.2 Detach. 202
13.4.3 Location update. 202
13.5 Access rights procedure . 203
13.5.1 Obtaining the access rights . 203
13.5.2 Termination of access rights. 204
13.6 Key allocation procedure. 206
13.7 Parameter retrieval procedure. 207
13.8 Ciphering related procedure . 208
14 Link Control Entity (LCE) procedures . 211
14.1 General . 211
14.2 Connection oriented link control procedures. 212
14.2.1 Link establishment . 212
14.2.2 Direct PT initiated link establishment . 212
14.2.3 Indirect (paged) FT initiated link establishment. 213
14.2.4 Direct FT initiated link establishment (optional). 215
14.2.5 Link maintenance. 215
14.2.6 Link suspend and resume. 215
14.2.6.1 Link suspend . 215
14.2.6.2 Link resume. 216
14.2.7 Link release . 216
14.2.7.1 NLR notification without "partial release" as release
reason . 216
14.2.7.2 NLR notification with "partial release" as release reason . 217
14.3 Connectionless link control procedures. 217
14.3.1 Message routing. 217
14.3.2 Broadcast announce procedure . 218
14.4 Procedure for collective and group ringing . 218
15 Management procedures. 219
15.1 Lower Layer Management Entity (LLME) . 219
15.2 Service mapping and negotiation. 220
15.2.1 General . 220
15.2.2 Prioritised list negotiation. 220
15.2.3 Exchanged attribute negotiation . 221
15.2.4 Operating parameter negotiation. 221
15.2.5 Peer attribute negotiation . 221
Page 10
ETS 300 175-5: September 1996
15.3 Service modification procedures .222
15.4 Resource management .222
15.5 Management of MM procedures.222
15.6 Call ciphering management.223
15.7 External Handover .224
15.7.1 Handover candidate procedures.224
15.7.1.1 General.224
15.7.1.2 Handover candidate indication.224
15.7.1.3 Handover candidate retrieval.225
15.7.1.4 Target FP selection.225
15.7.2 Handover reference procedure.226
15.7.2.1 General.226
15.7.2.2 Handover reference indication .226
...