ETSI TS 144 005 V13.0.0 (2016-01)

Digital cellular telecommunications system (Phase 2+); Data Link (DL) Layer; General aspects (3GPP TS 44.005 version 13.0.0 Release 13)

RTS/TSGG-0244005vd00

General Information

• Status: Published
• Publication Date: 24-Jan-2016
• Technical Committee: 3GPP GERAN 2 - Protocol aspects
• Current Stage: 12 - Completion
• Due Date: 20-Jan-2016
• Completion Date: 25-Jan-2016

Standards Content (Sample)

ETSI TS 1144 005 V13.0.0 (201616-01)






TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Datata Link (DL) Layer;
GGeneral aspects
(3GPP TS 44.0.005 version 13.0.0 Release 13 13)

R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS

---------------------- Page: 1 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 1 ETSI TS 144 005 V13.0.0 (2016-01)



Reference
RTS/TSGG-0244005vd00
Keywords
GSM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2016.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 2 ETSI TS 144 005 V13.0.0 (2016-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 3 ETSI TS 144 005 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
1 Scope . 5
2 References . 6
2a Concepts and terminology . 7
3 Overview description of LAPDm functions and procedures . 9
3.1 General . 9
3.2 Unacknowledged operation . 10
3.3 Acknowledged operation . 10
3.4 Information transfer mode . 11
3.4.1 Information transfer on the BCCH . 11
3.4.2 Information transfer on the PCH + AGCH . 11
3.4.3 Information transfer on the DCCHs . 11
3.5 Release of data links . 11
4 Service characteristics . 11
4.1 General . 11
4.2 Services provided to layer 3 . 11
4.2.1 General . 11
4.2.2 Priority . 12
4.2.3 Segmentation . 12
4.2.4 Unacknowledged information transfer service . 12
4.2.5 Acknowledged information transfer services . 12
4.2.6 Random access procedure . 14
4.3 Services required from the physical layer . 14
4.4 Administrative services . 15
4.4.1 General description of administrative services . 15
4.4.2 Definition of primitives for administrative services . 15
5 Overview of data link layer structure . . 15
5.1 Functional composition . 15
5.2 Identification of data link end points . 16
5.3 Data link procedure . 16
5.4 Data link distribution procedure . 16
5.5 Random access procedures . 17
6 Specific requirements . 17
6.1 Mode of operation and allowed SAPIs . 17
6.2 Acknowledged mode of operation . 18
6.2.1 Window size . 18
6.2.2 Processing capacity . 18
Annex A (informative): Change History . 19
History . 20

ETSI

---------------------- Page: 4 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 4 ETSI TS 144 005 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 5 ETSI TS 144 005 V13.0.0 (2016-01)
1 Scope
The present document describes in general terms the Link Access Procedures on the Dm channel, LAPDm. The
application of this protocol to other channel types is for further study. Details are provided in 3GPP TS 44.006.
The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface (MS
to network interface) using the Dm channel.
NOTE 1: The term Dm channel is used for convenience to designate the collection of all the various signalling
channels required in the GSM system. See also 3GPP TS 44.003.
The definition of LAPDm is based on the principles and terminology of:
- ITU-T Recommendations X.200 and X.210: the reference model for Open Systems Interconnection (OSI);
- ITU-T Recommendations Q.920 and Q.921: the specification of LAPD for the user-network interface in ISDN;
- ITU-T Recommendation X.25 LAPB: user-network interface for packet mode terminals; and
- ISO/IEC 3309 and ISO 4335: High-level Data Link Control (HDLC) standards for frame structure and elements
of procedures.
LAPDm is a protocol that operates at the data link layer of the OSI architecture. The relationship between the data link
layer and other protocol layers is defined below.
NOTE 2: The interface between the mobile station and external terminal equipment/terminal adapters is defined in
the Technical Specifications of the GSM 07-series.
NOTE 3: The physical layer on the radio interface is defined in 3GPP TS 44.004 and layer 3 is defined in
3GPP TS 24.007, 3GPP TS 44.018, 3GPP TS 24.010 and 3GPP TS 24.011. Reference should be made to
these Technical Specifications for the complete definitions of the protocols and procedures across the
GSM PLMN radio interface.
NOTE 4: The term "data link layer" is used in the main text of the present document. However, mainly in figures
and tables, the terms "layer 2" and "L2" are used abbreviations. Furthermore, in accordance with
3GPP TS 24.007 and 3GPP TS 44.018 the term "layer 3" is used to indicate the layer above the data link
layer.
LAPDm is independent of the transmission bit rate. It requires physical channels with characteristics as defined in
3GPP TS 44.003.
Clause 2 below describes basic concepts used in the present document and 3GPP TS 44.006.
Clause 3 gives an overview description of LAPDm functions and procedures.
Clause 4 summarizes the services that the data link layer provides to layer 3 and the services that the data link layer
requires from the physical layer.
Clause 5 provides an overview of the data link layer structure.
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 6 ETSI TS 144 005 V13.0.0 (2016-01)
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 44.001: "Mobile Station - Base Station System (MS - BSS) Interface General Aspects
and Principles".
[3] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) Interface Channel Structures
and Access Capabilities".
[4] 3GPP TS 44.004: "Layer 1; General requirements".
[5] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL)
layer specification".
[6] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[7] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[8] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification; General
aspects".
[9] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[10] (void).
[11] (void).
[12] (void).
[13] (void).
[14] (void).
[15] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and Data
Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to
public data networks by dedicated circuit".
[16] ITU-T Recommendation X.200: "Information technology - Open Systems Interconnection - Basic
Reference Model: The basic model".
[17] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic
Reference Model: Conventions for the definition of OSI services".
[18] ITU-T Recommendation Q.920: "ISDN user-network interface data link layer - General aspects".
[19] ITU-T Recommendation Q.921: "ISDN user-network interface - Data link layer specification".
[20] ISO/IEC 3309: "Information technology - Telecommunications and information exchange between
systems - High-level Data Link Control (HDLC) procedures - Frame structure".
[21] ISO/IEC 4335: "Information technology - Telecommunications and information exchange between
systems - High-level Data Link Control (HDLC) procedures - Elements of procedures".
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 7 ETSI TS 144 005 V13.0.0 (2016-01)
2a Concepts and terminology
The general layering principles used in the present document and other specifications in the 44 series are given in
3GPP TS 44.001.
The data link layer is the next to lowest layer of the OSI reference model. The data link layer receives services from the
physical layer and provides services to layer 3.
The services provided by the data link layer are the combination of the services and functions provided by both the data
link layer and the physical layer.
A data link layer Service Access Point (SAP) is the point at which the data link layer provides services to layer 3. The
Service Access Point is identified by a Service Access Point Identifier (SAPI). One or more data link connection
endpoints can be associated with each data link layer SAP. See figure 1. A data link connection endpoint is identified by
a data link connection endpoint identifier (as seen from layer 3) and by a Data Link Connection Identifier DLCI (as
seen from the data link layer).
SAPIs and DLCIs used by LAPDm are defined in subclause 5.2.
Layer 3 Layer 3
entity
Datalink layer service access point
*
Datalink connection endpoint
Datalink
Datalink
layer
layer entity

Figure 1: Entities, service access points and endpoints
Co-operation between data link layer entities is governed by a peer-to-peer protocol specific to the layer. For
information exchange between two or more layer 3 entities, an association must be established between the layer 3
entities in the data link layer using a data link layer protocol. This association is called a data link connection. Data link
connections are provided by the data link layer between two or more SAPs (see figure 2).
Layer 3
Layer 3
entity
entity
Datalink layer
service access point


Datalink connection endpoint
Datalink relationship

Figure 2: Peer-to-peer relationship
Data link layer message units are conveyed between data link layer entities by means of physical connection.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 8 ETSI TS 144 005 V13.0.0 (2016-01)
Layer 3 requests services from the data link layer via service primitives. The same applies for the interaction between
the data link layer and the physical layer. The primitives represent, in an abstract way, the logical exchange of
information and control between the data link layer and its adjacent layers. They do not specify or constrain
implementations.
The primitives that are exchanged between the data link layer and adjacent layers are of the following four types (see
also figure 3).
Layer 3
Indication Response
Confirm Request
* *
SAP
Data
link
layer
Layer 2 peer-to-peer protocol

NOTE: The same principle applies for data link layer-physical layer interactions.

Figure 3: Primitive action sequence
The REQUEST primitive type is used when a higher layer is requesting a service from the next lower layer.
The INDICATION primitive type is used by a layer providing a service to notify the next higher layer of activities
related to the primitive type REQUEST.
The RESPONSE primitive type is used by a layer to acknowledge receipt, from a lower layer, of the primitive type
INDICATION.
The CONFIRM primitive type is used by the layer providing the requested service to confirm that the activity has been
completed.
The precise specification of Layer-to-layer interactions is given in 3GPP TS 44.006.
Information between peer entities and between entities in adjacent layers attached to the same SAP is transferred in two
different types of message units:
- message units of a peer-to-peer protocol; and
- message units that contain layer-to-layer information concerning status and specialized service requests.
The message units of the layer 3 peer-to-peer protocol are carried by the data link connection. The message units
containing layer-to-layer information concerning status and specialized service requests are never conveyed over a data
link connection or a physical connection.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 9 ETSI TS 144 005 V13.0.0 (2016-01)
The present document introduces (see also figure 4):
a) the peer-to-peer protocol for the transfer of information and control between any pair of data link layer service
access points;
b) the interactions between the data link layer and layer 3, and between the data link layer and the physical layer.
Layer 3
Layer 3
entity entity
Datalink
Datalink layer
layer/layer 3
service access point
primitives
Datalink
Datalink Datalink layer
layer layer
peer-to-peer protocol
entity
entity
Datalink layer
service access point
Datalink
Physical layer
layer/
service access point
physical
layer
Physical
Physical
primitives
layer
layer
entity
entity
Physical connection

Figure 4: Data link layer reference model
3 Overview description of LAPDm functions and
procedures
3.1 General
The purpose of LAPDm is to convey information between layer 3 entities across the GSM PLMN radio interface using
the Dm channel. Specifically LAPDm will support:
- multiple layer 3 entities;
- multiple physical layer entities;
- broadcast control channel (BCCH) signalling;
- paging channel (PCH) signalling;
- access grant channel (AGCH) signalling;
- dedicated control channel (DCCH) signalling.
NOTE 1: The term "DCCH" designates a number of control channels (SDCCH, FACCH and SACCH) as defined
in 3GPP TS 44.003.
NOTE 2: The random access channel (RACH) does not utilise LAPDm. However, for the purpose of specification,
the data link layer acts as a protocol interface between layer 3 and the physical layer also for random
access.
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 10 ETSI TS 144 005 V13.0.0 (2016-01)
The frame structure of data link layer messages is defined in 3GPP TS 44.006.
The Dm channel between a network and a specific MS may be distorted on several control channels, e.g. PCH, SDCCH
and FACCH during a connection (See also 3GPP TS 44.003). Selection and activation of these channels is performed
by layer 3.
LAPDm includes functions for:
a) the provision of one or more data link connections on a Dm channel. Discrimination between the data link
connections is by means of a Data Link Connection Identifier (DLCI);
b) allowing recognition of frame types;
c) allowing layer 3 message units to be passed transparently between layer 3 entities;
d) sequence control, to maintain the sequential order of frames across a data link connections;
e) detection of format and operational errors on a data link;
f) notification to the layer 3 entity of unrecoverable errors;
NOTE 3: It is in the responsibility of layer 3 entity to recover from these errors.
g) flow control; and
h) contention resolution when establishing a data link after an access request has been made on the RACH.
Two types of operation of the data link layer are defined for layer 3 information transfer: unacknowledged operation
and acknowledged (multiple frame) operation. They may co-exist on a Dm channel.
The BCCH and the (PCH + AGCH) will only support unacknowledged operation. The SDCCH, SACCH and FACCH
will support both types of operation.
3.2 Unacknowledged operation
In unacknowledged operation, layer 3 information is transmitted in Unnumbered Information (UI) frames.
At the data link layer, the UI frames are not acknowledged. Flow control mechanisms and error recovery mechanisms
are not defined.
Applicability of unacknowledged operation to different types of control channels is specified in subclause 6.1.
3.3 Acknowledged operation
In acknowledged operation, layer 3 information is transmitted in frames that are acknowledged by the receiving data
link layer.
Error recovery procedures based on retransmission of unacknowledged frames are specified. In case of errors which
cannot be corrected by the data link layer, a report is issued to the layer 3 entity. Flow control procedures are also
defined.
Applicability of acknowledged operation to different types of control channels is specified in subclause 6.1.
Only one form of acknowledged information transfer is defined, i.e. multiple frame operation.
For multiple frame operation, layer 3 information is sent in numbered Information (I) frames. In principle, a number of I
frames may be outstanding at the same time. However, for many applications (e.g. signalling) a window size of 1 is
required. Multiple frame operation is initiated by a multiple frame establishment procedure using a Set Asynchronous
Balanced Mode (SABM) command.
If an access request has been made on the RACH, the establishment procedure also contains functions for resolving any
ambiguity that may arise as a result of this access method.
ETSI

---------------------- Page: 11 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 11 ETSI TS 144 005 V13.0.0 (2016-01)
3.4 Information transfer mode
3.4.1 Information transfer on the BCCH
The BCCH exists only in the network to MS direction and is used for broadcasting radio sub-system information to
MSs. Only UI frames are sent on the BCCH.
3.4.2 Information transfer on the PCH + AGCH
These channels exist only in the network to MS direction. On the PCH + AGCH only unacknowledged operation is
possible.
3.4.3 Information transfer on the DCCHs
On the DCCHs both unacknowledged operation and multiple frame operation are possible (see subclause 6.1). The type
of operation required at any time is determined by layer 3.
3.5 Release of data links
Multiple frame operation may be released in the following ways:
- normal release by exchange of commands/responses. This type of release is initiated by layer 3;
- local end release, i.e. without exchange of commands/responses, initiated and controlled by layer 3;
- abnormal local end release, i.e. without exchange of commands/responses, commanded by layer 3.
The release mode is indicated by layer 3.
No release mechanism using exchange of commands/responses is defined for unacknowledged operation.
4 Service characteristics
4.1 General
The data link layer provides services to layer 3 and utilizes the services provided by the physical layer.
In the present document and 3GPP TS 44.006 the following general syntax is used for describing primitives.
XX - Generic Name - Type (Parameters).
where XX designates the layer providing the services. In the present document XX is DL and MDL for the data link
layer and PH for the physical layer.
4.2 Services provided to layer 3
4.2.1 General
The specification of the interactions with layer 3 (primitives) provides a description of the services that the data link
layer, plus the physical layer, offer to layer 3, as viewed from layer 3.
Two forms of information transfer services are associated with layer 3. The first is based on unacknowledged
information transfer at the data link layer and the second service is based on acknowledged information transfer at the
data link layer using multiple frame operation. Different information transfer services may co-exist on the same data
link subject to restrictions imposed by the type of channel being used (see subclause 3.4).
ETSI

---------------------- Page: 12 ----------------------
3GPP TS 44.005 version 13.0.0 Release 13 12 ETSI TS 144 005 V13.0.0 (2016-01)
In addition, the data link layer will pass primitives between the physical layer and layer 3 for random access operation
on the RACH.
4.2.2 Priority
The priority between data links shall be as follows:
On SDCCH:
Highest priority: SAPI = 0;
Lowest priority : SAPI = 3.
On SACCH:
The priority arrangement on the SACCH must ensure that if a SAPI = 3 frame is awaiting transmission, two
SAPI = 0 frames are not sent in consecutive SACCH frames. An exception is when Repeated SACCH is
supported, where a SACCH block containing a SAPI = 0 frame may be repeated in the next SACCH period
(see 3GPP TS 44.006). In addition, for the mobile to network direction it must also be ensured that any SAPI = 3
frame is followed by at least one SAPI = 0
...