SIST ETS 300 175-4:1999
(Main)Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) 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-Jun-1999
- Technical Committee
- RES - Radio equipment and systems
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Jul-1999
- Due Date
- 01-Jul-1999
- Completion Date
- 01-Jul-1999
SIST ETS 300 175-4:1999 is the Slovenian version of ETS 300 175-4 Edition 2 for Digital Enhanced Cordless Telecommunications (DECT) Common Interface (CI). It specifies the Data Link Control (DLC) layer, which is the DECT layer 2b between MAC and NWK, and it defines how DECT equipment carries control traffic and user traffic over the radio interface. The standard is written for implementers of DECT fixed and portable parts who need the DLC procedures, frame formats, and management rules in one document.
What does SIST ETS 300 175-4:1999 specify?
SIST ETS 300 175-4:1999 specifies the DECT DLC layer and its two independent planes of operation: the Control plane (C-plane) and the User plane (U-plane). The C-plane covers signalling and control, including a reliable point-to-point service and a broadcast service. The U-plane covers end-to-end user information and defines a family of independent services with different protection, delay, and rate-adaptation behavior.
The document is organized from the general layer model to detailed field coding and procedures. It moves through the DLC overview, C-plane service characteristics, frame structures, peer-to-peer procedures, management procedures, U-plane service characteristics, U-plane frame structures, and U-plane peer-to-peer procedures.
| Annex | What it covers |
|---|---|
| A | LAPC timer values, U-plane timer values, and constants such as N250 and N251 |
| B | Arithmetic conventions, checksum coding and decoding algorithms, and examples |
| C | MAC connection states, informative |
| D | Mapping of agreed channel rates to MCS sizes for LU5, for protected and unprotected operation |
| E | LU7 64 kbit/s data bearer service, including architecture, ARQ/FEC, procedures, and network layer service |
What are the key requirements of SIST ETS 300 175-4:1999?
SIST ETS 300 175-4:1999 requires DECT implementations to treat the C-plane and U-plane as separate, independently managed services. That separation matters in practice because control signalling, broadcast, and user data are handled with different protocols, different SAPs, and different frame structures.
C-plane architecture and services
Clause 4 defines the C-plane as the control plane of the DECT protocol stack. It provides two independent services: the data link service (LAPC+Lc) and the broadcast service (Lb). In practice, an implementation must route signalling through the correct SAP and must not mix the point-to-point C-plane service with broadcast traffic.
Clause 5 says the broadcast service is an unacknowledged connectionless service from the Fixed radio Termination (FT) to one or more Portable radio Terminations (PTs). Lb is used for restricted broadcast and is carried on fixed-length frames with MAC layer broadcast duplication. In practice, this supports paging and other network messages that need to reach active PTs.
C-plane framing and link control
Clauses 6 and 7 define the C-plane frame structure and the coding of the address, control, length indicator, fill, and checksum fields. The control field supports I-format, S-format, and U-format frames, and the length indicator is used to delimit frames. In practice, this means implementers must encode and decode bits exactly as specified so that link partners can interpret the frame type, length, and sequence control correctly.
Clause 7 also defines the command and response set used on a C-plane link, including I, RR, RNR, REJ, SABM, DM, UI, DISC, and UA. The standard distinguishes class U unacknowledged transfer, class A acknowledged single-frame operation, and class B acknowledged multiple-frame operation. In practice, class A is the default for connection-oriented links, class B adds multiframe capability when both sides negotiate it, and class U is the only class used for connectionless service.
Clause 7.10 requires the checksum field to include both an underlying checksum and a link signature. The link signature is used to protect against slot theft and is defined for links to a given PT within the domain of one FT. In practice, implementers must maintain the signature at both ends through the Lower Layer Management Entity (LLME) and combine it with the checksum exactly as specified.
Primitives and management
Clause 8 defines abstract primitives between the DLC layer and the adjacent layers. The key NWK-facing primitives include DL_ESTABLISH, DL_RELEASE, DL_DATA, DL_UNIT_DATA, DL_SUSPEND, DL_RESUME, DL_ENC_KEY, DL_ENCRYPT, DL_BROADCAST, DL_EXPEDITED, DL_U_DATA, DL_U_UNIT_DATA, and DL_U_ERROR. In practice, these primitives describe the layer interfaces that software must provide, even though the standard treats them as abstract rather than testable APIs.
Clause 10 assigns coordination to the LLME. The LLME manages MAC connection set-up, release, and modification, chooses the logical channel, installs and removes DLC C-plane and U-plane resources, coordinates connection handover, and handles ciphering management. In practice, the LLME is the control point that ties the DLC layer to the MAC layer and the NWK layer.
U-plane services and bearer types
Clause 11 defines the family of U-plane services, collectively called LUX. The named members include LU1 TRansparent UnProtected service (TRUP), LU2 Frame RELay service (FREL), LU3 Frame SWItching service (FSWI), LU4 Forward Error Correction service (FEC), LU5 Basic Rate AdapTion service (BRAT), LU6 Secondary Rate AdapTion (SRAT), LU7 64 kbit/s data bearer service, and LU16 ESCape service (ESC), with LU8 to LU15 reserved. In practice, this lets an implementation choose a service that matches the application, from low-delay speech to protected data bearer operation.
Clause 11 also states that each U-plane service is independent and is accessed through its own LU SAP. LU1 is the simplest service and is intended for speech and transparent data with no error protection. LU5 and LU6 support rate adaptation, while LU7 provides a full-duplex synchronous 64 kbit/s bearer with FEC and ARQ behavior described in Annex E.
U-plane frame formats and procedures
Clauses 12 to 14 define the U-plane frame structures FU1 to FU6 and the peer-to-peer procedures for those frames. The frame types differ by whether they use addressing, length indication, and sequencing, and the transmission classes range from class 0 to class 3. In practice, this tells implementers whether a link is optimized for minimum delay, frame boundary preservation, sequencing, or retransmission.
Clause 14 defines the generic rules for acknowledgements, sequence numbering, and operation parameter negotiation on U-plane links. The procedures are written to support one point-to-point U-plane link at a time, even though multiple instances may exist in a device. In practice, this gives a common procedure set that can be reused across several LU services.
What terms does SIST ETS 300 175-4:1999 define?
- Digital Enhanced Cordless Telecommunications (DECT) - the cordless telecommunications system for which this common interface standard defines the DLC layer.
- Data Link Control (DLC) - the DECT layer 2b that carries control-plane and user-plane traffic between MAC and NWK.
- Control plane (C-plane) - the DLC plane used mainly for DECT signalling, internal control, and some user control.
- User plane (U-plane) - the DLC plane used for end-to-end user information and application-dependent procedures.
- Link Access Protocol for DECT (LAPC) - the upper C-plane protocol entity that provides reliable point-to-point link service and uses DECT-specific framing.
- Lower Layer Management Entity (LLME) - the management entity that coordinates routing, MAC connection control, handover, and service instancing.
- Basic Rate AdapTion service (BRAT) - the U-plane service that rate-matches and multiplexes input channels into multi-channel sets.
- 64 kbit/s data bearer service (LU7) - the U-plane service that provides synchronous 64 kbit/s bearer operation using FEC and ARQ.
Who uses SIST ETS 300 175-4:1999?
SIST ETS 300 175-4:1999 is used by DECT equipment designers who implement the DLC layer in fixed parts, portable parts, repeaters, and interworking units. It is also used by chipset and firmware teams that need the exact frame coding, sequence rules, and management behavior.
Test laboratories and quality teams use it to check that a DECT implementation handles C-plane and U-plane traffic in the way the standard defines. Buyers and integrators use it to judge whether a product supports the DECT services they need, such as broadcast paging, transparent speech transport, rate adaptation, or LU7 bearer support.
What changed in SIST ETS 300 175-4:1999 from the previous edition?
SIST ETS 300 175-4:1999 is identical to ETS 300 175-4 Edition 2. The scope says this second edition updates ETS 300 175 using experience from the development of TBR 6 and TBR 10 and comments received.
Which standards are used with SIST ETS 300 175-4:1999?
The standard cites the following references and companion DECT parts:
- ETS 300 175-1 - DECT Common Interface overview and shared definitions.
- ETS 300 175-2 - Physical layer.
- ETS 300 175-3 - Medium Access Control (MAC) layer and lower-layer primitives.
- ETS 300 175-5 - Network (NWK) layer.
- ETS 300 175-6 - Identities and addressing.
- ETS 300 175-7 - Security features.
- ETS 300 175-8 - Speech coding and transmission.
- ETS 300 175-9 - Public Access Profile (PAP).
- I-ETS 300 176 - Approval test specification.
- ETSI-GSM Technical Specification 04.06 - data link layer reference for the LAPD_M framing idea used in the C-plane.
- CCITT Q.920 and Q.921 - the LAPD basis for LAPC.
- CCITT V.42 - error-control procedures used as the basis for LAPU.
- CCITT V.110 - rate-adaptation reference.
- CCITT X.200 and X.210 - OSI reference model and service-convention terminology.
- ISO/IEC 8073 - checksum basis used in the DLC checksum method.
What does the SIST ETS 300 175-4:1999 document contain?
The document contains detailed bit-level frame formats for the C-plane and U-plane, including address, control, length indicator, fill, and checksum fields. It also contains command and response coding, primitive lists between layers, and peer-to-peer procedures for acknowledged, unacknowledged, and broadcast communication.
It includes the LLME management model, MAC connection handling, handover rules, and ciphering management. Annex A gives timer values and constants, Annex B gives checksum algorithms and examples, and Annex C shows MAC connection states.
Annex D maps agreed channel rates to MCS sizes for LU5, and Annex E gives the detailed LU7 service description, including buffering, FEC, ARQ, control fields, sequence variables, exception handling, and network layer service behavior.
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-4:1999 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) 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-4:1999 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT); 35.100.20 - Data link layer. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 175-4:1999 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-julij-1999
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH '(&7 6NXSQLYPHVQLN &,
GHO 3ODVWNUPLOMHQMDSRGDWNRYQLKSRYH]DY '&/
Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4:
Data Link Control (DLC) layer
Ta slovenski standard je istoveten z: ETS 300 175-4 Edition 2
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
35.100.20 Podatkovni povezovalni sloj Data link layer
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 175-4
TELECOMMUNICATION September 1996
STANDARD Second Edition
Source: ETSI TC-RES Reference: RE/RES-03027-4
ICS: 33.060, 33.060.50
Key words: DECT, radio
Radio Equipment and Systems (RES);
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI);
Part 4: Data Link Control (DLC) 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-4: 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-4: September 1996
Contents
Foreword .11
1 Scope .13
2 Normative references.13
3 Definitions and abbreviations .14
3.1 Definitions .14
3.2 Abbreviations .15
4 Data Link Control (DLC) layer overview .17
4.1 General .17
4.2 C-Plane data link service .17
4.3 C-plane broadcast service .19
4.4 U-plane services .19
4.5 Lower Layer Management Entity (LLME).19
5 C-plane service characteristics .20
5.1 Data link service (LAPC+Lc).20
5.1.1 General.20
5.1.2 LAPC types of operation.21
5.1.3 Establishment of information transfer modes.21
5.1.3.1 Data Link Identifier (DLI).21
5.1.3.2 LAPC states.21
5.2 Broadcast service (Lb).22
6 Frame structures for C-plane services.23
6.1 Data link service frame structure .23
6.1.1 General frame structure .23
6.1.2 Lc frame delimiting and transparency .24
6.1.3 Transmission order .24
6.1.4 Routing to logical channels .25
6.1.4.1 C logical channel .25
F
6.1.4.2 C logical channel.25
S
6.1.5 Invalid frames.26
6.2 Broadcast service frame structure.26
6.2.1 Standard frame structure .26
6.2.2 Extended frame structure.27
7 Elements of procedures and formats of fields for C-plane peer-to-peer communication .27
7.1 General .27
7.2 Address field formats.27
7.3 Address field parameters.27
7.3.1 REServed bit (RES) .27
7.3.2 Command Response (C/R) bit.27
7.3.3 SAPI field.28
7.3.4 New Link Flag (NLF) bit.28
7.3.5 LLN-field .28
7.3.6 Data Link Identifiers (DLI).29
7.4 Control field formats.29
7.5 Control field parameters .29
7.5.1 Poll/Final (P/F) bit.29
7.5.2 Multiple frame operation variables and sequence numbers.30
7.5.2.1 Modulus .30
7.5.2.2 Send state Variable V(S) .30
7.5.2.3 Acknowledge state Variable V(A) .30
7.5.2.4 Send sequence Number N(S) .30
Page 4
ETS 300 175-4: September 1996
7.5.2.5 Receive state Variable V(R). 30
7.5.2.6 Receive sequence Number N(R). 30
7.5.3 Unacknowledged operation variables and sequence numbers . 30
7.5.4 Supervisory and Unnumbered function bits S and U. 31
7.6 Length indicator field format. 31
7.7 Length indicator field parameters. 31
7.7.1 Length indicator field extension bit; N. 31
7.7.2 More data bit; M. 31
7.7.3 Length parameter; L . 32
I
7.7.4 Extended length parameter; L . 32
JJ
7.7.5 Reserved bit; RES . 32
7.8 Fill field format. 32
7.9 Checksum field format . 33
7.10 Checksum field parameters . 33
7.11 Commands and responses . 34
7.11.1 Information (I) command . 35
7.11.2 Receive Ready (RR) command/response . 35
7.11.3 Receive Not Ready (RNR) command/response. 35
7.11.4 REJect (REJ) command/response . 35
7.11.5 Set Asynchronous Balanced Mode (SABM) command . 36
7.11.6 Disconnect Mode (DM) response . 36
7.11.7 Unnumbered Information (UI) command. 36
7.11.8 DISConnect (DISC) command . 36
7.11.9 Unnumbered ACK (UA) response . 36
8 Primitives . 37
8.1 Primitive types . 37
8.2 Primitives to the MAC layer (lower layer) . 37
8.3 Primitives to the NWK layer (higher layer) . 37
8.3.1 Parameter definitions. 37
8.3.2 S-SAP primitives. 38
8.3.2.1 DL_ESTABLISH primitive . 39
8.3.2.2 DL_RELEASE primitive. 39
8.3.2.3 DL_DATA primitive . 39
8.3.2.4 DL_UNIT_DATA primitive. 39
8.3.2.5 DL_SUSPEND primitive. 39
8.3.2.6 DL_RESUME primitive. 40
8.3.2.7 DL_ENC_KEY primitive . 40
8.3.2.8 DL_ENCRYPT primitive. 40
8.3.3 B-SAP primitives. 40
8.3.3.1 DL_BROADCAST primitive. 40
8.3.3.2 DL_EXPEDITED primitive. 41
8.4 Primitives to the interworking unit. 41
8.4.1 Parameter definitions. 41
8.4.2 LU -SAP primitives . 41
X
8.4.2.1 DL_U_DATA primitive. 42
8.4.2.2 DL_U_UNIT_DATA primitive . 42
8.4.2.3 DL_U_ERROR primitive . 42
9 C-plane peer-to-peer procedures . 42
9.1 General. 42
9.2 Point to point acknowledged operation . 43
9.2.1 Procedure for the use of the P/F bit. 43
9.2.1.1 Class A acknowledged information transfer . 43
9.2.1.2 Class B acknowledged information transfer . 43
9.2.2 Use of LLN. 43
9.2.2.1 Class A operation. 43
9.2.2.2 Class B operation. 44
9.2.3 Link establishment and information transfer in class A operation . 44
9.2.3.1 Establishing class A operation . 44
9.2.3.2 Class A acknowledged information transfer . 45
9.2.3.4 Reception of class A I-frames. 45
9.2.3.5 Receiving acknowledgements . 46
Page 5
ETS 300 175-4: September 1996
9.2.3.6 Waiting for acknowledgement .46
9.2.3.7 Release of class A operation.47
9.2.3.8 Re-establishment of class A operation.47
9.2.4 Establishing class B multiple frame operation.47
9.2.4.1 Overview.47
9.2.4.2 Class B multiple frame establishment procedures .48
9.2.4.3 Class B LLN assignment procedures .49
9.2.4.3.1 PT establishment.49
9.2.4.3.2 FT establishment .50
9.2.5 Link maintenance and information transfer in class B multiple frame
operation .50
9.2.5.1 Transmitting I-frames .50
9.2.5.2 Receiving I-frames.51
9.2.5.2.1 P bit set to 1.51
9.2.5.2.2 P bit set to 0.51
9.2.5.3 Sending and receiving acknowledgements .51
9.2.5.3.1 Sending acknowledgements.51
9.2.5.3.2 Receiving acknowledgements .52
9.2.5.4 Receiving REJ-frames.52
9.2.5.5 Receiving RNR-frames.53
9.2.5.6 LAPC own receiver busy condition .55
9.2.5.7 Waiting acknowledgement .55
9.2.6 Release of class B multiple frame operation.56
9.2.7 Link suspension and resumption.57
9.2.7.1 Link suspension.57
9.2.7.1.1 Class B acknowledged suspend.57
9.2.7.1.2 Unacknowledged suspend.58
9.2.7.2 Class B link resumption.59
9.2.7.3 Connection handover.60
9.2.7.3.1 Class A connection handover .61
9.2.7.3.2 Class B connection handover .62
9.2.7.3.3 Expiry of connection handover timer .62
9.2.8 Re-establishment of class B multiframe operation.63
9.2.8.1 Criteria for re-establishment .63
9.2.9 Exception handling .64
9.2.9.1 General.64
9.2.9.2 Class B exception condition reporting and recovery.64
9.2.9.2.1 N(S) sequence error .64
9.2.9.2.2 N(R) sequence error.65
9.2.9.2.3 Timer recovery condition .65
9.2.9.2.4 Collision of identical transmitted and
received commands.65
9.3 Unacknowledged operation .65
9.3.1 Use of LLN for unacknowledged information transfer.65
9.3.2 Class U link establishment .65
9.3.3 Unacknowledged information transfer.65
9.3.3.1 Transmission of unacknowledged information .65
9.3.3.2 Reception of unacknowledged information.66
9.3.4 Unacknowledged release.66
9.4 Broadcast operation.66
9.4.1 Normal operation.66
9.4.1.1 Procedure in the Fixed radio Termination (FT) .66
9.4.1.2 Procedure in the Portable radio Termination (PT).66
9.4.2 Expedited operation .67
9.4.2.1 Procedure in the Fixed radio Termination (FT) .67
9.4.2.2 Procedure in the Portable radio Termination (PT).67
9.5 MAC layer interfaces.67
9.5.1 MC-SAP .67
9.5.1.1 C-plane overview .67
9.5.1.2 C-plane service data procedures.68
9.5.1.3 U-plane service data.68
9.5.2 MB-SAP.69
9.5.2.1 C-plane overview .69
Page 6
ETS 300 175-4: September 1996
9.5.2.2 C-plane service data procedures . 69
9.5.2.3 U-plane service data . 69
9.5.3 MA-SAP . 69
9.5.3.1 Overview . 69
9.5.3.2 Service data procedures . 69
10 Management procedures. 70
10.1 Lower Layer Management Entity (LLME). 70
10.2 MAC connection management. 70
10.2.1 MAC connection set-up . 70
10.2.2 MAC connection release. 71
10.2.3 MAC connection modification . 71
10.2.4 MAC connection identifiers. 72
10.2.4.1 Overview . 72
10.2.4.2 Advanced MAC Connection Identifiers (AMCI). 72
10.2.4.3 Basic MAC Connection Identifiers (BMCI) . 73
10.2.4.4 MAC Connection Endpoint Identifier (MCEI). 73
10.2.5 Selection of logical channel (C or C ). 73
S F
10.3 DLC C-plane (LAPC) management. 74
10.3.1 Provision of link signature. 74
10.3.2 Routing of connection oriented links. 74
10.3.3 Routing of connectionless links . 74
10.4 DLC U-plane (LUX) management. 75
10.4.1 U-plane establishment. 75
10.4.2 U-plane release . 75
10.4.3 U-plane suspend and resume . 75
10.5 Connection handover management. 76
10.6 Ciphering management. 76
10.6.1 Ciphering management in cases where the NWK layer executes the
ciphering related MM procedure. 76
10.6.1.1 Providing a key to the MAC layer. 76
10.6.1.2 Starting and stopping the ciphering. 77
10.6.1.3 Connection handover. 77
10.6.2 Ciphering management in cases where the NWK layer does not execute
the ciphering related MM procedure. 77
11 U-plane service characteristics. 77
11.1 General. 77
11.2 LU1 TRansparent UnProtected service (TRUP) . 78
11.3 LU2 Frame RELay service (FREL) . 79
11.3.1 General . 79
11.3.2 Checksum operation. 80
11.3.3 Segmentation and transmission class. 80
11.3.4 Data transmission. 81
11.3.4.1 Send side procedure. 81
11.3.4.2 Receive side procedure . 81
11.4 LU3 Frame SWItching service (FSWI). 81
11.5 LU4 Forward Error Correction service (FEC). 82
11.6 LU5 Basic Rate AdapTion service (BRAT) . 82
11.6.1 Overview. 82
11.6.2 Protected service operation. 83
11.6.2.1 General . 83
11.6.2.2 Data buffering and initial rate adaption . 84
11.6.2.3 Multi-channel set multiplexing. 85
11.6.2.4 Segmentation of Multiplexed Data Units (MDU) . 87
11.6.2.5 Frame sequencing and addition of control and fill octets. 87
11.6.2.6 Frame transmission . 88
11.6.3 Unprotected service operation. 89
11.6.3.1 General . 89
11.6.3.2 Data buffering and initial rate adaption . 89
11.6.3.3 Multi-channel set multiplexing. 90
11.6.3.4 Segmentation of MDUs. 91
11.6.3.5 Frame transmission . 91
Page 7
ETS 300 175-4: September 1996
11.7 LU6 Secondary Rate AdapTion (SRAT) service.92
11.7.1 General.92
11.8 LU16 ESCape Service (ESC) .93
11.8.1 General.93
11.9 LU7 64 kbits/s data bearer service .93
12 Frame structures for U-plane services.94
12.1 General .94
12.2 FU1 frame structure.94
12.2.1 General frame structure .94
12.2.2 FU1 buffering procedures .95
12.2.3 Minimum delay (speech) operation .95
12.2.4 Connection handover .96
12.2.5 Transmission order .96
12.3 FU2 frame structure.96
12.3.1 General frame structure .96
12.3.2 FU2 buffering procedures .97
12.3.3 Connection handover .97
12.3.4 Transmission order .97
12.4 FU3 frame structure.97
12.4.1 General frame structure .97
12.4.2 FU3 buffering procedures .98
12.4.3 Connection handover .98
12.4.4 Transmission order .98
12.5 FU4 frame structure.99
12.5.1 General frame structure .99
12.5.2 FU4 buffering procedures .100
12.5.3 Connection handover .100
12.5.4 Transmission order .100
12.6 FU5 frame structure.100
12.6.1 General frame structure .100
12.6.2 FU5 buffering procedures .101
12.6.3 Connection handover .101
12.6.4 Transmission order .102
12.7 FU6 frame structure.102
12.7.1 General frame structure .102
12.7.2 FU6 buffering procedures .103
12.7.3 Connection handover .103
12.7.4 Transmission order .103
13 Elements of procedures and formats of fields for U-plane peer-to-peer communication .104
13.1 General .104
13.2 Address elements .104
13.2.1 Address field format .104
13.2.2 Address field parameters .104
13.3 Length indicator elements.105
13.3.1 Length indicator field format.105
13.3.2 Length indicator field parameters.105
13.4 Sequence number elements.106
13.4.1 Send sequence number format.106
13.4.2 Send sequence number parameters.106
13.4.3 Receive sequence number parameters .106
13.5 Fill elements.107
13.5.1 Fill field format.107
14 U-plane peer-to-peer procedures.107
14.1 General .107
14.2 Frame transmission principles.107
14.2.1 Sequence numbering .107
14.2.2 Acknowledgements .107
14.2.2.1 Sending acknowledgements.107
14.2.2.2 Receiving acknowledgements .108
14.2.3 Transmission classes.108
Page 8
ETS 300 175-4: September 1996
14.2.3.1 Class 1: no LU retransmission. 108
X
14.2.3.2 Class 2: variable throughput LU retransmission. 109
X
14.2.3.3 Class 3: fixed throughput LU retransmission. 109
X
14.2.4 Operation parameter negotiation. 109
14.3 Frame transmission procedures . 110
14.3.1 General . 110
14.3.2 Class 0 procedures. 110
14.3.2.1 Sending side procedure . 110
14.3.2.2 Receiving side procedure. 110
14.3.3 Class 1 procedures. 110
14.3.3.1 Sending side procedure . 110
14.3.3.2 Receiving side procedure. 111
14.3.4 Class 2 procedures. 112
14.3.4.1 Sending side procedure . 112
14.3.4.2 Receiving side procedure. 113
14.3.5 Class 3 procedures. 114
14.3.5.1 Sending side procedure . 114
14.3.5.2 Receiving side procedure. 115
Annex A (normative): System parameters. 116
A.1 LAPC timer values. 116
A.2 U-plane timer values. 117
A.3 Constants. 117
A.3.1 Retransmission counter (N250) . 117
A.3.2 Maximum number of CHO attempts (N251) . 117
Annex B (informative): Checksum algorithms . 118
B.1 Arithmetic conventions. 118
B.2 Coding algorithm. 118
B.3 Decoding algorithm. 119
B.4 Some examples. 119
Annex C (informative): MAC connection states. 120
Annex D (normative): Mapping of agreed channel rates to MCS sizes . 121
D.1 Protected class operation . 121
D.2 Unprotected class operation. 122
Annex E (normative): LU7 64 kbit/s data bearer service . 123
E.1 General. 123
E.2 Physical layer service . 123
E.3 MAC layer service. 123
E.4 DLC layer service . 123
E.4.1 Architectural model . 123
E.4.1.1 Transmit (Tx) frame buffering. 123
E.4.1.2 Receive (Rx) frame buffering. 124
E.4.2 Automatic-Repeat-Request (ARQ) and Forward Error Control (FEC) . 124
E.4.2.1 Control field. 125
E.4.2.1.1 Format control parameter coding. 125
Page 9
ETS 300 175-4: September 1996
E.4.2.1.2 Offset variable V(O).126
E.4.2.1.3 Time variables V (T) .126
n
E.4.2.1.4 Offset number N(O).126
E.4.2.1.5 Send state variable V(S).126
E.4.2.1.6 Acknowledge state variable V(A).127
E.4.2.1.7 Send sequence number N(S).127
E.4.2.1.8 Receive state variable V(R).127
E.4.2.1.9 Receive sequence number N(R) .127
E.4.2.2 Information field.127
E.4.2.3 ARQ checksum .128
E.4.3 Procedures for normal operation .128
E.4.3.1 Establishment and synchronisation procedures.128
E.4.3.2 Active phase.130
E.4.3.2.1 Transmitting frames (first time transmission) .130
E.4.3.2.2 Re-transmitting frames .131
E.4.3.2.3 Receiving frames.131
E.4.3.2.4 Sending acknowledgements.132
E.4.3.2.5 Receiving acknowledgements .132
E.4.3.3 Release .132
E.4.4 Exceptional procedures.132
E.4.4.1 Invalid frame condition .132
E.4.4.2 Establishment.132
E.4.4.3 Transmitting frames .132
E.4.4.4 Receiving frames.133
E.4.4.5 Sending acknowledgements .133
E.4.4.6 Forwarding of received data.133
E.4.4.7 N(R) sequence error.133
E.4.4.8 N(O) sequence error .133
E.4.4.9 N(S) sequence error.134
E.4.4.10 Format error .134
E.4.4.11 Abnormal release .134
E.5 Network layer service .134
E.5.1 LCE service.134
E.5.2 CC service .134
Annex F (informative): Bibliography.135
History.136
Page 10
ETS 300 175-4: September 1996
Blank page
Page 11
ETS 300 175-4: September 1996
Foreword
This second edition European Telecommunication Standard (ETS) has been produced by the Radio
Equipment and Systems (RES) Technical Committee of the European Telecommunications Standards
Institute (ETSI).
This ETS forms part 4 of a series of 9 laying down the arrangements for the Digital Enhanced Cordless
Telecommunications (DECT) Common Interface (CI).
Part 1: "Overview".
Part 2 "Physical layer (PHL)".
Part 3 "Medium Access Control (MAC) layer".
Part 4 "Data Link Control (DLC) layer".
Part 5: "Network (NWK) layer".
Part 6: "Identities and addressing".
Part 7: "Security features".
Part 8: "Speech coding and transmission".
Part 9: "Public Access Profile (PAP)".
Annexes A, D and E in this ETS are normative. Annexes B, C and F in this ETS are informative.
Further details of the DECT system may be found in ETR 015, ETR 043, and ETR 056.
Transposition dates
Date of adoption of this ETS: 6 September 1996
Date of latest announcement of this ETS (doa): 31 December 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 June 1997
Date of withdrawal of any conflicting National Standard (dow): 30 June 1997
Page 12
ETS 300 175-4: September 1996
Blank page
...