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

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

TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Layer 1;
Geneneral Requirements
(3GPP TS 44.0.004 version 13.0.0 Release 13 13)

R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS
3GPP TS 44.004 version 13.0.0 Release 13 1 ETSI TS 144 004 V13.0.0 (2016-01)

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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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
3GPP TS 44.004 version 13.0.0 Release 13 2 ETSI TS 144 004 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
3GPP TS 44.004 version 13.0.0 Release 13 3 ETSI TS 144 004 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
1a References . 7
2 Interfaces to the physical layer . 8
2.1 Interface to the Data Link Layer . 9
2.1a Interface to the Radio Link Control and Medium Access Control layer . 9
2.1b Flexible Layer One Interface to the Radio Link Control and Medium Access Control layer . 9
2.2 Interface to radio resource management . 10
2.3 Interface to other functional units . 10
3 Service of the physical layer . 10
3.1 Service Access Point . 10
3.2 Service of the physical layer. 12
3.2.1 Specific services of the physical layer in the MS . 13
4 Primitives of the physical layer . 13
4.1 Generic names of primitives between layers 1 and 2 for the transfer of layer 2 frames and RLC/MAC
blocks . 14
4.2 Generic names of primitives between layer 1 and the RR-management entity of layer 3 . 14
4.3 Primitive types . 14
4.4 Parameter definition . 15
5 Physical layer procedures . 16
5.0 General . 16
5.1 States of the physical layer . 16
5.2 Control procedures . 18
5.3 Physical layer interface procedures . 18
6 Physical layer protocol header . 18
6.0 General . 18
6.1 Physical layer protocol fields and procedures . 18
7 Block transmission . 19
7.0 General . 19
7.1 SACCH downlink block format . 19
7.1.1 A/Gb mode. 19
7.1.2 Iu mode . 20
7.2 SACCH uplink block format . 21
7.2.1 A/Gb mode. 21
7.2.2 Iu mode . 21
7.3 FACCH/SDCCH/CCCH/BCCH/CBCH downlink block format . 21
7.3.1 CCCH/BCCH/CBCH downlink block format . 21
7.3.2 FACCH/SDCCH downlink block format . 22
7.3.2.1 A/Gb mode . 22
7.3.2.2 Iu mode . 22
7.4 FACCH/SDCCH uplink block format . 23
7.4.1 A/Gb mode. 23
7.4.2 Iu mode . 23
7.4a RACH uplink / Uplink access burst block format . 23
7.5 PBCCH/PCCCH downlink/PACCH block format . 24
7.6 PDTCH block formats . 25
7.6.1 PDTCH block type 1 (CS-1) format . 25
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 4 ETSI TS 144 004 V13.0.0 (2016-01)
7.6.2 PDTCH block type 2 (CS-2) format . 25
7.6.3 PDTCH block type 3 (CS-3) format . 26
7.6.4 PDTCH block type 4 (CS-4) format . 26
7.6.5 PDTCH block type 5 (MCS-1) format . 26
7.6.6 PDTCH block type 6 (MCS-2) format . 27
7.6.7 PDTCH block type 7 (MCS-3) format . 27
7.6.8 PDTCH block type 8 (MCS-4) format . 28
7.6.9 PDTCH block type 9 (MCS-5) format . 28
7.6.9.1 Uplink . 28
7.6.9.2 Downlink . 29
7.6.10 PDTCH block type 10 (MCS-6) format . 29
7.6.10.1 Uplink . 29
7.6.10.2 Downlink . 29
7.6.11 PDTCH block type 11 (MCS-7) format . 30
7.6.11.1 Uplink . 30
7.6.11.2 Downlink . 30
7.6.12 PDTCH block type 12 (MCS-8) format . 31
7.6.12.1 Uplink . 31
7.6.12.2 Downlink . 31
7.6.13 PDTCH block type 13 (MCS-9) format . 32
7.6.13.1 Uplink . 32
7.6.13.2 Downlink . 32
7.6.14 PDTCH block type 14 (UAS-7) format (uplink only) . 33
7.6.15 PDTCH block type 15 (UAS-8) format (uplink only) . 33
7.6.16 PDTCH block type 16 (UAS-9) format (uplink only) . 34
7.6.17 PDTCH block type 17 (UAS-10) format (uplink only) . 35
7.6.18 PDTCH block type 18 (UAS-11) format (uplink only) . 35
7.6.19 PDTCH block type 19 (UBS-5) format (uplink only) . 36
7.6.20 PDTCH block type 20 (UBS-6) format (uplink only) . 36
7.6.21 PDTCH block type 21 (UBS-7) format (uplink only) . 36
7.6.22 PDTCH block type 22 (UBS-8) format (uplink only) . 37
7.6.23 PDTCH block type 23 (UBS-9) format (uplink only) . 37
7.6.24 PDTCH block type 24 (UBS-10) format (uplink only). 38
7.6.25 PDTCH block type 25 (UBS-11) format (uplink only). 38
7.6.26 PDTCH block type 26 (UBS-12) format (uplink only). 39
7.6.27 PDTCH block type 27 (DAS-5) format (downlink only) . 39
7.6.28 PDTCH block type 28 (DAS-6) format (downlink only) . 40
7.6.29 PDTCH block type 29 (DAS-7) format (downlink only) . 41
7.6.30 PDTCH block type 30 (DAS-8) format (downlink only) . 41
7.6.31 PDTCH block type 31 (DAS-9) format (downlink only) . 42
7.6.32 PDTCH block type 32 (DAS-10) format (downlink only) . 42
7.6.33 PDTCH block type 33 (DAS-11) format (downlink only) . 43
7.6.34 PDTCH block type 34 (DAS-12) format (downlink only) . 43
7.6.35 PDTCH block type 35 (DBS-5) format (downlink only) . 44
7.6.36 PDTCH block type 36 (DBS-6) format (downlink only) . 44
7.6.37 PDTCH block type 37 (DBS-7) format (downlink only) . 44
7.6.38 PDTCH block type 38 (DBS-8) format (downlink only) . 45
7.6.39 PDTCH block type 39 (DBS-9) format (downlink only) . 45
7.6.40 PDTCH block type 40 (DBS-10) format (downlink only) . 46
7.6.41 PDTCH block type 41 (DBS-11) format (downlink only) . 46
7.6.42 PDTCH block type 42 (DBS-12) format (downlink only) . 47
7.7 PRACH uplink/PACCH uplink short acknowledgement block formats . 47
7.8 PTCCH downlink block format . 48
7.9 PTCCH uplink block formats . 49
7.9a Transport block formats (Iu mode) . 49
7.9a.1 Generic transport block format . 49
7.9a.2 Transport block format for signalling TFC . 49
7.10 Order of bit transmission . 50
8 Vocabulary . 50
Annex A (informative): Change History . 53
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 5 ETSI TS 144 004 V13.0.0 (2016-01)
History . 54

ETSI
3GPP TS 44.004 version 13.0.0 Release 13 6 ETSI TS 144 004 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
3GPP TS 44.004 version 13.0.0 Release 13 7 ETSI TS 144 004 V13.0.0 (2016-01)
1 Scope
The present document defines the service offered by the physical layer (3GPP TS 45-series of Technical Specifications)
of the MS-BS interface (3GPP TS 45- and 44-series of Technical Specifications). Its main objective is to be a guidance
for the interface between the 3GPP Technical Specifications in the 45-series and the 44-series. It also specifies the
format of signalling channels and the order of bit transmission.
As far as possible, the present document makes use of the layering principles of the Reference Model for Open System
Interconnection (OSI) as contained in ITU-T Recommendations X.200 and X.210.
1a 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 22.011: "Service accessibility".
[3] 3GPP TS 43.013: "Discontinuous Reception (DRX) in the GSM System".
[4] 3GPP TS 43.020: "Security-related network functions".
[5] Void.
[6] Void.
[7] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures
and access capabilities".
[8] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".
[9] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL)
layer specification".
[10] Void.
[11] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[12] Void.
[13] Void.
[14] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio
interface".
[15] Void.
[16] Void.
[17] Void.
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 8 ETSI TS 144 004 V13.0.0 (2016-01)
[17a] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station
System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
[18] Void.
[19] Void.
[20] Void.
[21] Void.
[22] Void.
[23] Void.
[24] Void.
[25] Void.
[26] Void.
[26a] 3GPP TS 44.118: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC)
Protocol, Iu Mode".
[26b] 3GPP TS 44.160: "Radio Link Control/Medium Access Control (RLC/MAC) protocol, Iu Mode"
[27] 3GPP TS 45.001: "Physical Layer on the Radio Path (General Description)".
[28] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[29] 3GPP TS 45.003: "Channel coding".
[30] Void.
[31] 3GPP TS 45.005: "Radio transmission and reception".
[32] 3GPP TS 45.008: "Radio subsystem link control".
[33] 3GPP TS 45.010: "Radio subsystem synchronization".
[34] Void.
[35] ITU-T Recommendation X.200: "Information technology; Open Systems Interconnection; Basic
Reference Model: The basic model".
[36] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic
Reference Model: Conventions for the definition of OSI services".
[37] 3GPP TS 48.058: 'Base Station Controler - Base Transceiver Station (BCS-BTS) Interface Layer
3 Specification'.
[38] 3GPP TR 45.902: 'Flexible Layer One'.
2 Interfaces to the physical layer
The physical layer (layer 1) is the lowest layer in the OSI Reference Model and it supports all functions required for the
transmission of bit streams on the physical medium. These bit streams are transferred on traffic channels, packet data
traffic channels and control channels as defined in 3GPP TS 44.003.
NOTE: For GSM application the physical layer may also be referred to as the radio subsystem. However, the
radio subsystem supports functions additional to those described in the present document.
The physical layer interfaces the Data Link Layer, the Radio Link Control and Medium Access Control layer and the
supported functional units of the application (figure 2).
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 9 ETSI TS 144 004 V13.0.0 (2016-01)

to upper layers
to other
RR (layer 3)
RRC (layer 3)
functional
units
RLC/MAC layer
Data Link Layer
PH- PH-
MPH- MPH-
TCH
primitives primitives
primitives
primitives
Physical Layer
Figure 2: Interfaces with the Physical Layer
2.1 Interface to the Data Link Layer
The physical layer interfaces the data link layer. On this interface control channels are supported. The data link layer is
specified in 3GPP TS 44.005 and 44.006. Communication between the Physical Layer and the Data Link Layer is in an
abstract way performed by means of PH-primitives. They do not constrain implementations.
NOTE: The terms physical layer and layer 1, and data link layer and layer 2, will be used synonymously in the
present document.
The PH-primitives exchanged between the physical layer and the data link layer are used for the transfer of layer 2
frames. They are also used to indicate the establishment of channels to layer 2.
2.1a Interface to the Radio Link Control and Medium Access
Control layer
The physical layer interfaces the Radio Link Control and Medium Access Control (RLC/MAC) layer. On this interface
packet data control channels and packet data traffic channels are supported when MS is operating in A/Gb mode; when
MS is operating in Iu mode, traffic channels, dedicated control channels, packet data control channels and packet data
traffic channels are supported. The RLC/MAC layer is specified in 3GPP TS 44.060 (A/Gb mode) and 3GPP TS 44.160
(Iu mode). Communication between the Physical Layer and the RLC/MAC layer is in an abstract way performed by
means of PH-primitives. They do not constrain implementations.
The PH-primitives exchanged between the physical layer and the RLC/MAC layer are used for the transfer of
RLC/MAC blocks. They are also used to indicate the establishment of packet data physical channels (A/Gb mode) or
shared basic physical subchannels (Iu mode) to the RLC/MAC layer.
2.1b Flexible Layer One Interface to the Radio Link Control and
Medium Access Control layer
In Iu mode, when the Flexible Layer One is used the physical layer interfaces the Radio Link Control and Medium
Access Control (RLC/MAC) layer (see 3GPP TR 45.902). On this interface transport channels are supported. The
RLC/MAC layer is specified in 3GPP TS 44.160. Communication between the Physical Layer and the RLC/MAC layer
is in an abstract way performed by means of PH-primitives. They do not constrain implementations.
The PH-primitives exchanged between the physical layer and the RLC/MAC layer are used for the transfer of transport
blocks.
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 10 ETSI TS 144 004 V13.0.0 (2016-01)
2.2 Interface to radio resource management
The physical layer interfaces the radio resource management (RR or RRC) entity of layer 3 in the MS and in the
network. When the MS is operating in A/Gb mode the radio resource management is provided by the RR entity whilst
when operating in Iu mode the radio resource management is provided by the RRC entity.
Communication is performed in an abstract way by means of MPH-primitives. They do not constrain implementations.
The primitives exchanged with the RR-management entity are related to the assignment of channels, physical layer
system information (including measurement results), etc.
2.3 Interface to other functional units
The physical layer interfaces other functional units in the MS and in the network for supporting traffic channels. These
interfaces are described in the 26, 27 and 46 series of Technical Specifications.
3 Service of the physical layer
The physical layer supports transfer of bit streams on the radio medium according to the Technical Specifications of the
45-series. The scope of the 45-series of Technical Specifications is the definition of a framework for operation on the
radio medium. The application of this framework on the radio medium results in a transmission service. General
characteristics of the service obtained by applying the framework of the 45-series at the operation on the radio medium
are described in this clause.
3.1 Service Access Point
In the Reference Model for Open System Interconnection, Service Access Points (SAPs) of a layer are defined as gates
through which services are offered to an adjacent higher layer (figure 3.1.a). Through a SAP the physical layer offers a
service to the data link layer. The SAP is used both for the control of the service providing entity (in case this is the
physical layer; commands related to the establishment and release of channels) and the transfer of data (in case of the
physical layer; the transfer of bits). The physical layer service access points defined in the present document differ from
the OSI physical layer Service Access Points; the layer 3 RR-management instead of the data link layer controls the
SAPs (establishment and release of channels).
adjacent higher layer adjacent higher layer
SAP SAP
transmission medium
Figure 3.1.a: Service Access Point principle
On the physical layer of the GSM system a SAP is defined between the physical layer and the data link layer for each
control channel (figure 3.1.b and figure 3.1.b1). The characteristics of SAPs (channels) are listed in 3GPP TS 44.003.
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 11 ETSI TS 144 004 V13.0.0 (2016-01)
Data Link Layer
BCCH PCH+AGCH RACH SDCCH SACCH FACCH
Physical layer
Figure 3.1.b: SAPs between the physical layer and the data link layer when the MS is operating in
A/Gb mode
Data Link layer
BCCH
Physical layer
Figure 3.1.b1: SAPs between the physical layer and the data link layer when the MS is capable of
operating in Iu mode
Moreover, on the physical layer of the GSM system a SAP is defined between the physical layer and the RLC/MAC
layer for the packet data control channels, dedicated control channels (Iu mode), traffic channels (Iu mode) and the
packet data traffic channel and the transport channels (FLO in Iu mode) (see figure 3.1.c, figure 3.1.d and figure 3.1.e).
Multiplexing of these channels is controlled by the RLC/MAC layer, see 3GPP TS 44.060 (A/Gb mode) and 3GPP
TS 44.160 (Iu mode). The characteristics of channels are listed in 3GPP TS 44.003.
RLC/MAC layer
PBCCH + PPCH + PAGCH + PRACH + PACCH + PDTCH
Physical layer
Figure 3.1.c: SAP between the physical layer and the RLC/MAC layer when the MS is operating in
A/Gb mode
PBCCH+PPCH+
RLC/MAC layer
PAGCH+PRACH+
MAC layer
PDTCH+PACCH
SDCCH SACCH TCH FACCH
Physical layer
Figure 3.1.d: SAP between the physical layer and the RLC/MAC layer when the MS is operating in Iu
mode
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 12 ETSI TS 144 004 V13.0.0 (2016-01)

PBCCH+PPCH+
RLC/MAC layer
PAGCH+PRACH+
MAC layer
PDTCH+PACCH
TrCH
SDCCH SACCH TCH FACCH
Physical layer
Figure 3.1.e: SAP between the physical layer and the RLC/MAC layer
when the MS is operating in Iu mode with FLO
3.2 Service of the physical layer
The physical layer offers a transmission service on a limited set of logical channels. Additionally with FLO in Iu mode,
the physical layer offers a transmission service on transport channels. The BS and MS access capabilities and the
characteristics of logical channels (SAPs) are defined in 3GPP TS 44.003.
NOTE: Between 3GPP TS 44.003 and the 3GPP TS 45.0xx series there is a slight difference in terminology. The
"channels" mentioned in 3GPP TS 44.003 are "logical channels" according to the 3GPP TS 45.0xx series
(especially 3GPP TS 45.002). The "CCCH", a channel name commonly used in the 3GPP TS 44.0xx
series, covers the logical channels of the type RACH, PCH and AGCH. Similarly, the 'PCCCH' covers
the logical channels of the type PPCH, PAGCH and PRACH.
For an MS operating in A/Gb mode, logical channels are multiplexed on physical channels. Physical channels are the
units scheduled on the radio medium. Some are reserved by the network for common use (e.g. a combination of CCCH
and BCCH), others are assigned to dedicated connections with MSs (dedicated physical channels), or are assigned to a
shared usage between MSs for packet switched data traffic (packet data physical channels). In time, the combination of
logical channels used on an assigned physical channel may change. Allowed combinations of logical channels on a
physical channel are defined in 3GPP TS 44.003. Data on SAPs of control channels is exchanged in discrete blocks with
a size of 23 or 21 (SACCH) octets. Data on a SAP of packet data traffic channels is exchanged in discrete blocks with a
size dependent on the block type (see clause 7).
For an MS operating in Iu mode, logical channels are multiplexed on basic physical subchannels. Basic physical
subchannels are the units scheduled on the radio medium. Some basic physical channels are reserved by the network for
common use (e.g. BCCH); dedicated basic physical subchannels are assigned to dedicated connections with MSs,
shared basic physical subchannels are assigned to a shared usage between MSs for packet switched data traffic. In time,
the combination of logical channels used on an assigned basic physical subchannel may change. Allowed combinations
of logical channels on a basic physical subchannel are defined in 3GPP TS 44.003. Data on SAPs of control channels is
exchanged in discrete blocks with a size of 23 or 21 (SACCH) octets. Data on a SAP of packet data traffic channels is
exchanged in discrete blocks with a size dependent on the block type (see clause 7).
For an MS operating in Iu mode with FLO, transport channels are multiplexed on dedicated basic physical subchannels.
The combination of transport channels used on an assigned basic physical subchannel may change in time. Data on
SAPs of transport channels is exchanged in discrete transport blocks.
Synchronization between layer 1 and layer 2 (data link layer) is provided for piggy-backing of RR (receive ready)
frames, and the starting of timers (T200). See also 3GPP TS 44.006. Synchronization between the physical layer and the
RLC/MAC layer is provided for the handling of timers, and the multiplexing of logical channels. See also 3GPP TS
44.060 (A/Gb mode) and 3GPP TS 44.160 (Iu mode).
- Error detection:
The physical layer offers an error protected transmission service, it includes error detection functions and to a lower
level, error correction functions. Erroneous received frames are not offered to the data link layer or the RLC/MAC
layer. The probability of one or more errors in a physical block transferred by the physical layer is defined in 3GPP TS
45.005. Due to not specified methods of quality detection, the probability of residual errors in transferred blocks may
vary between implementations.
- Encryption:
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 13 ETSI TS 144 004 V13.0.0 (2016-01)
Security related functions implemented at the physical layer are described in 3GPP TS 43.020.
An overview of the functions specified in the 45-series which create the service of the physical layer can be found in
3GPP TS 45.001.
3.2.1 Specific services of the physical layer in the MS
The access capability service of the physical layer in the MS differs depending on the nature of the channel (traffic,
packet data traffic or broadcast/common channels).
- Establishment of dedicated physical channels (A/Gb Mode):
Establishment of dedicated physical channels on the physical layer is controlled by the radio resources management of
layer 3 (3GPP TS 44.018). During operation on a dedicated physical channel, the physical layer measures the signals of
neighbouring base stations and the signal quality of the used dedicated physical channel. Measurements are transferred
to layer 3, measurement control information is offered by layer 3.
- Establishment of dedicated basic physical subchannels (Iu mode):
Establishment of dedicated basic physical subchannels on the physical layer is controlled by the radio resources
management of layer 3 (3GPP TS 44.018 and 3GPP TS 44.118). During operation on a dedicated basic physical
subchannel, the physical layer measures the signals of neighbouring base stations and the signal quality of the used
dedicated basic physical subchannel. Measurements are transferred to layer 3, measurement control information is
offered by layer 3.
- Establishment of packet data physical channels (A/Gb mode):
Establishment of packet data physical channels on the physical layer is controlled by the radio resource management of
layer 3. Packet access and the reservation of radio resource on packet data physical channels is controlled by the
RLC/MAC layer in co-operation with layer 3 (3GPP TS 44.060 and 3GPP TS 44.118). During operation on packet data
physical channels, the physical layer measures the signals of neighbouring base stations and the signal quality of the
used packet data physical channel. Measurements are transferred to layer 3, measurement control information is offered
by layer 3.
- Establishment of shared basic physical subchannels (Iu mode):
Establishment of shared basic physical subchannels on the physical layer is controlled by the radio resource
management of layer 3. Packet access and the reservation of radio resource on shared basic physical subchannels is
controlled by the RLC/MAC layer in co-operation with layer 3 (3GPP TS 44.160 and 3GPP TS 44.118). During
operation on shared basic physical subchannels, the physical layer measures the signals of neighbouring base stations
and the signal quality of the used shared basic physical subchannel. Measurements are transferred to layer 3,
measurement control information is offered by layer 3.
- cell/PLMN selection in idle mode or in packet mode:
In idle mode or in packet mode, the physical layer selects the best cell with its BCCH/CCCH in close co-operation with
layer 3, meeting requirements for PLMN selection specified in 3GPP TS 22.011. The idle mode procedures are not
modelled within the present document. Examples of procedures for cell selection are described in 3GPP TS 45.008. The
physical layer performs automatic crossover.
4 Primitives of the physical layer
The Physical layer interacts with other entities as illustrated in figure 2.1. The interactions with the data link layer of
Dm channels and the interactions with the RLC/MAC layer of packet data physical channels (A/Gb mode), shared or
dedicated basic physical subchannels (Iu mode) are shown in terms of primitives where the primitives represent the
logical exchange of information and control between the physical layer and adjacent layers. They do not specify or
constrain implementations. The interactions between the physical layer and layer 1 entities for Bm/Lm channels are for
further study. For the physical layer two sets of primitives are defined:
- Primitives between physical layer and data link layer and RLC/MAC layer respectively:
PH - Generic name - Type: Parameters.
ETSI
3GPP TS 44.004 version 13.0.0 Release 13 14 ETSI TS 144 004 V13.0.0 (2016-01)
- Primitives between layer 1 and the RR-management layer 3 entity:
MPH - Generic name - Type: Parameters.
4.1 Generic names of primitives between layers 1 and 2 for the
transfer of layer 2 frames and RLC/MAC blocks
The following primitive generic names are defined on the SAPs between the physical layer and the data link layer:
a) PH-DATA:
The PH-DATA primitives are used on a SAP to pass message units containing frames used for data link layer
and RLC/MAC layer respective peer-to-peer communications to and from the physical layer.
b) PH-RANDOM ACCESS:
The PH-RANDOM ACCESS (PH-RA) primitives are used on the SAP of the RACH and the PRACH to
request and confirm (in the MS) the sending of a random access frame and to indicate (in the network) the
arrival of a random access frame. For MS operating in A/Gb mode, the random access protocols are specified
in 3GPP TS 44.018 and 3GPP TS 44.060 respectively; for MS operating in Iu mode, they are specified in
3GPP TS 44.160.
c) PH-CONNECT:
The PH-CONNECT primitive is used on a SAP to indicate that the physical connection on the corresponding
control channel or packet data physical channel (A/Gb mode) or shared basic physical subchannel (Iu mode)
has been established.
d) PH-READY-TO-SEND:
The PH-READY-TO-SEND primitive is used by the physical layer to trigger, if applicable, piggy backing,
the start of timer for the data link layer or the RLC/MAC layer and the forwarding a data unit to the physical
layer. It is passed to the upper layer just before a new physical block is transmitted.
e) PH-EMPTY-FRAME:
The PH-EMPTY-FRAME primitive can be used by the data link layer and the RLC/MAC layer to indicate
that no frame has to be transmitted after receiving the PH-READY-TO-SEND primitive. It enables polling of
several upper layer entities by the physical layer and support DTX.
4.2 Generic names of primitives between layer 1 and the
RR-management entity of layer 3
The following primitive generic name is defined between layer 1 and the RR-management entity of layer 3:
- MPH-INFORMATION:
MPH-INFORMATION (MPH-INFO) primitives are used for the control of the physical layer by the
RR-management of layer 3. This information activates and deactivates, configures and deconfigures, through
connects and disconnects physical, logical and transport channels. It is also used for the transfer of
measurements and meas
...