GSM T S

GSM GSM 08.
56
TECHNICAL December 1996
SPECIFICATION Version 5.0.0
Source: ETSI TC-SMG Reference: TS/SMG-030856Q
ICS: 33.020
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
GLOBAL SYSTEM FOR

MOBILE COMMUNICATIONS
Digital cellular telecommunications system;

Base Station Controller - Base Transceiver Station
(BSC - BTS) interface;
Layer 2 specification
(GSM 08.56)
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: [email protected]
Tel.: +33 4 92 94 42 00 - Fax: +33 4 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
GSM 08.56 version 5.0.0: December 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
Contents
Foreword .......................................................................................................................................................5
1 Scope ..................................................................................................................................................7
2 Normative references..........................................................................................................................7
3 Definitions and abbreviations ..............................................................................................................8
4 General description .............................................................................................................................8
5 Functional contents .............................................................................................................................9
6 LAPD functions....................................................................................................................................9
6.1 Exceptions and modifications ............................................................................................10
6.1.2 Command/Response field bit (C/R) ..............................................................10
6.1.3 Service Access Point Identifier (SAPI) ..........................................................10
6.1.4 TEI for point-to-point data link connection.....................................................10
6.1.5 Commands and responses ...........................................................................10
6.1.6 Exchange identification (XID) command/response .......................................10
6.1.7 MDL-XID........................................................................................................10
6.1.8 PH-DATA, PH DEACTIVATE and PH-ACTIVATE ........................................11
6.1.9 MPH-ACTIVATE, MPH-DEACTIVATE an MPH-INFORMATION .................11
6.1.10 Priority indicator.............................................................................................11
6.1.11 Terminal Endpoint Identifier (TEI) management procedures ........................11
6.1.11.1 General ................................................................................11
6.1.11.2 TEI assignment procedure ..................................................11
6.1.11.3 TEI identity verify procedure ................................................13
6.1.11.4 Formats and codes..............................................................13
6.1.12 Automatic negotiation of data link layer parameters .....................................14
6.1.13 Establishment procedures.............................................................................14
6.1.14 N(S) sequence error......................................................................................14
6.1.15 List of system parameters .............................................................................14
6.1.15.1 Timer T200 ..........................................................................15
6.1.15.2 Maximum number of retransmissions (N200) .....................15
6.1.15.3 Maximum number of octets in an information field (N201)..15
6.1.15.4 Maximum number of transmission of the TEI identity
request message (N202) .....................................................15
6.1.15.5 Maximum number of outstanding frames (K) ......................15
6.1.15.6 Timer T201 ..........................................................................15
6.1.15.7 Timer T202 ..........................................................................15
6.1.15.8 Timer T203 ..........................................................................15
6.1.16 Data link layer monitor function .....................................................................15
6.1.17 Miscellaneous................................................................................................15
History..........................................................................................................................................................16
Page 4
Blank page
Page 5
Foreword
This Global System for Mobile communications Technical Specification (GTS) has been produced by the
Special Mobile Group (SMG) Technical Committee (TC) of the European Telecommunications Standards
Institute (ETSI).
This GTS specifies the link layer used for signalling on the A-bis interface between Base Station Controller
(BSC) and Base Transceiver Station (BTS) within the digital cellular telecommunications system.
The contents of this GTS are subject to continuing work within TC-SMG and may change following formal
TC-SMG approval. Should TC-SMG modify the contents of this GTS it will then be republished by ETSI
with an identifying change of release date and an increase in version number as follows:
Version 5.x.y
where:
y the third digit is incremented when editorial only changes have been incorporated in the
specification;
x the second digit is incremented for all other types of changes, i.e. technical enhancements,
corrections, updates, etc.
The specification from which this GTS has been derived was originally based on CEPT documentation,
hence the presentation of this GTS may not be entirely in accordance with the ETSI/PNE rules.
Page 6
Blank page
Page 7
1 Scope
This Global System for Mobile communications Technical Specification (GTS) specifies the link layer used
for signalling on the A-bis interface between Base Station Controller (BSC) and Base Transceiver Station
(BTS). The use and general aspects of the A-bis interface are described in GSM 08.51 and the interface
aspects in GSM 08.52.
The Link Access Procedure on the D-channel (LAPD) specification used on the A-bis interface in the GSM
PLMN is a subset of the ETS 300 125 which in turn has less options than the CCITT
Recommendation Q.921.
This description contains first the protocol definitions and second the services provided by the layer 2 to
the layer 3.
2 Normative references
This GTS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this GTS only when incorporated in it by amendment or revision. For undated references, the
latest edition of the publication referred to applies.
[1] GSM 01.04 (ETR 350): "Digital cellular telecommunications system (Phase 2+);
Abbreviations and acronyms".
[2] GSM 08.51: "Digital cellular telecommunications system; Base Station Controller
- Base Transceiver Station (BSC - BTS) interface; General aspects".
[3] GSM 08.52: "Digital cellular telecommunications system; Base Station Controller
- Base Transceiver Station (BSC - BTS) interface; Interface principles".
[4] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunications system
(Phase 2); Objectives and structure of Network Management (NM)".
(Phase 2); Common aspects of GSM Network Management (NM)".
(Phase 2); Operations and performance management".
[7] GSM 12.02 (ETS 300 613): "Digital cellular telecommunications system
(Phase 2); Subscriber, Mobile Equipment (ME) and services data
administration".
(Phase 2); Security management".
(Phase 2); Performance data measurements".
(Phase 2); Subscriber related event and call data".
(Phase 2); GSM Network change control".
(Phase 2); Maintenance of the Base Station System (BSS)".
(Phase 2); Network Management (NM) procedures and messages".
Page 8
(Phase 2); Network Management (NM) procedures and message on the A-bis
interface".
(Phase 2); Interworking of GSM Network Management (NM) procedures and
messages at the Base Station Controller (BSC)".
[16] CCITT Recommendation Q.921: "Integrated services digital network (ISDN)

user-network interface - Data link layer specification".
[17] ETS 300 125: "Integrated Services Digital Network (ISDN); User-network
interface data link layer specification Application of CCITT Recommendations
Q.920/I.440 and Q.921/I.441".
3 Definitions and abbreviations

The following abbreviations and acronyms are used in this GTS.
Ai Action indicator
BCF Base Station Control Function
BSC Base Station Controller
BTS Base Transceiver Station
C/R Command/Response field bit
GSM Global System for Mobile communication
L2ML Layer 2 Management Link
LAPD Link Access Procedure on the D-Channel
MPH- Communication between Management and PHysical layer
MS Mobile Station
N(S) Send sequence variable
O&M Operation and Maintenance
OML Operation and Maintenance Link
PH- Communication between data link layer and PHysical layer
PLMN Public Land Mobile Network
Ri Reference number
RSL Radio Signalling Link
SAP Service Access Point
SAPI Service Access Point Identifier
SMS Short Message Service
TEI Terminal Endpoint Identifier
TRX Transceiver
XID EXchange IDentification
4 General description
The following information categories are supported by the procedures of this layer 2 Recommendation:
- signalling (including Short Message Service (SMS) information);

- operation and maintenance;
- layer 2 management.
For each of these categories the BSC may have one or more layer 2 links to every TRX and BCF.
The signalling links over the A-bis interface are addressed to the different units by Terminal Endpoint
Identifiers (TEI).
The same unit will normally have more than one functional entity. The logical links between different
functional entities are identified by functional addresses, the Service Access Points Identifier (SAPI).
Figure 1 shows the architectural model with different layer 2 links.

Page 9
A number of logical links may be multiplexed on each physical link. The same layer 2 logical link may not
be distributed over more than one physical link.
RSL SAPI = 0
OML SAPI = 62 TRX TEI 1
L2ML SAPI = 63
LAYER 2
RSL SAPI = 0 TRX TEI 2

OML SAPI = 62
L2ML SAPI = 63
TEI
RSL SAPI = 0
OML SAPI = 62
L2ML SAPI = 63 TRX TEI 3
MANAGE-
MENT
OML SAPI = 62
L2ML SAPI = 63 BCF TEI 4
OML SAPI = 62 TEI 65

L2ML SAPI = 63
Figure 1: An example of Logical Layer 2 links supported by three permanent

and one semipermanent links
5 Functional contents
The basic functional content of the layer 2 protocol is:
- transparent layer 2 links and time fill;

- point-to-point dedicated layer 2 links addressing both physical entities and functional entities;
- point-to-multipoint addressed links used for layer 2 management;
- basic functions for TEI assignment and management;
- basic priority functions;
- basic supervision of links when not carrying traffic;
- sequence control;
- transmission error control;
- control of errors not recoverable by retransmission.
6 LAPD functions
The LAPD functions as specified in ETS 300 125 are applicable. However, the exceptions and
modifications specified in the remainder of this specification shall be used.
Page 10
6.1 Exceptions and modifications
In the following headlines from ETS 300 125 are kept and references are made to the corresponding
subclause of ETS 300 125.
6.1.2 Command/Response field bit (C/R)
(Refer to ETS 300 125, part 2, subclause 3.3.2.)

In GSM PLMN's BSC represents the network side and TRX/BCF the user side of the interface.
6.1.3 Service Access Point Identifier (SAPI)

The SAPI values for the A-bis interface are as listed in table 1.
Table 1: Allocation of SAPI values and priority classes
SAPI Related layer 3 or layer management entity Priority

value
0 Radio signalling procedures 2
1 Reserved for packet mode communications using Q.931 -
call control procedures (not used in GSM PLMN)
16 Reserved for packet communication conforming to X.25 -
level 3 procedures (not used in GSM PLMN)
62 Operation and maintenance procedures 1
63 Layer 2 management procedures 1
All others Reserved for future standardization -
6.1.4 TEI for point-to-point data link connection
(Refer to ETS 300 125, part 2, subclause 3.3.4.2.)

The remaining Terminal Endpoint Identifier (TEI) values are used for the point-to-point data link
connections associated with the addressed Service Access Point (SAP). The range of TEI values shall be
allocated as shown in table 2.
Table 2: Allocation of TEI values
TEI User type

value
0 - 63 TEI assignment for fixed TRX and BCF addresses.
64 - 126 EI assignment for additional, TRX or BCF addresses.
NOTE: A BCF is given a separate layer 2 link only if it is not integrated with a TRX.
6.1.5 Commands and responses

The XID command and response are not used.
6.1.6 Exchange identification (XID) command/response

This functionality is not used.
6.1.7 MDL-XID

This functionality is not used.
Page 11
6.1.8 PH-DATA, PH DEACTIVATE and PH-ACTIVATE
(Refer to ETS 300 125, part 2, subclauses 4.1.1.10 - 4.1.1.12).

This functionality is not relevant.
6.1.9 MPH-ACTIVATE, MPH-DEACTIVATE an MPH-INFORMATION
(Refer to ETS 300 125, part 2, subclauses 4.1.1.13 - 4.1.1.15.)

This functionality is not relevant.
6.1.10 Priority indicator

The different SAPIs are given the priority classes as listed in table 1 when contending (with priority one as
the highest).
6.1.11 Terminal Endpoint Identifier (TEI) management procedures
(Refer to ETS 300 125, part 2, subclause 5.3.)

Due to the special assignment functions needed on the A-bis interface there are modifications and
additions to the assignment procedures. The rest of subclause 5.3 in ETS 300 125, part 2, is kept if not
stated otherwise.
6.1.11.1 General

TEI management for A-bis interface is based on the following procedural means:
- a Subset of the TEI assignment procedures;

- the TEI check procedures;
- the TEI remove procedures;
- an additional TEI assignment procedure.
The TEI management needs procedures to check the used TEI values and procedures for reaction in
situation where more than one TRX equipment uses the same TEI value. In addition to the fixed values it
shall be possible to use additional TEI value to the same TRX equipment and thus increase the signalling
capacity.
6.1.11.2 TEI assignment procedure

The TEI assignment procedure used on the A-bis interface has some additions to the automatic TEI
assignment procedure specified in ETS 300 125, part 2.
To facilitate the configuration control in the BSC each TRX will have a fixed TEI and possibly get access to
one or more additional TEIs assigning physical channels/layer 2 links.
The layer 2 links may all be turned on and off according to the normal automatic TEI assignment scheme
but the TRX may only request identified TEI values which is (semi-) permanently programmed or
programmed by operation and maintenance messages.
In GSM the reference number Ri is not used. It is only misoperation situations resulting from double
failures that could be prevented/solved faster by this parameter. The marginal advantage is not supposed
to motivate the application of a random generator and the checking procedure.
The subset of the automatic assignment procedure applicable for the first layer 2 link to a TRX shall have
the following modifications to ETS 300 125, part 2:
- the identity request shall have an Ai value in the range 0-63 identifying the TEI value which is
requested for activation;
Page 12
- on reception of the identity request message the BSC will check that the requested TEI may be
used from the configurations aspects and then perform a normal TEI check procedure to prevent a
double assignment;
- if the TEI request is accepted an identity assigned message with the requested TEI number is
received by TRX before the expiry of timer T202;
- a successful assignment procedure is shown in figure 2.
75;%6&
··
··,GHQWLW\UHTXHVW$L·
···
··,GHQWLW\FKHFNUHTXHVW$L·
······
··1RUPDO··
···LGHQWLW\···
7··FKHFN··7
···SURFHGXUH···
··1RDQVZHU··
·····
9·,GHQWLW\DVVLJQHG$L·9
··
If timer T201 expires the request shall be repeated once and timer T201 restarted
Figure 2: A successful assignment procedure
If timer T202 expires the assignment procedure did not succeed, and the TRX will take further actions in
accordance with the procedures as specified in ETS 300 125, part 2.
If within the assignment procedure an identity check response is received, then the requested TEI value is
already in use. There shall be no answer to the requesting TRX and an error indication shall be sent to
O&M.
An example of a non-successful assignment procedure is shown in figure 3.
75;%6&
··
···
7··,GHQWLW\FKHFNUHTXHVW$L·
····7
··,GHQWLW\FKHFNUHVSRQVH$L·9
···
9··
··
If timer T201 expires the request shall be repeated once and timer T201 restarted.
Figure 3: An example of assignment in error case (TEI value already in use)
The additional TEI assignment procedure is equivalent to the normal one with two exceptions:
- the TEI value is in the range: 64-126;
- the TEI value and the identification of which physical link it shall operate on is transmitted to the
TRX from BSC in an operation and maintenance message. This layer 3 O&M message is
transferred on an already assigned layer 2 link. (See 12-series of GSM Technical Specifications.)
The successful additional assignment procedure is shown in figure 4.

Page 13
75;%6&
··
·2 0FRPPDQG$LSK\VLFDODGGUHVV·
···
···
··,GHQWLW\FKHFNUHTXHVW$L·
······
··,GHQWLW\FKHFN··
7···3URFHGXUH···7
··ZLWKQRUHVSRQVHIURP··
···WKH75;VLGH···
····
9·,GHQWLW\DVVLJQHG$L·9
··
If timer T201 expires the request shall be repeated once and timer T201 restarted.
Figure 4: The procedure for assigning an additional TEI to a TRX or BCF
6.1.11.3 TEI identity verify procedure

This procedure is not used.
6.1.11.4 Formats and codes.

All messages except Identity verify and Identity denied are used. The Ai is used as described in subclause
6.1.11.2, the modification to ETS 300 125, part 2, subclause 5.3.2. The Ri parameter is not used and will
always be coded 0000 0000.
The coding of each field of the various messages is specified in table 3.

Page 14
Table 3: Codes for messages concerning TEI management procedures
Message name Layer Reference Message Action indicator Ai

management number Ri type
entity
identifier
Identity request 0000 1111 Not used 0000 0001 Ai = 0-126

(user to network) (coded 0)
Identity assigned 0000 1111 Not used 0000 0010 Ai = 0-126

(network to user) (coded 0) Assigned TEI value
Identity Ai = 127
check request 0000 1111 Not used Check all TEI values
(network to user) (coded 0) 0000 0100 ---------------------------------
Ai = 0-126
TEI value to be
checked
Identity Ai = 0-126
check response 0000 1111 Not used 0000 0101 TEI value in use
(user to network) (coded 0)
Identity remove 0000 1111 Not used 0000 0110 Ai = 127

(network to user) (coded 0) Request for removal
of all TEI values
---------------------------------
Ai = 0-126
TEI value to be
removed
6.1.12 Automatic negotiation of data link layer parameters
(Refer to ETS 300 125, part 2, subclause 5.4 and annex IV.)
The procedures are not supported.
6.1.13 Establishment procedures

The timer T203 shall be implemented in the equipment on both sides of interface A-bis.
6.1.14 N(S) sequence error
(Refer to ETS 300 125, part 2, subclause 5.8.1 and appendix I.)
As it is the case in ETS 300 125, the optional procedure for retransmission as described in Appendix I is
not supported.
6.1.15 List of system parameters

All the default values are given in the following subclauses.
Page 15
6.1.15.1 Timer T200

The default value of timer T200 is 240 ms starting from the end of a transmitted frame.
NOTE: This timer depends on the timer values used for supervising the message flow
between the Mobile Station (MS) and the network. The proper operation of the
procedure requires timer T200 to be greater than the maximum time between
transmission of command frames and the reception of their corresponding response or
acknowledgement frames and shorter than the shortest layer 3 timer used for
supervising this message flow.
6.1.15.2 Maximum number of retransmissions (N200)

The default value of (N200) is 3.
6.1.15.3 Maximum number of octets in an information field (N201)

The default and maximum value of (N201) is 260 octets for all SAPI values.
6.1.15.4 Maximum number of transmission of the TEI identity request message (N202)

Not used (i.e. equivalent to infinity).
6.1.15.5 Maximum number of outstanding frames (K)

For the SAPI value 0 identifying radio signalling the default (K) value shall be 2. For all other SAPIs the
value shall be set to the fixed value of 1.
NOTE: The value of K for SAPI value 0 shall always be greater than the k value for the other
SAPIs.
6.1.15.6 Timer T201

Timer T201 shall have the default value 1 second.
6.1.15.7 Timer T202

The minimum time between the transmission of TEI Identity request messages is a system parameter
(T202) which shall be set to 15 seconds.
6.1.15.8 Timer T203

The timer T203 represents the maximum time allowed without frames being exchanged for each TEI. The
value of timer T203 shall be 10 seconds.
6.1.16 Data link layer monitor function

The supervisory function will be used in the equipment on both sides of the A-bis interface.
6.1.17 Miscellaneous
(Refer to ETS 300 125, part 2, appendix I-IV.)

The functionalities specified in appendix I-IV of ETS 300 125, part 2, is not used.
Page 16
History
Document history
December 1996 Publication of GSM 08.56 version 5.0.0
ISBN 2-7437-1209-0
Dépôt légal : Décembre 1996

GSM T S

Uploaded by

Copyright:

Available Formats

GSM T S

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GSM T S

Uploaded by

Copyright:

Available Formats

GSM GSM 08.

SPECIFICATION Version 5.0.0

Source: ETSI TC-SMG Reference: TS/SMG-030856Q

GLOBAL SYSTEM FOR

Digital cellular telecommunications system;

© European Telecommunications Standards Institute 1996. All rights reserved.

3 Definitions and abbreviations ..............................................................................................................8

4 General description .............................................................................................................................8

5 Functional contents .............................................................................................................................9

[16] CCITT Recommendation Q.921: "Integrated services digital network (ISDN)

3 Definitions and abbreviations

- signalling (including Short Message Service (SMS) information);

Figure 1 shows the architectural model with different layer 2 links.

RSL SAPI = 0 TRX TEI 2

OML SAPI = 62 TEI 65

Figure 1: An example of Logical Layer 2 links supported by three permanent

- transparent layer 2 links and time fill;

6.1 Exceptions and modifications

6.1.2 Command/Response field bit (C/R)

(Refer to ETS 300 125, part 2, subclause 3.3.2.)

6.1.3 Service Access Point Identifier (SAPI)

(Refer to ETS 300 125, part 2, subclause 3.3.3.)

Table 1: Allocation of SAPI values and priority classes

SAPI Related layer 3 or layer management entity Priority

6.1.4 TEI for point-to-point data link connection

(Refer to ETS 300 125, part 2, subclause 3.3.4.2.)

Table 2: Allocation of TEI values

TEI User type

6.1.5 Commands and responses

(Refer to ETS 300 125, part 2, subclause 3.6.1.)

6.1.6 Exchange identification (XID) command/response

(Refer to ETS 300 125, part 2, subclause 3.6.12.)

(Refer to ETS 300 125, part 2, subclause 4.1.1.9.)

6.1.8 PH-DATA, PH DEACTIVATE and PH-ACTIVATE

(Refer to ETS 300 125, part 2, subclauses 4.1.1.10 - 4.1.1.12).

6.1.9 MPH-ACTIVATE, MPH-DEACTIVATE an MPH-INFORMATION

(Refer to ETS 300 125, part 2, subclauses 4.1.1.13 - 4.1.1.15.)

6.1.10 Priority indicator

(Refer to ETS 300 125, part 2, subclause 4.1.3.1.)

6.1.11 Terminal Endpoint Identifier (TEI) management procedures

(Refer to ETS 300 125, part 2, subclause 5.3.)

(Refer to ETS 300 125, part 2, subclause 5.3.1.)

- a Subset of the TEI assignment procedures;

6.1.11.2 TEI assignment procedure

(Refer to ETS 300 125, part 2, subclause 5.3.2.)

- a successful assignment procedure is shown in figure 2.

Figure 2: A successful assignment procedure

An example of a non-successful assignment procedure is shown in figure 3.

Figure 3: An example of assignment in error case (TEI value already in use)

- the TEI value is in the range: 64-126;

The successful additional assignment procedure is shown in figure 4.

Figure 4: The procedure for assigning an additional TEI to a TRX or BCF

6.1.11.3 TEI identity verify procedure

(Refer to ETS 300 125, part 2, subclause 5.3.5.)

6.1.11.4 Formats and codes.

(Refer to ETS 300 125, part 2, subclause 5.3.6.)

The coding of each field of the various messages is specified in table 3.

Table 3: Codes for messages concerning TEI management procedures

Message name Layer Reference Message Action indicator Ai