5 Document structure of physical layer specification
25.2013GPPPhysical layer - general descriptionRelease 17TS
5.1 Overview
The physical layer specification consists of a general document (TS 25.201), five FDD mode documents (TS 25.211 through 25.215), five TDD mode documents (TS 25.221 through 25.225). In addition, there are two technical reports (TR 25.833 and 25.944).
5.2 TS 25.201: Physical layer – General description
The scope is to describe:
– the contents of the Layer 1documents (TS 25.200 series);
– where to find information;
– a general description of Layer 1.
5.3 TS 25.211: Physical channels and mapping of transport channels onto physical channels (FDD)
The scope is to establish the characteristics of the Layer-1 transport channels and physical channels in the FDD mode, and to specify:
– the different transport channels that exist;
– which physical channels exist;
– what is the structure of each physical channel, slot format etc.;
– relative timing between different physical channels in the same link, and relative timing between uplink and downlink;
– mapping of transport channels onto the physical channels.
5.4 TS 25.212: Multiplexing and channel coding (FDD)
The scope is to describe multiplexing, channel coding and interleaving in the FDD mode, and to specify:
– coding and multiplexing of transport channels into CCTrCHs;
– channel coding alternatives;
– coding for Layer 1 control information, such as TFCI;
– the different interleavers;
– how is rate matching done;
– physical channel segmentation and mapping.
5.5 TS 25.213: Spreading and modulation (FDD)
The scope is to establish the characteristics of the spreading and modulation in the FDD mode, and to specify:
– the spreading (channelisation plus scrambling);
– generation of channelisation and scrambling codes;
– generation of RACH preamble codes;
– generation of SCH synchronisation codes;
– modulation.
RF channel arrangements and Pulse shaping are specified in TS 25.101 for UE and in TS 25.104 for Node-B.
5.6 TS 25.214: Physical layer procedures (FDD)
The scope is to establish the characteristics of the physical layer procedures in the FDD mode, and to specify:
– cell search procedures;
– power control procedures;
– random access procedure.
5.7 TS 25.215: Physical layer – Measurements (FDD)
The scope is to establish the characteristics of the physical layer measurements in the FDD mode, and to specify:
– the measurements that Layer 1 is to perform;
– reporting of measurements to higher layers and network;
– handover measurements, idle-mode measurements etc.
5.8 TS 25.221: Physical channels and mapping of transport channels onto physical channels (TDD)
The scope is to establish the characteristics of the Layer-1 transport channels and physical channels in the TDD mode, and to specify:
– transport channels;
– physical channels, structure and contents;
– mapping of transport channels onto the physical channels.
5.9 TS 25.222: Multiplexing and channel coding (TDD)
The scope is to describe multiplexing, channel coding and interleaving in the TDD mode, and to specify:
– channel coding and multiplexing of transport channels into CCTrCHs;
– channel coding alternatives;
– coding for Layer 1 control information, such as TFCI;
– interleaving;
– rate matching;
– physical channel segmentation and mapping.
5.10 TS 25.223: Spreading and modulation (TDD)
The scope is to establish the characteristics of the spreading and modulation in the TDD mode, and to specify:
– data modulation;
– spreading;
– generation of synchronisation codes.
RF channel arrangements and Pulse shaping are specified in TS 25.102 for UE and in TS 25.105 for Node-B.
5.11 TS 25.224: Physical layer procedures (TDD)
The scope is to establish the characteristics of the physical layer procedures in the TDD mode, and to specify:
– cell synchronisation;
– timing advance;
– power control procedures;
– idle mode tasks.
5.12 TS 25.225: Physical layer – Measurements (TDD)
The scope is to establish the characteristics of the physical layer measurements in the TDD mode, and to specify:
– the measurements that Layer 1 is to perform;
– reporting of measurements to higher layers and network;
– handover measurements, idle-mode measurements etc.
5.13 TR 25.833: Physical layer items not for inclusion in Release ’99
The scope is to collect materials on UTRA physical layer items not included in the Release ’99 specification documents, such as DSCH control channel, FAUSCH, Hybrid ARQ, 4-state SCCC turbo coding and ODMA.
5.14 TR 25.944: Channel coding and multiplexing examples
The scope is to describe examples of channel coding and multiplexing for transport channels of various types and cases.
Annex A (informative):
Preferred mathematical notations
The following table contains the preferred mathematical notations used in L1 documentation.
|
Item |
Notation |
|---|---|
|
multiply product |
cross sign, e.g. ab |
|
matrix product |
dot sign, e.g. ab |
|
scalar product (product of a matrix by a scalar) |
dot sign, scalar should precede matrix e.g. |
|
matrix dimensioning |
number of rows number of column, e.g.: RC |
|
Kronecker product |
ab |
|
bracketing of sets (all elements of same type, not ordered elements) |
curly brackets {}, e.g. {a1, a2, …,ap}, or |
|
bracketing of lists (all elements not necessary of same type, ordered elements) |
round brackets (), e.g. (A, u, x) |
|
bracketing of sequences (all elements of same type, ordered elements) |
angle brackets, e.g. <a1, a2, …,ap> or |
|
bracketing of function argument |
round brackets, e.g. f(x) |
|
bracketing of array index |
square brackets, e.g. a[x] |
|
bracketing of matrix or vector |
square brackets [], e.g. |
|
Separation of indexes |
use a comma : e.g. Ni,j |
|
use of italic for symbols |
a symbol should be either in italic or in normal font, but mixing up should be avoided. |
|
bracketing of arithmetic expression to force precedence of operations |
round brackets : e.g. |
|
necessity of bracketing arithmetic expressions |
When only + and bracketing is not necessary. When the mod operator is used explicit bracketing of mod operands and possibly result should be done. |
|
number type |
in a context of non negative integer numbers, some notes should stress when a number is signed, or possibly fractional. |
|
binary xor and and |
respectively use + or . If no "mod 2" is explicitly in the expression some text should stress that the operation is modulo 2. |
|
matrix or vector transpose |
vT |
|
11 matrices |
implicitly cast to its unique element. |
|
vector dot product |
uTv for column vectors, and uvT for line vectors |
|
complex conjugate |
v* |
|
matrix or vector Hermitian transpose |
vH |
|
real part and imaginary part of complex numbers. |
Re(x) and Im(x) |
, 
, or 
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
RAN_05 |
RP-99586 |
– |
Approved at TSG RAN #5 and placed under Change Control |
– |
3.0.0 |
||
|
14/01/00 |
– |
– |
– |
Modified in terms of formality. The contents were not changed. |
3.0.0 |
3.0.1 |
|
|
31/03/00 |
RAN_07 |
RP-000059 |
001 |
– |
Editorial revision |
3.0.1 |
3.0.2 |
|
26/06/00 |
RAN_08 |
RP-000264 |
002 |
– |
Corrections to align with TS 25.212 and TR 25.944 |
3.0.2 |
3.1.0 |
|
26/06/00 |
RAN_08 |
RP-000264 |
003 |
1 |
Editorial corrections |
3.0.2 |
3.1.0 |
|
26/06/00 |
RAN_08 |
RP-000264 |
004 |
– |
Physical layer information flow |
3.0.2 |
3.1.0 |
|
26/06/00 |
RAN_08 |
RP-000264 |
005 |
1 |
Preferred mathematical notation for editorial unity of L1 documentation |
3.0.2 |
3.1.0 |
|
16/03/01 |
RAN_11 |
– |
– |
– |
Approved as Release 4 specification (v4.0.0) at TSG RAN #11 |
3.1.0 |
4.0.0 |
|
16/03/01 |
RAN_11 |
RP-010071 |
006 |
1 |
Inclusion of 1.28Mcps TDD in TS 25.201 |
3.1.0 |
4.0.0 |
|
14/12/01 |
RAN_14 |
RP-010735 |
008 |
– |
Removal of slow power control and ODMA from TS 25.201 |
4.0.0 |
4.1.0 |
|
08/03/02 |
RAN_15 |
RP-020231 |
010 |
1 |
Removal of channel coding option "no coding" for FDD |
4.1.0 |
4.2.0 |
|
08/03/02 |
RAN_15 |
RP-020058 |
013 |
– |
Specification of HS-DSCH for Release 5 in 25.201 |
4.1.0 |
5.0.0 |
|
07/06/02 |
RAN_16 |
RP-020306 |
017 |
– |
Downlink bit mapping |
5.0.0 |
5.1.0 |
|
10/09/02 |
RAN_17 |
RP-020580 |
018 |
Correction on the description of TS and layer |
5.1.0 |
5.2.0 |
|
|
13/01/04 |
RAN_22 |
– |
– |
– |
Created for M.1457 update |
5.2.0 |
6.0.0 |
|
13/12/04 |
RAN_26 |
RP-040449 |
019 |
– |
Introduction of E-DCH |
6.0.0 |
6.1.0 |
|
16/06/05 |
RAN_28 |
RP-050250 |
021 |
– |
Feature Clean Up: Removal of "CPCH" |
6.1.0 |
6.2.0 |
|
20/03/06 |
RAN_31 |
RP-060079 |
0023 |
– |
Introduction of 7.68Mcps TDD option |
6.2.0 |
7.0.0 |
|
29/09/06 |
RAN_33 |
RP-060492 |
0025 |
– |
Introduction of E-DCH for 3.84Mcps and 7.68Mcps TDD |
7.0.0 |
7.1.0 |
|
07/03/07 |
RAN_35 |
RP-070115 |
031 |
– |
Introduction of CPC related functionality |
7.1.0 |
7.2.0 |
|
07/03/07 |
RAN_35 |
RP-070114 |
032 |
– |
Introduction of MIMO |
7.1.0 |
7.2.0 |
|
07/03/07 |
RAN_35 |
RP-070118 |
028 |
– |
Introduction of E-DCH for 1.28Mcps TDD |
7.1.0 |
7.2.0 |
|
07/03/07 |
RAN_35 |
RP-070116 |
026 |
2 |
Introduction of 64QAM for HSDPA |
7.1.0 |
7.2.0 |
|
30/05/07 |
RAN_36 |
RP-070388 |
027 |
2 |
Introduction of 16QAM for HSUPA |
7.2.0 |
7.3.0 |
|
30/05/07 |
RAN_36 |
RP-070385 |
029 |
1 |
Support for MBSFN operation |
7.2.0 |
7.3.0 |
|
30/05/07 |
RAN_36 |
RP-070384 |
030 |
1 |
Support for DL only SFN operation for MBMS FDD |
7.2.0 |
7.3.0 |
|
30/05/07 |
RAN_36 |
RP-070386 |
034 |
– |
Support for 1.28Mcps TDD MBSFN operation |
7.2.0 |
7.3.0 |
|
11/09/07 |
RAN_37 |
RP-070640 |
0035 |
1 |
Minor modification related to EDCH in 1.28Mcps TDD |
7.3.0 |
7.4.0 |
|
27/11/07 |
RAN_38 |
RP-070943 |
0037 |
1 |
More improvement on dedicated carrier for 1.28Mcps TDD MBMS |
7.4.0 |
7.5.0 |
|
04/03/08 |
RAN_39 |
– |
– |
– |
Release 8 version created further to RAN_39 decision |
7.5.0 |
8.0.0 |
|
28/05/08 |
RAN_40 |
RP-080356 |
0039 |
– |
Introduction 64QAM for 1.28Mcps TDD HSDPA |
8.0.0 |
8.1.0 |
|
18/09/09 |
RAN_45 |
– |
– |
– |
Release 9 version created further to RAN_45 decision |
8.1.0 |
9.0.0 |
|
21/03/11 |
SP-51 |
– |
– |
– |
Release 10 version created further to SP-51 decision |
9.0.0 |
10.0.0 |
|
2012-09 |
SP-57 |
– |
– |
– |
Update to Rel-11 version (MCC) |
10.0.0 |
11.0.0 |
|
04/12/12 |
RAN_58 |
RP-121845 |
0040 |
– |
Introduction of uplink MIMO and 64QAM |
11.0.0 |
11.1.0 |
|
2014-09 |
SP_65 |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.1.0 |
12.0.0 |
|
2015-12 |
SP_70 |
– |
– |
– |
Update to Rel-13 version (MCC) |
12.0.0 |
13.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
RP-75 |
– |
– |
– |
– |
Promotion to Release 14 without technical change (MCC) |
14.0.0 |
|
2018-06 |
RP-80 |
– |
– |
– |
– |
Promotion to Release 15 without technical change (MCC) |
15.0.0 |
|
2020-07 |
RP-88e- |
– |
– |
– |
– |
Upgrade to Rel-16 version without technical change |
16.0.0 |
|
2022-03 |
RP-95e- |
– |
– |
– |
– |
Upgrade to Rel-17 version without technical change |
17.0.0 |
-
MBSFN transmission is characterised by a group of synchronised base stations transmitting the same wave form by using a common scrambling code ↑