You are on page 1of 52

3GPP TS 25.301 V11.0.

0 (2012-09)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Radio Access Network;
Radio Interface Protocol Architecture
(Release 11
The present document has been developed within the 3
rd
Generation Partnership Project (3GPP
TM
) and may be further elaborated for the purposes of 3GPP..
The present document has not been subject to any approval process by the 3GPP

Oranisational Partners and shall not be implemented.
This !pecification is provided for future development wor" within 3GPP

only. The Oranisational Partners accept no liability for any use of this
!pecification.
!pecifications and reports for implementation of the 3GPP
TM
system should be obtained via the 3GPP Oranisational Partners# Publications Offices.
3GPP
$eywords
UMTS, radio, architecture
3GPP
Postal address
3GPP support office address
650 Route de !ucio"e - So#hia $%ti#o"i
Va"&o%%e - 'R$()*
Te".+ ,33 - 92 9- -2 00 'a.+ ,33 - 93 65 -/ 16
%nternet
htt#+00111.32##.or2
Copyright Notification
&o part may be reproduced e'cept as authori(ed by written permission.
The copyriht and the foreoin restriction e'tend to reproduction in all media.
) *+,*- 3GPP Orani(ational Partners (./%0- .T%!- 11!.- 2T!%- TT.- TT1).
.ll rihts reserved.
3MT!4 is a Trade Mar" of 2T!% reistered for the benefit of its members
3GPP4 is a Trade Mar" of 2T!% reistered for the benefit of its Members and of the 3GPP Orani(ational Partners
5T24 is a Trade Mar" of 2T!% currently bein reistered for the benefit of its Members and of the 3GPP
Orani(ational Partners
G!M6 and the G!M loo are reistered and owned by the G!M .ssociation
3GPP TS !"#3$1 %11#$#$ (!$1!&$' ! Release 1$
)o%te%t
7oreword..........................................................................................................................................................
, !cope......................................................................................................................................................
* /eferences..............................................................................................................................................
3 8efinitions and abbreviations.................................................................................................................
3., 8efinitions...........................................................................................................................................................
3.* .bbreviations.......................................................................................................................................................
9 .ssumed 3MT! .rchitecture.................................................................................................................
: /adio interface protocol architecture......................................................................................................
:., Overall protocol structure....................................................................................................................................
:.,., !ervice access points and service primitives...............................................................................................
:.* 5ayer , !ervices and 7unctions.........................................................................................................................
:.*., 5, !ervices...................................................................................................................................................
:.*.,., Transport channels..................................................................................................................................
:.*.* 5, 7unctions................................................................................................................................................
:.3 5ayer * !ervices and 7unctions.........................................................................................................................
:.3., M.1 !ervices and 7unctions......................................................................................................................
:.3.,., M.1 !ervices to upper layers...............................................................................................................
:.3.,.,., 5oical channels...............................................................................................................................
:.3.,.,.* Mappin between loical channels and transport channels..............................................................
:.3.,.,.*., Mappin in 3plin"......................................................................................................................
:.3.,.,.*.* Mappin in 8ownlin".................................................................................................................
:.3.,.* M.1 functions.......................................................................................................................................
:.3.* /51 !ervices and 7unctions........................................................................................................................
:.3.*., !ervices provided to the upper layer......................................................................................................
:.3.*.* /51 7unctions.......................................................................................................................................
:.3.3 P81P !ervices and 7unction.......................................................................................................................
:.3.3., P81P !ervices provided to upper layers................................................................................................
:.3.3.* P81P 7unctions.....................................................................................................................................
:.3.9 0roadcast;Multicast 1ontrol < !ervices and functions.................................................................................
:.3.9., 0M1 !ervices........................................................................................................................................
:.3.9.* 0M1 7unctions......................................................................................................................................
:.3.: 8ata flows throuh 5ayer *.........................................................................................................................
:.3.:., 8ata flow for 011= mapped to 01=...................................................................................................
:.3.:.* 8ata flow for 011= mapped to 7.1=.................................................................................................
:.3.:.3 8ata flow for P11= mapped to P1=....................................................................................................
:.3.:.9 8ata flow for 111= mapped to 7.1=;/.1=.....................................................................................
:.3.:.: 8ata flow for !=11= mapped to 3!1=...............................................................................................
:.3.:.> 8ata flow for !=11= mapped to 7.1=;/.1=...................................................................................
:.3.:.? 8ata flow for 811= mapped to 7.1=;/.1=.....................................................................................
:.3.:.@ 8ata flow for 811= mapped to 8!1=.................................................................................................
:.3.:.A 8ata flow for 811= mapped to 3!1=.................................................................................................
:.3.:.,+ Boid........................................................................................................................................................
:.3.:.,, 8ata flow for 8T1= (non<transparent /51) mapped to 7.1=;/.1=................................................
:.3.:.,* 8ata flow for 8T1= (non<transparent /51) mapped to 8!1=...........................................................
:.3.:.,3 8ata flow for 8T1= (non<transparent /51) mapped to 3!1=...........................................................
:.3.:.,9 8ata flow for 8T1= (transparent /51) mapped to 81=.....................................................................
:.3.:.,: 8ata flow for 8T1= (non<transparent /51) mapped to 81=..............................................................
:.3.:.,> Boid........................................................................................................................................................
:.3.:.,? 8ata flow for 811= mapped to 81=...................................................................................................
:.3.:.,@ 8ata flow for 1T1= mapped to 7.1=..................................................................................................
:.3.:.,A 8ata flow for 811= mapped to =!<8!1=..........................................................................................
:.3.:.*+ 8ata flow for 8T1= (non<transparent /51) mapped to =!<8!1=.....................................................
:.3.:.*, 8ata flow for 811= mapped to 2<81=...............................................................................................
:.3.:.** 8ata flow for 8T1= (non<transparent /51) mapped to 2<81=..........................................................
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3 Release 1$
:.3.:.*3 8ata flow for M11= (non<transparent /51) mapped to 7.1=...........................................................
:.3.:.*9 8ata flow for M!1= (non<transparent /51) mapped to 7.1=...........................................................
:.3.:.*: 8ata flow for MT1= (non<transparent /51) mapped to 7.1=...........................................................
:.3.:.*> 8ata flow for 111= mapped to =!<8!1=;/.1= (788 only)...........................................................
:.3.:.*? 8ata flow for P11= mapped to =!<8!1=...........................................................................................
:.3.:.*@ 8ata flow for 011= mapped to =!<8!1= (788 and ,.*@ Mcps T88 only).....................................
:.3.:.*A 8ata flow for 111= mapped to =!<8!1=;2<81= (788 and ,.*@ Mcps T88 only)........................
:.3.> Transport 1hannel- 5oical 1hannel and M.1<d flow &umberin............................................................
:.9 5ayer 3 < 3u !tratum !ervices and 7unctions...................................................................................................
:.9., 3u !tratum services.....................................................................................................................................
:.9.,., General 1ontrol......................................................................................................................................
:.9.,.* &otification.............................................................................................................................................
:.9.,.3 8edicated 1ontrol..................................................................................................................................
:.9.* //1 functions..............................................................................................................................................
:.: %nteractions between //1 and lower layers in the 1 plane..............................................................................
:.> Protocol termination..........................................................................................................................................
:.>., Protocol termination for 81=......................................................................................................................
:.>.* Protocol termination for /.1=;7.1=.......................................................................................................
:.>.3 Boid..............................................................................................................................................................
:.>.9 Boid..............................................................................................................................................................
:.>.: Protocol termination for 8!1=...................................................................................................................
:.>.:., 8!1= definition.....................................................................................................................................
:.>.:.* /esource allocation and 32 identification on 8!1=............................................................................
:.>.:.*., Boid...................................................................................................................................................
:.>.:.*.* 32 reCuires a downlin" !=11=......................................................................................................
:.>.:.3 Model of 8!1= in 3T/.&...................................................................................................................
:.>.:.9 Protocol termination...............................................................................................................................
:.>.> Protocol termination for transport channel of type 3!1=..........................................................................
:.>.>., 3!1= definition.....................................................................................................................................
:.>.>.* /esource allocation and 32 identification on 3!1=............................................................................
:.>.>.3 Model of 3!1= in 3T/.&...................................................................................................................
:.>.>.9 Protocol termination...............................................................................................................................
:.>.? Protocol termination for transport channel of type 01=.............................................................................
:.>.@ Protocol termination for transport channel of type P1=.............................................................................
:.>.A Protocol termination for =!<8!1=.............................................................................................................
:.>.A., =!<8!1= definition..............................................................................................................................
:.>.A.* /esource allocation and 32 identification on =!<8!1=......................................................................
:.>.A.3 Protocol termination...............................................................................................................................
:.>.,+ Protocol termination for 2<81=..................................................................................................................
:.>.,+., 2<81= definition...................................................................................................................................
:.>.,+.* /esource allocation and 32 identification related to 2<81=................................................................
:.>.,+.3 Protocol termination...............................................................................................................................
:.>.,, Protocol termination for M0M!..................................................................................................................
:.>.,,., M0M! definition...................................................................................................................................
:.>.,,.* /esource allocation related to M0M!...................................................................................................
:.>.,,.3 Protocol termination...............................................................................................................................
> 3ser %dentification and //1 1onnection Mobility...............................................................................
>., 32 identification on the radio interface.............................................................................................................
>.* 32 connection to 3T/.&................................................................................................................................
? 32 modes.............................................................................................................................................
Annex A (informative): Change history..............................................................................................
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' ( Release 1$
'ore1ord
This Technical !pecification (T!) has been produced by the 3
rd
Generation Partnership Project (3GPP).
The contents of the present document are subject to continuin wor" within the T!G and may chane followin formal
T!G approval. !hould the T!G modify the contents of the present document- it will be re<released by the T!G with an
identifyin chane of release date and an increase in version number as followsD
Bersion '.y.(
whereD
' the first diitD
, presented to T!G for informationE
* presented to T!G for approvalE
3 or reater indicates T!G approved document under chane control.
y the second diit is incremented for all chanes of substance- i.e. technical enhancements- corrections-
updates- etc.
( the third diit is incremented when editorial only chanes have been incorporated in the document.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' " Release 1$
1 Sco#e
The present document shall provide an overview and overall description of the 32<3T/.& radio interface protocol
architecture as areed within the 3GPP T!G /.& wor"in roup *. 8etails of the radio protocols will be specified in
companion documents.
2 Re3ere%ce
The followin documents contain provisions which- throuh reference in this te't- constitute provisions of the present
document.
/eferences are either specific (identified by date of publication- edition number- version number- etc.) or
non<specific.
7or a specific reference- subseCuent revisions do not apply.
7or a non<specific reference- the latest version applies. %n the case of a reference to a 3GPP document (includin
a G!M document)- a non<specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
F,G 3GPP T! *3.,,+D H3MT! .ccess !tratumE !ervices and 7unctionsH.
F*G 3GPP T! *:.9+,D H/.& Overall 8escriptionH.
F3G 3GPP T/ *,.A+:D HBocabulary for 3GPP !pecificationsH.
F9G 3GPP T! *:.3+*D H!ervices provided by the Physical 5ayerH.
F:G 3GPP T! *:.3+3D H%nterlayer Procedures in 1onnected ModeH.
F>G 3GPP T! *:.3+9D H32 Procedures in %dle Mode and Procedures for 1ell /eselection in 1onnected
ModeH.
F?G 3GPP T! *:.3*,D HM.1 Protocol !pecificationH.
F@G 3GPP T! *:.3**D H/51 Protocol !pecificationH.
FAG 3GPP T! *:.3*3D HP81P Protocol !pecificationH.
F,+G 3GPP T! *:.3*9D H0M1 Protocol !pecificationH.
F,,G 3GPP T! *:.33,D H//1 Protocol !pecificationH.
F,*G 3GPP T! *:.**9D HPhysical 5ayer Procedures (T88)H.
F,3G 3GPP T! *9.++?D HMobile radio interface sinallin layer 3E General aspectsH.
F,9G 3GPP T! 33.,+:D H1ryptoraphic .lorithm /eCuirementsH.
F,:G 3GPP T! 33.,+*D H!ecurity .rchitectureH.
F,>G 3GPP T! 99.++:D H8ata 5in" (85) layerE General aspectsH.
F,?G 3GPP T! *:.3+@D H3T/. =ih !peed 8ownlin" Pac"et .ccess (=!8P.)E Overall descriptionH.
F,@G 3GPP T! *:.3+AD H 788 2nhanced 3plin"E Overall descriptionH.
F,AG 3GPP T! *:.39>D H%ntroduction of the Multimedia 0roadcast Multicast !ervice (M0M!) in the
/adio .ccess &etwor" (/.&) (!tae<*)H.
F*+G 3GPP T! *:.9*3D H3T/.& %ur interface /&!.P sinallinH.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' ) Release 1$
3 4e3i%itio% a%d a&&re5iatio%
3.1 4e3i%itio%
7or the purposes of the present document- the terms and definitions iven in F3G apply.
3.2 $&&re5iatio%
7or the purposes of the present document- the followin abbreviations applyD
./I .utomatic /epeat /eCuest
.! .ccess !tratum
.!1 .ccess !ervice 1lass
011= 0roadcast 1ontrol 1hannel
01= 0roadcast 1hannel
0M1 0roadcast;Multicast 1ontrol
1< 1ontrol<
11 1all 1ontrol
111= 1ommon 1ontrol 1hannel
11= 1ontrol 1hannel
11Tr1= 1oded 1omposite Transport 1hannel
1& 1ore &etwor"
1/1 1yclic /edundancy 1hec"
1T1= 1ommon Traffic 1hannel
81 8edicated 1ontrol (!.P)
81. 8ynamic 1hannel .llocation
811= 8edicated 1ontrol 1hannel
81= 8edicated 1hannel
85 8ownlin"
8/&1 8rift /adio &etwor" 1ontroller
8!1= 8ownlin" !hared 1hannel
8T1= 8edicated Traffic 1hannel
2<81= 2nhanced 8edicated 1hannel
7.1= 7orward 5in" .ccess 1hannel
71! 7rame 1hec" !eCuence
788 7reCuency 8ivision 8uple'
G1 General 1ontrol (!.P)
=./I =ybrid .utomatic /epeat /eCuest
=O =andover
=!<8!1= =ih !peed 8ownlin" !hared 1hannel
=!<P8!1= =ih !peed Physical 8ownlin" !hared 1hannel
J0M Jitter 0uffer Manaement
%T3 %nternational Telecommunication 3nion
"bps "ilobits per second
5, 5ayer , (physical layer)
5* 5ayer * (data lin" layer)
53 5ayer 3 (networ" layer)
5.1 5in" .ccess 1ontrol
5.% 5ocation .rea %dentity
M.1 Medium .ccess 1ontrol
M0M! Multimedia 0roadcast Multicast !ervice
M11= M0M! point<to<multipoint 1ontrol 1hannel
MM Mobility Manaement
M/&1 M0M! Master /&1
M!1= M0M! point<to<multipoint !chedulin 1hannel
MT1= M0M! point<to<multipoint Traffic 1hannel
&.! &on<.ccess !tratum
&t &otification (!.P)
P11= Pain 1ontrol 1hannel
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' * Release 1$
P1= Pain 1hannel
P81P Pac"et 8ata 1onverence Protocol
P83 Protocol 8ata 3nit
P=K Physical layer
Phy1= Physical 1hannels
/.0 /adio .ccess 0earer
/.1= /andom .ccess 1hannel
/0 /adio 0earer
/51 /adio 5in" 1ontrol
/&1 /adio &etwor" 1ontroller
/&! /adio &etwor" !ubsystem
/&T% /adio &etwor" Temporary %dentity
//1 /adio /esource 1ontrol
!.P !ervice .ccess Point
!83 !ervice 8ata 3nit
!=11= !hared 1hannel 1ontrol 1hannel
!/&1 !ervin /adio &etwor" 1ontroller
!/&! !ervin /adio &etwor" !ubsystem
!K&1 !ynchroni(ation 3ser Plane Protocol
T1= Traffic 1hannel
T88 Time 8ivision 8uple'
T71% Transport 7ormat 1ombination %ndicator
T7% Transport 7ormat %ndicator
T7/% Transport 7ormat and /esource %ndicator
TM!% Temporary Mobile !ubscriber %dentity
TP1 Transmit Power 1ontrol
T!& Transmit !eCuence &umber
3< 3ser<
32 3ser 2Cuipment
35 3plin"
3MT! 3niversal Mobile Telecommunications !ystem
3/. 3T/.& /eistration .rea
3!1= 3plin" !hared 1hannel
3T/. 3MT! Terrestrial /adio .ccess
3T/.& 3MT! Terrestrial /adio .ccess &etwor"
3u! 3u (/adio %nterface) !tratum
- $u6ed UMTS $rchitecture
7iure , shows the assumed 3MT! architecture as outlined in F,G. The fiure shows the 3MT! architecture in terms of
its entities 3ser 2Cuipment (32)- 3T/.& and 1ore &etwor". The respective reference points 3u (/adio %nterface) and
%u (1&<3T/.& interface) are shown. The fiure illustrates furthermore the hih<level functional roupin into the
.ccess !tratum and the &on<.ccess !tratum.
The .ccess !tratum offers services throuh the followin !ervice .ccess Points (!.P) to the &on<.ccess !tratumD
< General 1ontrol (G1) !.PsE
< &otification (&t) !.PsE and
< 8edicated 1ontrol (81) !.Ps.
The !.Ps are mar"ed with circles in 7iure ,.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' + Release 1$
81
&t G1
UTR$( U* )ore (et1or7
$cce Stratu6 ($S)
(o%-$cce Stratu6 (($S)
Radio
(Uu)
8u
81 &t G1
81 &t G1
81 &t G1
81 &t G1
81 &t G1
e%d $S e%tit9 e%d $S e%tit9
Re"a9
Uu
Stratu6
(UuS)
8u
Stratu6
!20!1
RR)
!20!1
RR)
,i-ure 1. Assu/ed 01TS Architecture
The model in 7iure , distinuishes the end .! entities F,G- which provide the services to hiher layers- from the local
entities- which provide services over respectively the 3u and the %u reference points.
The 3u !tratum (3u!) bloc" includes the radio interface protocol stac" described in subclause :.,.
5 Radio i%ter3ace #rotoco" architecture
5.1 :5era"" #rotoco" tructure
The radio interface is layered into three protocol layersD
< the physical layer (5,)E
< the data lin" layer (5*)E
< networ" layer (53).
5ayer * is split into followin sublayersD Medium .ccess 1ontrol (M.1)- /adio 5in" 1ontrol (/51)- Pac"et 8ata
1onverence Protocol (P81P) and 0roadcast;Multicast 1ontrol (0M1).
5ayer 3 and /51 are divided into 1ontrol (1<) and 3ser (3<) planes. P81P and 0M1 e'ist in the 3<plane only.
%n the 1<plane- 5ayer 3 is partitioned into sublayers where the lowest sublayer- denoted as /adio /esource 1ontrol
(//1)- interfaces with layer * and terminates in the 3T/.&. The ne't sublayer provides #8uplication avoidance#
functionality as specified in F,3G. %t terminates in the 1& but is part of the .ccess !tratumE it provides the .ccess
!tratum !ervices to hiher layers. The hiher layer sinallin such as Mobility Manaement (MM) and 1all 1ontrol
(11) is assumed to belon to the non<access stratum- and therefore not in the scope of 3GPP T!G /.&. On the eneral
level- the protocol architecture is similar to the current %T3</ protocol architecture- %T3</ M.,+3:.
7iure * shows the radio interface protocol architecture. 2ach bloc" in 7iure * represents an instance of the respective
protocol. !ervice .ccess Points (!.P) for peer<to<peer communication are mar"ed with circles at the interface between
sublayers. The !.P between M.1 and the physical layer provides the transport channels (cf. subclause :.*.,.,). The
!.Ps between /51 and the M.1 sublayer provide the loical channels (cf. subclause :.3.,.,.,). The /51 layer
provides three types of !.Ps- one for each /51 operation mode (3M- .M- and TM- see F@G). P81P and 0M1 are
accessed by P81P and 0M1 !.Ps- respectively. The service provided by layer * is referred to as the radio bearer. The
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' ' Release 1$
1<plane radio bearers- which are provided by /51 to //1- are denoted as sinallin radio bearers. %n the 1<plane- the
interface between #8uplication avoidance# and hiher 53 sublayers (11- MM) is defined by the General 1ontrol (G1)-
&otification (&t) and 8edicated 1ontrol (81) !.Ps.
&OT2D The !.Ps shown in 7iure * are e'amples. 7or details on the definition of !.Ps refer to the respective
radio interface protocol specification.
.lso shown in the fiure are connections between //1 and M.1 as well as //1 and 5, providin local inter<layer
control services. .n eCuivalent control interface e'ists between //1 and the /51 sublayer- between //1 and the
P81P sublayer and between //1 and 0M1 sublayer. These interfaces allow the //1 to control the confiuration of
the lower layers. 7or this purpose separate 1ontrol !.Ps are defined between //1 and each lower layer (P81P- /51-
M.1- and 5,).
The /51 sublayer provides ./I functionality closely coupled with the radio transmission techniCue used. There is no
difference between /51 instances in 1 and 3 planes.
The M.1 sublayer is made up of several different M.1 entities- M.1<d- M.1<c;sh;m- M.1<hs;M.1<ehs- M.1<
es;M.1<e- M.1<i;is and M.1<m.
The M.1<hs;M.1<ehs entity provides =ybrid ./I functionality- and is only used on the =!<8!1=.
The M.1<es;M.1<e and M.1<i;is entities provide =ybrid ./I functionality- and are only used with 2<81=.
The M.1<m entity provides selection combinin functionality for MT1= from different cells. M.1<m is only used for
7.1= carryin MT1= and M!1=.
The 3T/.& can be reCuested by the 1& to prevent all loss of data (i.e. independently of the handovers on the radio
interface)- as lon as the %u connection point is not modified. This is a basic reCuirement to be fulfilled by the 3T/.&
retransmission functionality as provided by the /51 sublayer.
=owever- in case of the %u connection point is chaned (e.. !/&! relocation- streamlinin)- the prevention of the loss
of data may not be uaranteed autonomously by the 3T/.& but relies on #8uplication avoidance# functions in the 1&.
There are primarily two "inds of sinallin messaes transported over the radio interface < //1 enerated sinallin
messaes and &.! messaes enerated in the hiher layers. On establishment of the sinallin connection between the
peer //1 entities three or four 3M;.M sinallin radio bearers may be set up. Two of these bearers are set up for
transport of //1 enerated sinallin messaes < one for transferrin messaes throuh an unac"nowleded mode /51
entity (see subclause :.3.*. for details on /51 modes) and the other for transferrin messaes throuh an ac"nowleded
mode /51 entity. One sinallin radio bearer is set up for transferrin &.! messaes set to Hhih priorityH by the
hiher layers. .n optional sinallin radio bearer may be set up for transferrin &.! messaes set to Hlow priorityH by
the hiher layers. !ubseCuent to the establishment of the sinallin connection (ero to several TM sinallin radio
bearers may be set up for transferrin //1 sinallin messaes usin transparent mode /51.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1$ Release 1$
L3
c
o
n
t
r
o
l
c
o
n
t
r
o
l
c
o
n
t
r
o
l
c
o
n
t
r
o
l
5oical
1hannels
Transport
1hannels
1<plane sinallin
3<plane information
P=K
L2/MAC
L1
/51
81
&t
G1
L2/RLC
M.1
/51
/51
/51
/51
/51
/51
/51
8uplication avoidance
3u! boundary
0M1
L2/BMC
control
P81P
P81P
L2/PCP
81
&t
G1
/adio
0earers
//1
,i-ure !. Radio Interface protocol architecture (Ser2ice Access Points /arked 34 circles
5.1.1 Ser5ice acce #oi%t a%d er5ice #ri6iti5e
2ach layer provides services at !ervice .ccess Points (!.Ps). . service is defined by a set of service primitives
(operations) that a layer provides to upper layer(s).
1ontrol services- allowin the //1 layer to control lower layers locally (i.e. not reCuirin peer<to<peer communication)
are provided at 1ontrol !.Ps (1<!.P). &ote that 1<!.P primitives can bypass one or more sublayers- see 7iure *.
%n the radio interface protocol specifications- the followin namin conventions for primitives shall be applicableD
< Primitives provided by !.Ps between adjacent layers shall be prefi'ed with the name of the service<providin
layer- i.e. P=K- M.1- /51- P81P- 0M1 or 33!.
< Primitives provided by !.Ps to an application shall be prefi'ed with the name of the service<providin layer- i.e.
//1.
< Primitives provided by 1ontrol !.Ps- in addition to the name of the service<providin layer- shall be prefi'ed
with a H1H- i.e. 1P=K- 1M.1- 1/51- 1P81P or 10M1.
This principle leads to the followin notations- where LTypeM corresponds to reCuest- indication- response or confirm
type of primitivesD
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 11 Release 1$
Primitives between P=K and M.1D
P!"# $%eneri& name' # $(y)e'
Primitives between P=K and //1 (over 1<!.P)D
CP!"# $%eneri& name' # $(y)e'
Primitives between M.1 and /51D
MAC# $%eneri& name' # $(y)e'
Primitives between M.1 and //1 (over 1<!.P)D
CMAC# $%eneri& name' # $(y)e'
Primitives between /51 and upper layers- between /51 and //1 for data transfer and between /51 and P81PD
RLC# $%eneri& name' # $(y)e'
Primitives between /51 and //1 for control of /51 (over 1<!.P)D
CRLC# $%eneri& name' # $(y)e'
Primitives above 3u !tratumD
**+# $%eneri& name' # $(y)e'
Primitives between P81P and non<access stratumD
PCP# $%eneri& name' # $(y)e'
Primitives between P81P and //1 (over 1<!.P)D
CPCP# $%eneri& name' # $(y)e'
Primitives between 0M1 and upper layerD
BMC# $%eneri& name' # $(y)e'
Primitives between 0M1 and //1 for control of 0M1 (over 1<!.P)D
CBMC# $%eneri& name' # $(y)e'
%n this model- some 33! primitives map directly to /51 primitives without intervenin function.
5.2 !a9er 1 Ser5ice a%d 'u%ctio%
This subclause shall provide an overview on services and functions provided by the physical layer. . detailed
description of 5ayer , eneral reCuirements can be found in F9G.
5.2.1 !1 Ser5ice
The physical layer offers information transfer services to M.1 and hiher layers. The physical layer transport services
are described by how and with what characteristics data are transferred over the radio interface. .n adeCuate term for
this is #Transport 1hannel#.
&OT2D This should be clearly separated from the classification of what is transported- which relates to the
concept of loical channels. Thus 81= is used to denote that the physical layer offers the same type of
service for both control and traffic.
5.2.1.1 Tra%#ort cha%%e"
. eneral classification of transport channels is into two roupsD
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1! Release 1$
< common transport channels (where there is a need for inband identification of the 32s when particular 32s are
addressed)E and
< dedicated transport channels (where the 32s are identified by the physical channel- i.e. code and freCuency for
788 and code- time slot and freCuency for T88).
1ommon transport channel types are (a more detailed description can be found in F9G)D
# Ran,om A&&ess Channe- (RAC!)
. contention based uplin" channel used for transmission of relatively small amounts of data- e.. for initial
access or non<real<time dedicated control or traffic data.
# .or/ar, A&&ess Channe- (.AC!)
1ommon downlin" channel without closed<loop power control used for transmission of relatively small amount
of data. %n addition 7.1= is used to carry broadcast and multicast data.
# o/n-in0 +hare, Channe- (+C!)
. downlin" channel shared by several 32s carryin dedicated control or traffic data- used in T88 mode only.
# *)-in0 +hare, Channe- (*+C!)
.n uplin" channel shared by several 32s carryin dedicated control or traffic data- used in T88 mode only.
# Broa,&ast Channe- (BC!)
. downlin" channel used for broadcast of system information into an entire cell.
# Paging Channe- (PC!)
. downlin" channel used for broadcast of control information into an entire cell allowin efficient 32 sleep
mode procedures. 1urrently identified information types are pain and notification. .nother use could be
3T/.& notification of chane of 011= information.
< !igh +)ee, o/n-in0 +hare, Channe- (!+#+C!)
. downlin" channel shared between 32s by allocation of individual codes- from a common pool of codes
assined for the channel.
< 1nhan&e, e,i&ate, Channe- (1#C!) (. an, 1.22 M&)s ( on-y)
7or 788- in 1255N7.1= state and %852 mode- this channel is used for uplin" transmission and is shared
between 32s by allocation of individual codes- from a common pool of codes assined for the channel. 7or ,.*@
Mcps T88- in 1255N7.1= state and %852 mode- this channel is used for uplin" transmission and is shared by
32s in 1255N7.1=- 1255N81= and %dle mode. The common 2<81= is subject to &ode<0 controlled
schedulin and =./I.
8edicated transport channel types areD
# e,i&ate, Channe- (C!)
. channel dedicated to one 32 used in uplin" or downlin".
# 1nhan&e, e,i&ate, Channe- (1#C!)
%n 1255N81=- a channel dedicated to one 32 used in uplin" only. The 2<81= is subject to &ode<0 controlled
schedulin and =./I.
To each transport channel- there is an associated Transport 7ormat (for transport channels with a fi'ed or slow chanin
rate) or an associated Transport 7ormat !et (for transport channels with fast chanin rate). . Transport 7ormat is
defined as a combination of encodins- interleavin- bit rate and mappin onto physical channels (see F9G for details). .
Transport 7ormat !et is a set of Transport 7ormats. 2..- a variable rate 81= has a Transport 7ormat !et (one Transport
7ormat for each rate)- whereas a fi'ed rate 81= has a sinle Transport 7ormat.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 13 Release 1$
5.2.2 !1 'u%ctio%
The physical layer performs the followin main functionsD
< Macrodiversity distribution;combinin and soft handover e'ecutionE
< 2rror detection on transport channels and indication to hiher layersE
< 721 encodin;decodin and interleavin;deinterleavin of transport channelsE
< Multiple'in of transport channels and demultiple'in of coded composite transport channelsE
< /ate matchinE
< Mappin of coded composite transport channels on physical channelsE
< Power weihtin and combinin of physical channelsE
< Modulation and spreadin;demodulation and despreadin of physical channelsE
< 7reCuency and time (chip- bit- slot- frame) synchronisationE
< Measurements and indication to hiher layers (e.. 72/- !%/- interference power- transmit power- etc.)E
< 1losed<loop power controlE
< /7 processinE
< !upport of timin advance on uplin" channels (T88 only)E
< !upport of 3plin" !ynchronisation as defined in F,*G (T88 only).
5.3 !a9er 2 Ser5ice a%d 'u%ctio%
5.3.1 M$) Ser5ice a%d 'u%ctio%
This subclause provides an overview on services and functions provided by the M.1 sublayer. . detailed description of
the M.1 protocol is iven in F?G.
5.3.1.1 M$) Ser5ice to u##er "a9er
< ata transfer. This service provides unac"nowleded transfer of M.1 !83s between peer M.1 entities. This
service provides data sementation on =!<8!1= and 2<81= but not for other transport channels. Therefore-
sementation;reassembly function should be achieved by upper layer when =!<8!1= or 2<81= is not used and
optionally when =!<8!1= or 2<81= is used.
< Rea--o&ation of ra,io reso3r&es an, MAC )arameters. This service performs on reCuest of //1 e'ecution of
radio resource reallocation and chane of M.1 parameters- i.e. reconfiuration of M.1 functions such as
chane of identity of 32- chane of transport format (combination) sets- chane of transport channel type. %n
T88 mode- in addition- the M.1 can handle resource allocation autonomously.
< Re)orting of meas3rements. 5ocal measurements such as traffic volume and Cuality indication are reported to
//1.
5.3.1.1.1 !o2ica" cha%%e"
The M.1 layer provides data transfer services on loical channels. . set of loical channel types is defined for different
"inds of data transfer services as offered by M.1. 2ach loical channel type is defined by what type of information is
transferred.
. eneral classification of loical channels is into two roupsD
< 1ontrol 1hannels (for the transfer of control plane information)E
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1( Release 1$
< Traffic 1hannels (for the transfer of user plane information).
The confiuration of loical channel types is depicted in 7iure 3.

0roadcast 1ontrol 1hannel (011=)
Pain 1ontrol 1hannel (P11=)
8edicated 1ontrol 1hannel (811=)
1ommon 1ontrol 1hannel (111=)
1ontrol 1hannel
8edicated Traffic 1hannel (8T1=) Traffic 1hannel
1ommon Traffic 1hannel (1T1=)
!hared 1hannel 1ontrol 1hannel (!=11=)
M0M! point<to<multipoint 1ontrol 1hannel (M11=)
M0M! point<to<multipoint Traffic 1hannel (MT1=)
M0M! point<to<multipoint !chedulin 1hannel (M!1=)
,i-ure 3. 5o-ical channel structure
)o%tro" )ha%%e"
1ontrol channels are used for transfer of control plane information only.
Broa,&ast Contro- Channe- (BCC!)
. downlin" channel for broadcastin system control information.
Paging Contro- Channe- (PCC!)
. downlin" channel that transfers pain information. This channel is used when the networ" does not "now the
location cell of the 32- or- the 32 is in the cell connected state (utilisin 32 sleep mode procedures).
Common Contro- Channe- (CCC!)
0i<directional channel for transmittin control information between networ" and 32s. This channel is commonly used
by the 32s havin no //1 connection with the networ" and by the 32s usin common transport channels when
accessin a new cell after cell reselection.
e,i&ate, Contro- Channe- (CC!)
. point<to<point bi<directional channel that transmits dedicated control information between a 32 and the networ". This
channel is established throuh //1 connection setup procedure.
+hare, Channe- Contro- Channe- (+!CC!)
0i<directional channel that transmits control information for uplin" and downlin" shared channels between networ" and
32s. This channel is for T88 only.
MBM+ )oint#to#m3-ti)oint Contro- Channe- (MCC!)
. point<to<multipoint downlin" channel used for transmittin control information from the networ" to the 32. This
channel is only used by 32s that receive M0M!.
MBM+ )oint#to#m3-ti)oint +&he,3-ing Channe- (M+C!)
. point<to<multipoint downlin" channel used for transmittin schedulin control information- from the networ" to the
32- for one or several MT1=s carried on a 11Tr1=. This channel is only used by 32s that receive M0M!.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1" Release 1$
Tra33ic )ha%%e"
Traffic channels are used for the transfer of user plane information only.
e,i&ate, (raffi& Channe- ((C!)
. 8edicated Traffic 1hannel (8T1=) is a point<to<point channel- dedicated to one 32- for the transfer of user
information. . 8T1= can e'ist in both uplin" and downlin".
Common (raffi& Channe- (C(C!)
. point<to<multipoint unidirectional channel for transfer of dedicated user information for all or a roup of specified
32s.
MBM+ )oint#to#m3-ti)oint (raffi& Channe- (M(C!)
. point<to<multipoint downlin" channel used for transmittin traffic data from the networ" to the 32. This channel is
only used for M0M!.
5.3.1.1.2 Ma##i%2 &et1ee% "o2ica" cha%%e" a%d tra%#ort cha%%e"
5.3.1.1.2.1 Ma##i%2 i% U#"i%7
%n 3plin"- the followin connections between loical channels and transport channels e'istD
< 111= can be mapped to /.1=E
< 111= can be mapped to 2<81= (in 788 and ,.*@ Mcps T88 mode only)E
< 811= can be mapped to /.1=E
< 811= can be mapped to 81=E
< 811= can be mapped to 3!1= (in T88 mode only)E
< 811= can be mapped to 2<81=E
< 8T1= can be mapped to /.1=E
< 8T1= can be mapped to 81=E
< 8T1= can be mapped to 3!1= (in T88 mode only)E
< !=11= can be mapped to /.1= (in T88 mode only)E
< !=11= can be mapped to 3!1= (in T88 mode only)E
< 8T1= can be mapped to 2<81=.
5.3.1.1.2.2 Ma##i%2 i% 4o1%"i%7
%n 8ownlin"- the followin connections between loical channels and transport channels e'istD
< 011= can be mapped to 01=E
< 011= can be mapped to 7.1=E
< 011= can be mapped to =!<8!1= (in 788 and ,.*@ Mcps T88 mode only)E
< P11= can be mapped to P1=E
< P11= can be mapped to =!<8!1= (in 788 and ,.*@ Mcps T88 mode only)E
< 111= can be mapped to 7.1=E
< 111= can be mapped to =!<8!1= (in 788 and ,.*@ Mcps T88 mode only)E
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1) Release 1$
< 811= can be mapped to 7.1=E
< 811= can be mapped to 8!1= (in T88 mode only)E
< 811= can be mapped to =!<8!1=E
< 811= can be mapped to 81=E
< M11= can be mapped to 7.1=E
< M!1= can be mapped to 7.1=E
< 8T1= can be mapped to 7.1=E
< 8T1= can be mapped to 8!1= (in T88 mode only)E
< 8T1= can be mapped to =!<8!1=E
< 8T1= can be mapped to 81=E
< 1T1= can be mapped to 7.1=E
< MT1= can be mapped to 7.1=E
< !=11= can be mapped to 7.1= (in T88 mode only)E
< !=11= can be mapped to 8!1= (in T88 mode only).
The mappins as seen from the 32 and 3T/.& sides are shown in 7iure 9 and 7iure : respectively.

01= P1= 8!1=
(T88 only)
7.1= /.1=
011=<
!.P
811=<
!.P
111=<
!.P
P11=<
!.P
81=
8T1=<
!.P
Transport
1hannels
M.1 !.Ps
3!1=
(T88 only)
1T1=<
!.P
!=11=<
!.P
(T88 only)
=!<8!1= 2<81=
M!1=<
!.P
M11=<
!.P
MT1=<
!.P
,i-ure (. 5o-ical channels /apped onto transport channels6 seen fro/ the 07 side
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1* Release 1$

01= P1= 8!1=
(T88 only)
7.1= /.1=
011=<
!.P
811=<
!.P
111=<
!.P
P11=<
!.P
81=
8T1=<
!.P
Transport
1hannels
M.1 !.Ps
3!1=
(T88 only)
1T1=<
!.P
!=11=<
!.P
(T88 only)
=!<8!1= 2<81=
M!1=<
!.P
M11=<
!.P
MT1=<
!.P
,i-ure ". 5o-ical channels /apped onto transport channels6 seen fro/ the 0TRAN side
5.3.1.2 M$) 3u%ctio%
The functions of M.1 includeD
< Ma))ing 4et/een -ogi&a- &hanne-s an, trans)ort &hanne-s. The M.1 is responsible for mappin of loical
channel(s) onto the appropriate transport channel(s).
< +e-e&tion of a))ro)riate (rans)ort .ormat for ea&h (rans)ort Channe- ,e)en,ing on instantaneo3s
so3r&e rate. Given the Transport 7ormat 1ombination !et assined by //1- M.1 selects the appropriate
transport format within an assined transport format set for each active transport channel dependin on source
rate. The control of transport formats ensures efficient use of transport channels.
< Priority han,-ing 4et/een ,ata f-o/s of one *1. Ohen selectin between the Transport 7ormat 1ombinations
in the iven Transport 7ormat 1ombination !et- priorities of the data flows to be mapped onto the correspondin
Transport 1hannels can be ta"en into account. Priorities are e.. iven by attributes of /adio 0earer services and
/51 buffer status. The priority handlin is achieved by selectin a Transport 7ormat 1ombination for which
hih priority data is mapped onto 5, with a Hhih bit rateH Transport 7ormat- at the same time lettin lower
priority data be mapped with a Hlow bit rateH (could be (ero bit rate) Transport 7ormat. Transport format
selection may also ta"e into account transmit power indication from 5ayer ,.
< Priority han,-ing 4et/een *1s 4y means of ,ynami& s&he,3-ing. %n order to utilise the spectrum resources
efficiently for bursty transfer- a dynamic schedulin function may be applied. M.1 realises priority handlin on
common transport channels- shared transport channels and for the dedicated and common 2<81= transport
channel. &ote that for dedicated transport channels other than 2<81=- the eCuivalent of the dynamic schedulin
function is implicitly included as part of the reconfiuration function of the //1 sublayer.
&OT2D %n the T88 mode the data to be transported are represented in terms of sets of resource units.
< 5,entifi&ation of *1s on &ommon trans)ort &hanne-s. Ohen a particular 32 is addressed on a common
downlin" channel- or when a 32 is usin the /.1=- there is a need for inband identification of the 32. !ince
the M.1 layer handles the access to- and multiple'in onto- the transport channels- the identification
functionality is naturally also placed in M.1. %n 788 and ,.*@ Mcps T88 mode only- if a 32 is in
1255N7.1=- 1255NP1= or 3/.NP1= state and =!<8!1= is used as a common transport channel- it is
possible to identify the 32 in physical layer usin dedicated =</&T% on =!<!11= if the =</&T% is dedicated
for the 32. %n 788 mode only- if a 32 is in 1255N7.1= state or %852 mode and 2<81= is used as a common
transport channel- there is a need for inband identification of the 32.
< M3-ti)-exing/,em3-ti)-exing of 3))er -ayer P*s into/from trans)ort 4-o&0s ,e-ivere, to/from the
)hysi&a- -ayer on &ommon trans)ort &hanne-s. M.1 should support service multiple'in for common
transport channels- since the physical layer does not support multiple'in of these channels.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1+ Release 1$
< M3-ti)-exing/,em3-ti)-exing of 3))er -ayer P*s into/from trans)ort 4-o&0 sets ,e-ivere, to/from the
)hysi&a- -ayer on ,e,i&ate, trans)ort &hanne-s. The M.1 allows service multiple'in for dedicated transport
channels. This function can be utilised when several upper layer services (e.. /51 instances) can be mapped
efficiently on the same transport channel. %n this case the identification of multiple'in is contained in the M.1
protocol control information.
< M3-ti)-exing/,em3-ti)-exing of 3))er -ayer P*s into trans)ort 4-o&0s ,e-ivere, to/from the )hysi&a-
-ayer on !+#+C!. The M.1 allows service multiple'in for =!<8!1=. This function can be utilised to
multiple' data from several upper layer services (e.. /51 instances). %n this case the identification of
multiple'in is contained in the M.1 protocol control information.
< (raffi& vo-3me meas3rement. Measurement of traffic volume on loical channels and reportin to //1. 0ased
on the reported traffic volume information- //1 performs transport channel switchin decisions.
< (rans)ort Channe- ty)e s/it&hing. 2'ecution of the switchin between common and dedicated transport
channels based on a switchin decision derived by //1.
< Ci)hering. This function prevents unauthorised acCuisition of data. 1ipherin is performed in the M.1 layer
for transparent /51 mode. 8etails of the security architecture are specified in F,:G.
< A&&ess +ervi&e C-ass se-e&tion for RAC! transmission an, 1nhan&e, *)-in0 for C1LL6.AC! an, 5,-e
mo,e. The /.1= and 2<81= (as common transport channel) resources (i.e. access slots and preamble
sinatures for 788- timeslot and channelisation code for T88) may be divided between different .ccess !ervice
1lasses in order to provide different priorities of /.1= and 2<81= (as common transport channel) usae. %n
addition it is possible for more than one .!1 or for all .!1s to be assined to the same access slot;sinature
space. 2ach access service class will also have a set of bac"<off parameters associated with it- some or all of
which may be broadcast by the networ". The M.1 function applies the appropriate bac"<off and indicates to the
P=K layer the /.1= partition associated to a iven M.1 P83 transfer.
< !AR7 f3n&tiona-ity for !+#+C! an, 1#C! transmission. The M.1<hs- M.1<ehs- M.1<e and M.1<i
entities are responsible for establishin the =./I entity in accordance with the hiher layer confiuration and
handlin all the tas"s reCuired to perform =./I functionality. This functionality ensures delivery between peer
entities by use of the .1$ and &.1$ sinallin between the peer entities.
< ata segmentation/re#assem4-y for !+#+C! an, 1#C!. =iher layer !83s can be semented by the
transmittin M.1<hs;M.1<ehs or M.1<i;is entity to fit the available radio resource. /eassembly is provided in
the receivin M.1<hs;M.1<ehs or M.1<is entity.
< 5n#se83en&e ,e-ivery an, assem4-y/,isassem4-y of higher -ayer P*s on !+#+C!. %n 1255N81= state
the transmittin M.1<hs;M.1<ehs entity assembles the data bloc" payload for the M.1<hs;M.1<ehs P83s
from the delivered M.1<d P83s. 7or M.1<hs- the M.1<d P83s that are assembled in any one M.1<hs P83
are the same priority- and from the same M.1<d flow. 7or M.1<ehs the M.1<d P83s that are assembled in
any one M.1<ehs P83 may be of the same or different priority- and from the same or different M.1<d flow.
The receivin M.1<hs;M.1<ehs entity is then responsible for the reorderin of the received data bloc"s
accordin to the received T!&- per priority and M.1<d flow- and then disassemblin the data bloc" into M.1<d
P83s for in<seCuence delivery to the hiher layers. %n 788 and ,.*@ Mcps T88 mode in 1255N7.1=-
1255NP1= and 3/.NP1= state the transmittin M.1<ehs entity assembles the data bloc" payload for the
M.1<ehs P83s from the delivered M.1<d P83s and M.1<c P83s for 111=- 011= and P11= loical
channels.
# 5n#se83en&e ,e-ivery an, assem4-y/,isassem4-y of higher -ayer P*s on 1#C!. The transmittin M.1<
es;M.1<e or M.1<i;is entity assembles the data bloc" payload for the M.1<e;M.1<i P83s from the delivered
M.1<d P83s. 7or 8T1= and 811= transmission- the receivin M.1<es or M.1<is entity is then responsible
for the reorderin of the received data bloc"s accordin to the received T!& and &ode<0 tain information-
per re<orderin Cueue- and then disassemblin the data bloc" into M.1<d P83s for in<seCuence delivery to the
hiher layers. 7or 111= transmission- the receivin M.1<is entity is then responsible for the reorderin of the
received data bloc"s accordin to the received T!& and &ode<0 tain information- then disassemblin the
data bloc" into a M.1<c P83. %f more then one M.1<is P83 was received- the added chec" sum is removed
and is verified- before delivery to the hiher layers. . failure to verify the chec"sum results in discardin the
M.1<c P83.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 1' Release 1$
5.3.2 R!) Ser5ice a%d 'u%ctio%
This subclause provides an overview on services and functions provided by the /51 sublayer. . detailed description of
the /51 protocol is iven in F@G.
5.3.2.1 Ser5ice #ro5ided to the u##er "a9er
# (rans)arent ,ata transfer. This service transmits upper layer P83s without addin any protocol information-
possibly includin sementation;reassembly functionality.
# *na&0no/-e,ge, ,ata transfer. This service transmits upper layer P83s without uaranteein delivery to the
peer entity. The unac"nowleded data transfer mode has the followin characteristicsD
# 8etection of erroneous dataD The /51 sublayer shall deliver only those !83s to the receivin upper layer
that are free of transmission errors by usin the seCuence<number chec" function.
# %mmediate deliveryD The receivin /51 sublayer entity shall deliver a !83 to the upper layer receivin
entity as soon as it arrives at the receiver.
< 8uplication avoidance and reorderinD .lternative to immediate delivery- the /51 sublayer shall deliver
!83s to the receivin upper layer entity in the same order as the transmittin upper layer entity submits them
to the /51 sublayer without duplication. !83s may be delayed by this procedure to ensure in<seCuence
delivery.
< Out<of<seCuence !83 deliveryD .lternative to immediate delivery- the /51 sublayer shall deliver !83s to
the upper layer receivin entity as soon as they can be recovered from P83s- without waitin for earlier in<
seCuence !83s to be recovered.
< !eCuence<number delivery to J0M.
# A&0no/-e,ge, ,ata transfer. This service transmits upper layer P83s and uarantees delivery to the peer
entity. %n case /51 is unable to deliver the data correctly- the user of /51 at the transmittin side is notified. 7or
this service- both in<seCuence and out<of<seCuence delivery are supported. %n many cases a upper layer protocol
can restore the order of its P83s. .s lon as the out<of<seCuence properties of the lower layer are "nown and
controlled (i.e. the upper layer protocol will not immediately reCuest retransmission of a missin P83) allowin
out<of<seCuence delivery can save memory space in the receivin /51. The ac"nowleded data transfer mode
has the followin characteristicsD
# 2rror<free deliveryD 2rror<free delivery is ensured by means of retransmission. The receivin /51 entity
delivers only error<free !83s to the upper layer.
# 3niCue deliveryD The /51 sublayer shall deliver each !83 only once to the receivin upper layer usin
duplication detection function.
# %n<seCuence deliveryD /51 sublayer shall provide support for in<order delivery of !83s- i.e.- /51 sublayer
should deliver !83s to the receivin upper layer entity in the same order as the transmittin upper layer
entity submits them to the /51 sublayer.
# Out<of<seCuence deliveryD .lternatively to in<seCuence delivery- it shall also be possible to allow that the
receivin /51 entity delivers !83s to upper layer in different order than submitted to /51 sublayer at the
transmittin side.
# Maintenan&e of 7o+ as ,efine, 4y 3))er -ayers. The retransmission protocol shall be confiurable by layer 3
to provide different levels of Io!. This can be controlled.
# 9otifi&ation of 3nre&overa4-e errors. /51 notifies the upper layer of errors that cannot be resolved by /51
itself by normal e'ception handlin procedures- e.. by adjustin the ma'imum number of retransmissions
accordin to delay reCuirements.
7or .M /51- there is only one /51 entity per /adio 0earer. 7or 3M and TM /51- there is one or two (one for each
direction) /51 entities per /adio 0earer.
5.3.2.2 R!) 'u%ctio%
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !$ Release 1$
# +egmentation an, reassem4-y. This function performs sementation;reassembly of variable<lenth upper layer
P83s into;from smaller /51 P83s. The /51 P83 si(e is either fi'ed (a semi static variable confiured by
upper layers) or fle'ible (automatically adjusted to the incomin !83 si(e) dependin on the confiuration.
7le'ible /51 P83 si(e is only supported when mapped on =!<8!1= or 2<81=.
# Con&atenation. %f the contents of an /51 !83 cannot be carried by one /51 P83- the first sement of the
ne't /51 !83 may be put into the /51 P83 in concatenation with the last sement of the previous /51 !83.
# Pa,,ing. Ohen concatenation is not applicable and the remainin data to be transmitted does not fill an entire
/51 P83 of iven si(e- the remainder of the data field shall be filled with paddin bits.
# (ransfer of 3ser ,ata. This function is used for conveyance of data between users of /51 services. /51
supports ac"nowleded- unac"nowleded and transparent data transfer. Io! settin controls transfer of user
data.
# 1rror &orre&tion. This function provides error correction by retransmission (e.. !elective /epeat- Go 0ac" &-
or a !top<and<Oait ./I) in ac"nowleded data transfer mode.
# 5n#se83en&e ,e-ivery of 3))er -ayer P*s. This function preserves the order of upper layer P83s that were
submitted for transfer by /51 usin the ac"nowleded data transfer service. %f this function is not used- out<of<
seCuence delivery is provided.
# 3)-i&ate ete&tion. This function detects duplicated received /51 P83s and ensures that the resultant upper
layer P83 is delivered only once to the upper layer.
# .-o/ &ontro-. This function allows an /51 receiver to control the rate at which the peer /51 transmittin entity
may send information.
# +e83en&e n3m4er &he&0. This function is used in unac"nowleded mode and uarantees the interity of
reassembled P83s and provides a mechanism for the detection of corrupted /51 !83s throuh chec"in
seCuence number in /51 P83s when they are reassembled into a /51 !83. . corrupted /51 !83 will be
discarded.
# Proto&o- error ,ete&tion an, re&overy. This function detects and recovers from errors in the operation of the
/51 protocol.
# Ci)hering. This function prevents unauthorised acCuisition of data. 1ipherin is performed in /51 layer for
non<transparent /51 mode. 8etails of the security architecture are specified in F,:G.
# +* ,is&ar,. This function allows an /51 transmitter to dischare /51 !83 from the buffer.
5.3.3 P4)P Ser5ice a%d 'u%ctio%
This subclause provides an overview on services and functions provided by the Pac"et 8ata 1onverence Protocol
(P81P). . detailed description of the P81P is iven in FAG.
5.3.3.1 P4)P Ser5ice #ro5ided to u##er "a9er
# P81P !83 delivery.
# 1! counter delivery to J0M.
5.3.3.2 P4)P 'u%ctio%
# !ea,er &om)ression an, ,e&om)ression. =eader compression and decompression of %P data streams (e..-
T1P;%P and /TP;38P;%P headers) at the transmittin and receivin entity- respectively. The header compression
method is specific to the particular networ" layer- transport layer or upper layer protocol combinations e..
T1P;%P and /TP;38P;%P.
# (ransfer of 3ser ,ata. Transmission of user data means that P81P receives P81P !83 from the &.! and
forwards it to the /51 layer and vice versa.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !1 Release 1$
# +3))ort for -oss-ess +R9+ re-o&ation or -oss-ess L RLC P* si:e &hange. Maintenance of P81P seCuence
numbers for radio bearers that are confiured to support lossless !/&! relocation or lossless 85 /51 P83 si(e
chane.
# C+ &o3nter. . 1! counter provides the P81P P83 with a timestamp value called the #1! counter#. The value of
the #1! counter# is set to the first to fifth 5!0s of the 17& at which the pac"et is received from hiher layers.
5.3.- ;roadcat0Mu"ticat )o%tro" - Ser5ice a%d 3u%ctio%
This subclause provides an overview on services and functions provided by the 0M1 sublayer. . detailed description of
the 0M1 protocol is iven in F,+G.
5.3.-.1 ;M) Ser5ice
The 0M1<!.P provides a broadcast;multicast transmission service in the user plane on the radio interface for common
user data in unac"nowleded mode.
5.3.-.2 ;M) 'u%ctio%
# +torage of Ce-- Broa,&ast Messages.
The 0M1 stores the 1ell 0roadcast messaes received over the 101</&1 interface for scheduled transmission.
< (raffi& vo-3me monitoring an, ra,io reso3r&e re83est for CB+.
.t the 3T/.& side- the 0M1 calculates the reCuired transmission rate for 1ell 0roadcast !ervice based on the
messaes received over the 101</&1 interface- and reCuests for appropriate 1T1=;7.1= resources from
//1.
< +&he,3-ing of BMC messages.
The 0M1 receives schedulin information toether with each 1ell 0roadcast messae over the 101</&1<
interface. 0ased on this schedulin information- at the 3T/.& side- 0M1 enerates schedule messaes and
schedules 0M1 messae seCuences accordinly. .t the 32 side- 0M1 evaluates the schedule messaes and
indicates schedulin parameters to //1- which are used by //1 to confiure the lower layers for 10!
discontinuous reception.
# (ransmission of BMC messages to *1.
This function transmits the 0M1 messaes (!chedulin and 1ell 0roadcast messaes) accordin to schedule.
# e-ivery of Ce-- Broa,&ast messages to 3))er -ayer (9A+).
This functions delivers the received 1ell 0roadcast messaes to upper layer (&.!) in the 32. Only non<
corrupted 1ell 0roadcast messaes are delivered.
5.3.5 4ata 3"o1 throu2h !a9er 2
8ata flows throuh layer * are characterised by the applied data transfer modes on /51 (ac"nowleded-
unac"nowleded and transparent transmission) in combination with the data transfer type on M.1- i.e. whether or not a
M.1 header is reCuired. The case where no M.1 header is reCuired is referred to as HtransparentH M.1 transmission.
.c"nowleded and unac"nowleded /51 transmissions both reCuire a /51 header. %n unac"nowleded transmission-
only one type of unac"nowleded data P83 is e'chaned between peer /51 entities. %n ac"nowleded transmission-
both (ac"nowleded) data P83s and control P83s are e'chaned between peer /51 entities.
The resultin different data flow cases are illustrated in 7iures > < A. On the level of detail presented here- differences
between ac"nowleded and unac"nowleded /51 transmission are not visible. .c"nowleded and unac"nowleded
/51 transmission is shown as one case- referred to as non<transparent /51.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !! Release 1$
&OT2D The term Htransparent transmissionH is used here to characterise the case where a protocol- M.1 or /51-
does not reCuire any protocol control information (e.. header). %n transparent transmission mode-
however- some protocol functions may still be applied. %n this case an entity of the respective protocol
must be present even when the protocol is transparent. 7or the /51 protocol the sementation;reassembly
function may be applied. This can be performed without sementation header when a iven hiher layer
P83 fits into a fi'ed number of /51 P83s to be transferred in a iven transmission time interval. %n this
case sementation;reassembly follows predefined rules "nown to sendin and receivin /51 entities. 7or
instance in the user plane- the sementation;reassembly function is needed for the case of real<time
services usin hih and possibly variable bit rates. 7or such services hiher layer P83s shall be
semented into reasonably si(ed /51 P83s of fi'ed lenth allowin efficient 71! error detection on the
physical layer. The hiher layer P83 can be reassembled by simply concatenatin all /51 P83s
included in a transport bloc" set as implied by the used transport format.
7iure > and 7iure ? illustrate the data flows for transparent /51 with transparent and non<transparent M.1
transmission- respectively.
7iure @ and 7iures A- Aa- Aa,- Ab- Ac illustrate the data flows for non<transparent /51 with transparent and non<
transparent M.1 transmission- respectively.
7iure ,+ illustrates the data flow for transparent /51 with transparent and non<transparent M.1 transmission.
%n 7iure Aa- with M.1<hs confiuration- M.1<d operation is non<transparent- when multiple loical channels are
multiple'ed on the same M.1<d flow- otherwise it is transparent.
. number of M.1 P83s shown in the fiures shall comprise a transport bloc" set. &ote- however- that in all cases a
transport bloc" set must not necessarily match with a /51 !83. The span of a transport bloc" set can be smaller or
larer than an /51 !83.
2ach mappin between a loical channel and a transport channel as defined in 7iure 9 and 7iure : in combination
with the respective /51 transmission mode implies a certain data flow that is specified on a eneral level in the
followin.
<i2her !a9er P4U
!1
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)

R!) P4U R!) P4U

R!) S4U
<i2her
!a9er
!2 M$)
(tra%#are%t)
!2 R!)
(tra%#are%t)
segmentation
reassembly
,i-ure ). 8ata flow for transparent R59 and 1A9
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !3 Release 1$
!1
!2 M$)
(%o%-tra%#are%t)
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)

M$)
header
M$)
header

!2 R!)
(tra%#are%t)
<i2her !a9er P4U
R!) P4U R!) P4U

R!) S4U
<i2her
!a9er
segmentation
reassembly
,i-ure *. 8ata flow for transparent R59 and non&transparent 1A9
<i2her !a9er
!1
<i2her !a9er P4U
R!) S4U
R!)
header
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)
Segmentation &
concatenation
reassembly

R!)
header

M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)

!2 M$)
(tra%#are%t)
!2 R!)
(%o%-tra%#are%t)
<i2her !a9er P4U
R!) S4U
,i-ure +. 8ata flow for non&transparent R59 and transparent 1A9
<i2her !a9er
!1
<i2her !a9er P4U
R!) S4U
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)

R!)
header
R!)
header
M$) S4U
Tra%#ort &"oc7 (M$) P4U)
)R)

M$)
header
M$)
header

!2 M$)
(%o%-tra%#are%t)
!2 R!)
(%o%-tra%#are%t) Segmentation &
concatenation
reassembly
<i2her !a9er P4U
R!) S4U
,i-ure '. 8ata flow for non&transparent R59 and 1A9
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !( Release 1$
,i-ure 'a. 8ata flow for non&transparent R59 and 1A9 /apped to :S&8S9: (1A9&hs confi-ured
,i-ure 'a1. 8ata flow for non&transparent R59 and 1A9 /apped to :S&8S9: (1A9&ehs confi-ured
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !" Release 1$

Higher Layer
L1
<i2her !a9er P4U
R!) S4U
M$)-d S4U
M$)-d P4U




R!)
header
R!)
header


M$)-d S4U
M$)-d P4U
)R)


L2 MAC-d
(transparent)
L2 RLC
(non-transparent)
Segmentation
&
Concatenation
Reassembly
<i2her !a9er P4U
R!) S4U
M$)-e0M$)-e S4U M$)-e0M$)-e S4U M$)-e0e
header
L2 MAC-es/MAC-e
(non-transparent)
Tra%#ort ;"oc7 (M$)-e P4U)


,i-ure '3. 8ata flow for non&transparent R59 and 1A9 /apped to 7&89: (1A9&e;es confi-ured

Higher Layer
L1
<i2her !a9er P4U
R!) S4U
M$)-d S4U
M$)-d P4U




R!)
header
R!)
header


M$)-d S4U
M$)-d P4U
)R)


L2 MAC-d
(transparent)
L2 RLC
(non-transparent)
Segmentation
& Concatenation
Reassembly
<i2her !a9er P4U
R!) S4U
M$)-i0M$)-i S4U M$)-i0M$)-i S4U

M$)-i0i
L2 MAC-is/i
(non-transparent)
Tra%#ort ;"oc7 (M$)-i P4U)


,i-ure 'c. 8ata flow for non&transparent R59 and 1A9 /apped to 7&89: (1A9&i;is confi-ured
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !) Release 1$
,i-ure 1$. 999: data for transparent R59 and non&transparent 1A9 /apped to 7&89: (1A9&i;is
confi-ured6 ,88 and 1#!+ 1cps T88 onl4
5.3.5.1 4ata 3"o1 3or ;))< 6a##ed to ;)<
.ll //1 P83s transmitted on 011= have a fi'ed lenth and fit into one /51 P83 (and- eCuivalently- M.1 P83- as
defined by the transport format). &o /51 header is needed- i.e. the transparent data transfer mode of /51 is applied.
&o M.1 header is needed since only one 011= loical channel is mapped onto a 01=. 7iure > is applicable.
5.3.5.2 4ata 3"o1 3or ;))< 6a##ed to '$)<
&o /51 header is needed- i.e. the transparent data transfer mode of /51 is applied. . M.1 header is reCuired for
identification of the loical channel carried by the 7.1=. The data flow shown in 7iure ? is applicable.
5.3.5.3 4ata 3"o1 3or P))< 6a##ed to P)<
&o /51 or M.1 header is needed- i.e. the data flow in 7iure > is applicable.
5.3.5.- 4ata 3"o1 3or )))< 6a##ed to '$)<0R$)<
7or 111=- transparent transmission mode on /51 is employed on the uplin" (when mapped to /.1=).
3nac"nowleded transmission mode on /51 is employed on the downlin" (when mapped to 7.1=). . M.1 header is
used for loical channel identification (011=- 111=- 1T1=- !=11=- 811=- 8T1=). %f the transparent /51
transfer mode is applied- the data flow 7iure ? is applicable. %f the unac"nowleded /51 transfer mode is applied- the
data flow 7iure A is applicable.
5.3.5.5 4ata 3"o1 3or S<))< 6a##ed to US)<
7or !=11= mapped on 3!1=- transparent transmission mode on /51 is employed. . M.1 header may be used for
loical channel identification (!=11=- 811=- 8T1=). Ohen no M.1 header is used- !=11= must be the only
channel mapped to 3!1=;8!1=. 8ependin on whether the M.1 header is needed or not- either the data flow 7iure
> or 7iure ? is applicable.
5.3.5.6 4ata 3"o1 3or S<))< 6a##ed to '$)<0R$)<
7or !=11=- transparent transmission mode on /51 is employed on the uplin" (when mapped to /.1=).
3nac"nowleded transmission mode on /51 is employed on the downlin" (when mapped to 7.1=). . M.1 header
may be used for loical channel identification (011=- 111=- 1T1=- !=11=- 811=- 8T1=). Ohen no M.1
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !* Release 1$
header is used- !=11= must be the only channel mapped to /.1=;7.1=. %f the transparent /51 transfer mode is
applied- dependin on whether the M.1 header is needed or not- either the data flow 7iure > or 7iure ? is applicable.
%f the unac"nowleded /51 transfer mode is applied- dependin on whether the M.1 header is needed or not- either
the data flow 7iure @ or 7iure A is applicable.
5.3.5./ 4ata 3"o1 3or 4))< 6a##ed to '$)<0R$)<
7or 811=- both unac"nowleded and ac"nowleded transmission mode on /51 is employed. . M.1 header is
mandatory for 7.1=;/.1= carryin 811=. The data flow shown in 7iure A is applicable.
5.3.5.= 4ata 3"o1 3or 4))< 6a##ed to 4S)<
7or 811=- both unac"nowleded and ac"nowleded transmission mode on /51 is employed. . M.1 header is
optional- i.e. either the data flow in 7iure @ or 7iure A is applicable.
5.3.5.9 4ata 3"o1 3or 4))< 6a##ed to US)<
7or 811=- both unac"nowleded and ac"nowleded transmission mode on /51 is employed. . M.1 header is
needed if 811= and 8T1= loical channels are multiple'ed in M.1 before mappin to a 3!1=- i.e. either the data
flow in 7iure @ or 7iure A is applicable.
5.3.5.10 Void
5.3.5.11 4ata 3"o1 3or 4T)< (%o%-tra%#are%t R!)) 6a##ed to '$)<0R$)<
Mappin to 7.1=;/.1= implies a 8T1= with ac"nowleded or unac"nowleded transmission on /51. . M.1
header is mandatory for 7.1=;/.1= when carryin 8T1=. The data flow shown in 7iure A is applicable.
5.3.5.12 4ata 3"o1 3or 4T)< (%o%-tra%#are%t R!)) 6a##ed to 4S)<
Mappin to 8!1= implies a 8T1= with ac"nowleded or unac"nowleded transmission on /51. . M.1 header is
optional- i.e. either the data flow in 7iure @ or 7iure A is applicable.
5.3.5.13 4ata 3"o1 3or 4T)< (%o%-tra%#are%t R!)) 6a##ed to US)<
Mappin to 3!1= implies a 8T1= with ac"nowleded or unac"nowleded transmission on /51. . M.1 header is
needed if 811= and 8T1= loical channels are multiple'ed in M.1 before mappin to a 3!1=- i.e. either the data
flow in 7iure @ or 7iure A is applicable.
5.3.5.1- 4ata 3"o1 3or 4T)< (tra%#are%t R!)) 6a##ed to 4)<
1ontinuous 8T1= data stream is semented into transport bloc"s on /51 and mapped on a 81= transport channel on
M.1. The transport bloc" si(e is naturally implied by the data rate. 0oth /51 and M.1 sublayers are transparent- i.e.
no protocol control information is added- when no multiple'in of 8T1= on M.1 is applied. The data flow shown in
7iure > is applicable. %f multiple'in on M.1 is performed- a M.1 header is needed- and 7iure ? applies.
5.3.5.15 4ata 3"o1 3or 4T)< (%o%-tra%#are%t R!)) 6a##ed to 4)<
%n this case ac"nowleded or unac"nowleded transmission on /51 is applied. . M.1 header is needed only if
multiple 8T1= loical channels are multiple'ed in M.1 before mappin to a 81=- i.e. either the data flow in 7iure @
or 7iure A is applicable.
5.3.5.16 Void
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !+ Release 1$
5.3.5.1/ 4ata 3"o1 3or 4))< 6a##ed to 4)<
%n this case non<transparent or transparent transmission mode on /51 is applied. . M.1 header is needed only if
811= and 8T1= loical channels are multiple'ed in M.1 before mappin to a 81=- i.e. either the data flow in
7iure @ or 7iure A is applicable.
5.3.5.1= 4ata 3"o1 3or )T)< 6a##ed to '$)<
7or 1T1=- unac"nowleded transmission mode on /51 is employed. . M.1 header is used for loical channel
identification (011=- 111=- 1T1=- !=11=- 811=- 8T1=). The data flow shown in 7iure A is applicable.
5.3.5.19 4ata 3"o1 3or 4))< 6a##ed to <S-4S)<
7or 811=- both unac"nowleded and ac"nowleded transmission mode on /51 is employed. Oith M.1<hs
confiuration- a M.1<d header is needed only if 811= and 8T1= loical channels are multiple'ed on the same
M.1<d flow- i.e. the data flow in 7iure Aa is applicable. Oith M.1<ehs confiuration- a M.1<d header is not needed-
i.e. the data flow in 7iure Aa, is applicable.
5.3.5.20 4ata 3"o1 3or 4T)< (%o%-tra%#are%t R!)) 6a##ed to <S-4S)<
Mappin to =!<8!1= implies a 8T1= with ac"nowleded or unac"nowleded transmission on /51. Oith M.1<hs
confiuration- a M.1<d header is needed only if 811= and 8T1= loical channels are multiple'ed on the same
M.1<d flow- i.e. the data flow in 7iure Aa is applicable. Oith M.1<ehs confiuration- a M.1<d header is not needed-
i.e. the data flow in 7iure Aa, is applicable.
5.3.5.21 4ata 3"o1 3or 4))< 6a##ed to *-4)<
7or 811=- both unac"nowleded and ac"nowleded transmission mode on /51 is employed. . M.1 header is
mandatory when the 811= is mapped to the 2<81=- i.e. the data flow in fiure Ab and Ac is applicable.
5.3.5.22 4ata 3"o1 3or 4T)< (%o%-tra%#are%t R!)) 6a##ed to *-4)<
Mappin to 2<81= implies a 8T1= with ac"nowleded or unac"nowleded transmission on /51. . M.1 header is
mandatory when the 8T1= is mapped to the 2<81=- i.e. the data flow in fiure Ab and Ac is applicable.
5.3.5.23 4ata 3"o1 3or M))< (%o%-tra%#are%t R!)) 6a##ed to '$)<
7or M11= mapped to 7.1=- unac"nowleded transmission mode on /51 is employed. %n case of M.1 multiple'in
the M.1 header is needed for loical channel service multiple'in. The data flow in either 7iure @ or 7iure A is
applicable.
5.3.5.2- 4ata 3"o1 3or MS)< (%o%-tra%#are%t R!)) 6a##ed to '$)<
7or M!1= mapped to 7.1=- unac"nowleded transmission mode on /51 is employed. %n case of M.1 multiple'in
the M.1 header is needed for loical channel service multiple'in. The data flow in either 7iure @ or 7iure A is
applicable.
5.3.5.25 4ata 3"o1 3or MT)< (%o%-tra%#are%t R!)) 6a##ed to '$)<
7or MT1= mapped to 7.1=- unac"nowleded transmission mode on /51 is employed. %n case of M.1 multiple'in
the M.1 header is needed for loical channel service multiple'in. The data flow in either 7iure @ or 7iure A is
applicable.
5.3.5.26 4ata 3"o1 3or )))< 6a##ed to <S-4S)<0R$)< ('44 o%"9)
%n 788- for 111=- transparent transmission mode on /51 is employed on the uplin" (when mapped to /.1=).
3nac"nowleded transmission mode on /51 is employed on the downlin" (when mapped to =!<8!1=). . M.1
header is used for loical channel identification (111=). %f the transparent /51 transfer mode is applied- the data flow
7iure ? is applicable. %f the unac"nowleded /51 transfer mode is applied- the data flow 7iure Aa is applicable.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' !' Release 1$
5.3.5.2/ 4ata 3"o1 3or P))< 6a##ed to <S-4S)<
&o /51 header is needed. . M.1 header is mandatory when the P11= is mapped to the =!<8!1=. 7or 788- an =<
/&T% specific for P11= transmission is used on =!<!11= to identify the loical channel carried by the =!<8!1=.
7or ,.*@ Mcps T88- the =!<!11= less operation is used. The loical channel %8 in M.1 header is set to a reserved
value.
5.3.5.2= 4ata 3"o1 3or ;))< 6a##ed to <S-4S)< ('44 a%d 1.2= Mc# T44 o%"9)
&o /51 header is needed- i.e. the transparent data transfer mode of /51 is applied. . M.1 header is mandatory when
the 011= is mapped to the =!<8!1=. .n =</&T% specific for 011= transmission is used on =!<!11= to identify
the loical channel carried by the =!<8!1=. The loical channel %8 in M.1 header is set to a reserved value.
5.3.5.29 4ata 3"o1 3or )))< 6a##ed to <S-4S)<0*-4)< ('44 a%d 1.2= Mc# T44
o%"9)
7or 111= transmission- transparent transmission mode on /51 is employed on the uplin" (when mapped to 2<81=).
3nac"nowleded transmission mode on /51 is employed on the downlin" (when mapped to =!<8!1=). . M.1
header is used for loical channel identification (111=). %f the transparent /51 transfer mode is applied- the data flow
7iure ,+ is applicable. %f the unac"nowleded /51 transfer mode is applied- the data flow 7iure Aa is applicable.
5.3.6 Tra%#ort )ha%%e", !o2ica" )ha%%e" a%d M$)-d 3"o1 (u6&eri%2
The 32 model for transport channel and loical channel numberin is defined by the followinD
< 7or 7.1= transport channelsD
< . transport channel identity is associated with each 7.1= transport channel. 2ach identity is uniCue within
the downlin" 7.1=s mapped onto the same physical channel.
< Transport channel identities can be allocated non seCuentially.
< Transport channel identity is not used to determine the radio bearer mappin. The transport channels that can
be used are determined from the available physical channels.
< 2ach downlin" 811= and 8T1= has a uniCue loical channel identity.
< . M.1 M0M! identity (M0M!<%d) is associated with each M0M! service carried on MT1= on 7.1=.
The identity is uniCue within a 7.1= and the mappin of the M0M! service id to the M0M!<%d is provided
on the M11=.
< 7or /.1= transport channelsD
< . transport channel identity is associated with each /.1= transport channel. 2ach identity is uniCue within
the /.1=s mapped onto the same P/.1=.
< Transport channel identities can be allocated non seCuentially.
< Transport channel identity is not used to determine the radio bearer mappin. The transport channels that can
be used are determined from the available physical channels.
< 2ach uplin" 811= and 8T1= has a uniCue loical channel identity.
< 7or downlin" 81= and 8!1= transport channelsD
< . transport channel identity is associated with each downlin" 81= transport channel. 2ach identity is uniCue
within the downlin" 81=s confiured in the 32E
< Transport channel identities can be allocated non seCuentially.
< . transport channel identity is associated with each 8!1= transport channel. 2ach identity is uniCue within
the 8!1=s confiured in the 32E
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3$ Release 1$
< . loical channel identity is associated with each loical channel that is multiple'ed with other loical
channels before bein mapped to a transport channel. 2ach identity is uniCue within the loical channels
mapped to the same transport channel.
< . loical channel that is mapped to 81= and 8!1= simultaneously in T88 has one loical channel identity.
< 7or =!<8!1=- when M.1<hs is confiuredD
< . M.1<flow identity is associated with each M.1<d flow. 2ach identity is uniCue within the M.1<d flows
confiured in the 32E
< . loical channel identity is associated with each loical channel that is multiple'ed with other loical
channels before bein mapped to a M.1<d flow. 2ach identity is uniCue within the loical channels mapped
to the same M.1<d flowE
< . loical channel that is mapped to 81= and =!<8!1= simultaneously has one loical channel identity.
< 7or =!<8!1=- when M.1<ehs is confiuredD
< . reorderin Cueue identity is associated with each reorderin Cueue. 2ach identity is uniCue within the
reorderin Cueues confiured in the 32E
< . loical channel identity is associated with each loical channel that is mapped to a reorderin Cueue. 2ach
identity is uniCue within the loical channels mapped to any reorderin CueueE
< . loical channel that is mapped to 81= and =!<8!1= simultaneously has one loical channel identity.
< 7or uplin" 81= and 3!1= transport channelsD
< . transport channel identity is associated with each uplin" 81= transport channel. 2ach identity is uniCue
within the uplin" 81=s confiured in the 32E
< Transport channel identities can be allocated non seCuentially.
< . transport channel identity is associated with each 3!1= transport channel. 2ach identity is uniCue within
the 3!1=s confiured in the 32E
< . loical channel identity is associated with each loical channel that is multiple'ed with other loical
channels before bein mapped to a transport channel. 2ach identity is uniCue within the loical channels
mapped to the same transport channel.
< 7or 2<81=- when M.1<e;es is confiuredD
< . M.1<flow identity is associated with each M.1<d flow. 2ach identity is uniCue within the M.1<d flows
confiured in the 32E
< . loical channel identity is associated with each loical channel that is mapped to a M.1<d flow. 2ach
identity is uniCue within the loical channels mapped to any M.1<d flowE
< . 88% (8ata 8escription %dentity) is associated with each M.1<d P83. The 88% values are uniCue within
the 32E
< %n addition to indicatin the M.1<d P83 si(e- the 88% value indicates M.1<d flow and loical channel for
the M.1<d P83 within the M.1<e P83.
< 7or 2<81=- when M.1<i;is is confiuredD
< . M.1<flow identity is associated with each M.1<d flow. 2ach identity is uniCue within the M.1<d flows
confiured in the 32E
< . loical channel identity is associated with each loical channel that is mapped to a M.1<d flow. 2ach
identity is uniCue within the loical channels mapped to any M.1<d flowE
< . 51=<%8 (5oical channel identity) is associated with each M.1<d P83. The 51=<%8 values indicate the
loical channel for the M.1<d P83 within the M.1<i P83.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 31 Release 1$
< %n 788 only- when the 32 is in 1255N7.1= state- an 2</&T% is associated with each M.1<d P83 until an
2<.G1= with the 32Ps 2</&T% has been received (throuh an %8<specific 1/1 attachment).
7or 788 and ,.*@ Mcps T88- one 51=<id value in the M.1<is header identifies M.1<d flows containin
111= data.
5.- !a9er 3 - Uu Stratu6 Ser5ice a%d 'u%ctio%
This subclause provides an overview on 5ayer 3 services and functions provided by the 3u !tratum as a whole. .
detailed description of the //1 protocol is iven in F,,G. 2'amples of structured procedures involvin //1 in %dle
Mode and 1onnected Mode are described in F:G and F>G- respectively.
5.-.1 Uu Stratu6 er5ice
5.-.1.1 Ge%era" )o%tro"
The G1 !.P provides an information broadcast service. This service broadcasts information to all 32s in a certain
eoraphical area. The basic reCuirements from such service areD
# %t should be possible to broadcast non<access stratum information in a certain eoraphical area.
# The information is transferred on an unac"nowleded mode lin". 3nac"nowleded mode means that the delivery
of the broadcast information can not be uaranteed (typically no retransmission scheme is used). %t seems
reasonable to use an unac"nowleded mode lin" since the information is broadcast to a lot of 32s and since
broadcast information often is repeated periodically.
# %t should be possible to do repeated transmissions of the broadcast information (how it is repeated is controlled
by the non<access stratum).
# The point where the 32 received the broadcast information should be included- when the access stratum delivers
broadcast information to the non<access stratum.
5.-.1.2 (oti3icatio%
The &t !.P provides pain and notification broadcast services. The pain service sends information to a specific
32(s). The information is broadcast in a certain eoraphical area but addressed to a specific 32(s). The basic
reCuirements from such service areD
# %t should be possible to broadcast pain information to a number of 32s in a certain eoraphical area.
# The information is transferred on an unac"nowleded mode lin". %t is assumed that the protocol entities in non<
access stratum handle any "ind of retransmission of pain information.
The notification broadcast service broadcasts information to all 32s in a certain eoraphical. The basic reCuirements
from this service are typically the same as for the information broadcast service of the G1 !.PD
# %t should be possible to broadcast notification information in a certain eoraphical area.
# The information is transferred on an unac"nowleded mode lin".
5.-.1.3 4edicated )o%tro"
The 81 !.P provides services for establishment;release of a connection and transfer of messaes usin this connection.
%t should also be possible to transfer a messae durin the establishment phase. The basic reCuirements from the
establishment;release services areD
# %t should be possible to establish connections (both point and roup connections).
# %t should be possible to transfer an initial messae durin the connection establishment phase. This messae
transfer has the same reCuirements as the information transfer service.
# %t should be possible to release connections.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3! Release 1$
The information transfer service sends a messae usin the earlier established connection. .ccordin to F,G it is possible
to specify the Cuality of service reCuirements for each messae. . finite number of Cuality of service classes will be
specified in F,G- but currently no class has been specified. %n order to et an idea of the basic reCuirements- the 11 and
MM protocols in G!M are used as a reference. . G!M based core networ" is chosen since it is one main option for
3MT!. 1onsiderin the e'istin G!M specification of 11 and MM the basic reCuirements from the information
transfer service provided by the #8uplication avoidance# function are (these are some of the services provided by the
combination of a duplication layer- // and the data lin" layer in G!M)D
# %n<seCuence transfer of messaes
Messaes are delivered to the &.! on the receiver side e'actly in the order they have been submitted by the
&.! on the sendin side- without loss or duplication- e'cept possibly for the loss of last messaes in case of
connection abortion.
# Priority handlin
%f !M! messaes should be transported throuh the control plane it should be possible to ive hiher priority to
sinallin messaes.
The 11 and MM protocols also e'pect other services- which can not be supported by the current primitives of the 81
!.P- e.. indication of radio lin" failure.
The information transfer service is provided by a combination of the services provided by the data lin" layer- /&1 and
the #8uplication avoidance# function.
5.-.2 RR) 3u%ctio%
The /adio /esource 1ontrol (//1) layer handles the control plane sinallin of 5ayer 3 between the 32s and 3T/.&.
The //1 performs the followin functionsD
# Broa,&ast of information )rovi,e, 4y the non#a&&ess strat3m (Core 9et/or0). The //1 layer performs
system information broadcastin from the networ" to all 32s. The system information is normally repeated on a
reular basis. The //1 layer performs the schedulin- sementation and repetition. This function supports
broadcast of hiher layer (above //1) information. This information may be cell specific or not. .s an e'ample
//1 may broadcast 1ore &etwor" location service area information related to some specific cells.
# Broa,&ast of information re-ate, to the a&&ess strat3m. The //1 layer performs system information
broadcastin from the networ" to all 32s. The system information is normally repeated on a reular basis. The
//1 layer performs the schedulin- sementation and repetition. This function supports broadcast of typically
cell<specific information.
# 1sta4-ishment; re#esta4-ishment; maintenan&e an, re-ease of an RRC &onne&tion 4et/een the *1 an,
*(RA9. The establishment of an //1 connection is initiated by a reCuest from hiher layers at the 32 side to
establish the first !inallin 1onnection for the 32. The establishment of an //1 connection includes an
optional cell re<selection- an admission control- and a layer * sinallin lin" establishment. The release of an
//1 connection can be initiated by a reCuest from hiher layers to release the last !inallin 1onnection for the
32 or by the //1 layer itself in case of //1 connection failure. %n case of connection loss- the 32 reCuests re<
establishment of the //1 connection. %n case of //1 connection failure- //1 releases resources associated
with the //1 connection.
# 1sta4-ishment; re&onfig3ration an, re-ease of Ra,io Bearers. The //1 layer can- on reCuest from hiher
layers- perform the establishment- reconfiuration and release of /adio 0earers in the user plane. . number of
/adio 0earers can be established to an 32 at the same time. .t establishment and reconfiuration- the //1 layer
performs admission control and selects parameters describin the /adio 0earer processin in layer * and layer ,-
based on information from hiher layers.
# Assignment; re&onfig3ration an, re-ease of ra,io reso3r&es for the RRC &onne&tion. The //1 layer handles
the assinment of radio resources (e.. codes) needed for the //1 connection includin needs from both the
control and user plane. The //1 layer may reconfiure radio resources durin an established //1 connection.
This function includes coordination of the radio resource allocation between multiple radio bearers related to the
same //1 connection. //1 controls the radio resources in the uplin" and downlin" such that 32 and 3T/.&
can communicate usin unbalanced radio resources (asymmetric uplin" and downlin"). //1 sinals to the 32 to
indicate resource allocations for purposes of handover to G!M or other radio systems.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 33 Release 1$
# RRC &onne&tion mo4i-ity f3n&tions. The //1 layer performs evaluation- decision and e'ecution related to
//1 connection mobility durin an established //1 connection- such as handover- preparation of handover to
G!M or other systems- cell re<selection and cell;pain area update procedures- based on e.. measurements
done by the 32.
# Paging/notifi&ation. The //1 layer can broadcast pain information from the networ" to selected 32s. =iher
layers on the networ" side can reCuest pain and notification. The //1 layer can also initiate pain durin an
established //1 connection.
# Ro3ting of higher -ayer P*s. This function performs at the 32 side routin of hiher layer P83s to the
correct hiher layer entity- at the 3T/.& side to the correct /.&.P entity.
# Contro- of re83este, 7o+. This function shall ensure that the Io! reCuested for the /adio 0earers can be met.
This includes the allocation of a sufficient number of radio resources.
# *1 meas3rement re)orting an, &ontro- of the re)orting. The measurements performed by the 32 are
controlled by the //1 layer- in terms of what to measure- when to measure and how to report- includin both
3MT! air interface and other systems. The //1 layer also performs the reportin of the measurements from the
32 to the networ".
# <3ter -oo) )o/er &ontro-. The //1 layer controls settin of the taret of the closed loop power control.
# Contro- of &i)hering. The //1 layer provides procedures for settin of cipherin (on;off) between the 32 and
3T/.&. 8etails of the security architecture are specified in F,:G.
# +-o/ CA. .llocation of preferred radio resources based on lon<term decision criteria. %t is applicable only in
T88 mode.
- Ar4itration of ra,io reso3r&es on 3)-in0 C!. This function controls the allocation of radio resources on
uplin" 81= on a fast basis- usin a broadcast channel to send control information to all involved users.
&OT2D This function is implemented in the 1/&1.
# 5nitia- &e-- se-e&tion an, re#se-e&tion in i,-e mo,e. !election of the most suitable cell based on idle mode
measurements and cell selection criteria.
# 5ntegrity )rote&tion. This function adds a Messae .uthentication 1ode (M.1<%) to those //1 messaes that
are considered sensitive and;or contain sensitive information. The mechanism how the M.1<% is calculated is
described in F,9G.
# 5nitia- Config3ration for CB+
This function performs the initial confiuration of the 0M1 sublayer.
< A--o&ation of ra,io reso3r&es for CB+
This function allocates radio resources for 10! based on traffic volume reCuirements indicated by 0M1. The
radio resource allocation set by //1 (i.e. the schedule for mappin of 1T1= onto 7.1=;!<11P1=) is
indicated to 0M1 to enable eneration of schedule messaes. The resource allocation for 10! shall be broadcast
as system information.
# Config3ration for CB+ ,is&ontin3o3s re&e)tion
This function confiures the lower layers (5,- 5*) of the 32 when it shall listen to the resources allocated for
10! based on schedulin information received from 0M1.
# (iming a,van&e &ontro-. The //1 controls the operation of timin advance. %t is applicable only in 3.@9;?.>@
Mcps T88.
# MBM+ &ontro-. The //1 controls the operation of M0M! point<to<point and point<to<multipoint radio bearers.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3( Release 1$
5.5 8%teractio% &et1ee% RR) a%d "o1er "a9er i% the ) #"a%e
R R )
R R )
R ! )
R ! )
/adio /esource
.ssinment
F1ode- 7reCuency-
T!- T7 !et- Mappin-
etc.G
Measurement /eport
/51 retransmission
control
! 1
! 1
3 T / . & 3 2
1
o
n
t
r
o
l
M
e
a
s
u
r
e
m
e
n
t
s
1
o
n
t
r
o
l
M
e
a
s
u
r
e
m
e
n
t
s
1
o
n
t
r
o
l
M
e
a
s
u
r
e
m
e
n
t
s
1
o
n
t
r
o
l
M
e
a
s
u
r
e
m
e
n
t
s
M $ )
M $ )
1
o
n
t
r
o
l
1
o
n
t
r
o
l
,i-ure 1$. Interactions 3etween RR9 and lower la4ers
The //1 protocol controls and sinals the allocation of radio resources to the 32. //1 allows M.1 to arbitrate
between users and /adio 0earers within the radio resource allocation. The //1 uses the measurements done by the
lower layers to determine which radio resources that are available. Therefore it is a need for a measurement report from
the 32 //1 to the 3T/.& //1. 7iure ,+ illustrates the principle. The local control and local measurements
reportin is handled throuh the control !.Ps between //1 and the lower layers.
5.6 Protoco" ter6i%atio%
This subclause specifies in which node of the 3T/.& the radio interface protocols are terminated- i.e. where within
3T/.& the respective protocol services are accessible. 8ashed lines indicate those protocols whose presence is
dependent on the service provided to upper layers.
5.6.1 Protoco" ter6i%atio% 3or 4)<
7iure ,, and 7iure ,* show the protocol termination for 81= for the control and user planes- respectively. The part
of physical layer terminatin in the !ervin /&1 is the topmost macro<diversity combinin and splittin function for
the 788 mode. %f no macrodiversity applies- the physical layer is terminated in &ode 0.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3" Release 1$
32 &ode0
//1
/51
P=K
P=K
!/&1
//1
/51
P=K
M.1 M.1
,i-ure 11. Protocol Ter/ination for 89:6 control plane
P81P P81P
32 &ode0
/51
P=K
P=K
!/&1
/51
P=K
M.1 M.1
,i-ure 1!. Protocol Ter/ination for 89:6 user plane
5.6.2 Protoco" ter6i%atio% 3or R$)<0'$)<
7iure ,3 and 7iure ,9 show the protocol termination for /.1=;7.1= for the control and user planes- respectively.
1ontrol plane termination refers to the case where /.1=;7.1= carry dedicated- common or shared control
information (i.e. 111=- 811= or !=11=- and in the downlin" possibly also 011=). 3ser plane termination refers to
the case where /.1=;7.1= carry dedicated user data (8T1=) or common user data (1T1=).
%t is assumed that macrodiversity;soft handover is not applied for /.1=;7.1=. Therefore- the physical layer
terminates in &ode 0. 7or /.1=;7.1= carryin 811=- M.1 is split between 1ontrollin and !ervin /&1. /51-
and in the 1 plane also //1 terminate in the !ervin /&1. !ince %ur can support common channel data streams- the
users of that common channel can depend on different !/&1s. =owever- they depend on the same 1ontrollin /&1.
Therefore- for a iven user- the 1ontrollin /&1 and the !ervin /&1 can be separate /&1s.
7or 7.1= carryin 011=- M.1- /51 and //1 are terminated in the 1/&1.
7or /.1=;7.1= carryin !=11=- M.1- /51 and //1 are terminated in the 1ontrollin /&1 (T88 only).
7or /.1=;7.1= carryin 111=- M.1- /51 and //1 are terminated in the /&1.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3) Release 1$
32
&ode 0
P=K P=K
/&1
M.1
M.1
//1
/51
//1
/51
CCC! :
CC!:
32
&ode 0
P=K P=K
!/&1
M.1
//1
/51
//1
/51
M.1
M.1
1/&1
32
&ode 0
P=K P=K
M.1
M.1
//1
/51
//1
/51
BCC! :
1/&1
32
&ode 0
P=K P=K
1ontrollin
/&1
M.1
M.1
//1
/51
//1
/51
+!CC!:
(T88 only)
,i-ure 13. Protocol Ter/ination for RA9:;,A9:6 control plane
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3* Release 1$
32
&ode 0
P=K P=K
1ontrollin
/&1
!/&1
M.1
/51 /51
M.1
M.1
(C!:
32
&ode 0
P=K P=K
/&1
M.1
M.1
/51 /51
C(C!:
0M1
0M1
P81P
P81P
32
&ode 0
P=K P=K
1ontrollin
/&1
!/&1
M.1
/51 /51
M.1
M.1
,i-ure 1(. Protocol Ter/ination for RA9:;,A9:6 user plane
5.6.3 Void
5.6.- Void
5.6.5 Protoco" ter6i%atio% 3or 4S)<
5.6.5.1 4S)< de3i%itio%
The 8!1= is only supported for T88. The 8!1= is a resource that e'ists in downlin" only. %t has only impact on the
physical and transport channel levels- so there is no definition of shared channel in the loical channels provided by
M.1.
The 8!1= is a transport channel shared dynamically between several 32s. The 8!1= is mapped to one or several
physical channels such that a specified part of the downlin" resources is employed. 7or the 8!1= no macrodiversity is
applied- i.e. a specific 8!1= is transmitted in a sinle cell only.
The 8!1= is defined as a shared downlin" channel for which resource allocation is performed by //1 in 1ontrollin
/&1. The allocation messaes- includin 32 identification- are transmitted on !=11=- which is mapped on
/.1=;7.1=. !everal 8!1= can be multiple'ed on a 11Tr1= in the physical layer- the transport formats of the
8!1=s have to be selected from the transport format combination set of this 11Tr1=. 2ach 11Tr1= is mapped on one
or more P8!1=s. %f the transport format combination subset of a 11Tr1= contains more than one transport format
combination- a T71% can be transmitted inside the P8!1=- or blind detection can be applied in the 32.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3+ Release 1$
%nterleavin for the 8!1= may be applied over a multiplicity of radio frames. &evertheless- here the basic case is
considered where the interleavin is rectanular for a iven M.1 P83- and eCual to one radio frame (,+ ms). The
framin is synchronised on the !1=.
%n every radio frame- one or several P8!1=s can be used in the downlin". Therefore- the 8!1= supports code
multiple'in. M.1 multiple'in of different 32s shall not be applied within a radio frame- i.e. within one radio frame
a P8!1= is assined to a sinle 32. =owever- M.1 multiple'in is allowed on a frame by frame basis- i.e. one
P8!1= may be allocated to different 32s at each frame.
Transport bloc"s on the 8!1= may be of constant si(e- so that the Transport 0loc" !et may be derived from the code
allocated to each 32 on the 8!1=. 7or case 0- the transport format combination set can chane with each transmission
time interval.
5.6.5.2 Reource a""ocatio% a%d U* ide%ti3icatio% o% 4S)<
The principles of capacity allocation and 32 identification on the 8!1= are described in more detail below.
5.6.5.2.1 Void
5.6.5.2.2 U* re>uire a do1%"i%7 S<))<
The information which physical downlin" shared channels to listen to and when- is sent by //1 on the !=11= loical
channel- which is mapped on /.1= and 3!1=;7.1= and 8!1=. The transmitted 5ayer 3 messaes contain
information about the used P8!1=s and the timin of the allocation.
5.6.5.3 Mode" o3 4S)< i% UTR$(
7iure ,: captures the wor"in assumption on the 8ownlin" !hared 1hannel (8!1=). The two /51s point to loical
channel (8T1=) specific /51<entities of specific users while M.1 refers to the provision of M.1 sublayer functions
for all users.
The M.1 sublayer of a 8!1= is split between the 1ontrollin /&1 and !/&1. 7or a iven user- the /51 sublayer is
terminated in its !/&1. !ince %ur can support 8!1= data streams- the users on that 8!1= can depend on different
!/&1s. 7or a iven user- the 1ontrollin /&1 and the !ervin /&1 can be separate /&1s. The M.1 in the networ"
ta"es care of mappin downlin" data either to a common channel (7.1=- not shown in this fiure)- or to a 81= and;or
the 8!1=.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' 3' Release 1$

32*
M.1
/51*
!/&1 , !/&1 *
8!1=
8ata for
32 ,Q*
32,
!/&1s
/51,
1ontrollin /&1
&ode 0
%ur or local
M.1<d, M.1<d*
32
3u
M.1<c;sh;m
!inallin
for 32 ,Q*
/51
/.1=;
7.1=
,i-ure 1". 1odel of downlink shared channel (8S9: in 0TRAN (T88 onl4
5.6.5.- Protoco" ter6i%atio%
The protocol termination points for 8!1= in control and user planes are presented in 7iure ,> and 7iure ,?-
respectively. The 8!1= is for T88 only.
32
&ode 0
//1
/51
P=K P=K
M.1
1ontrollin
/&1
!/&1
//1
/51
M.1
M.1 M.1
,i-ure 1). Protocol ter/ination points for 8S9:6 control plane (T88 onl4
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' ($ Release 1$
P81P
P81P
32
&ode 0
/51
P=K P=K
M.1
1ontrollin
/&1
!/&1
/51
M.1
M.1 M.1
,i-ure 1*. Protocol ter/ination points for 8S9:6 user plane (T88 onl4
5.6.6 Protoco" ter6i%atio% 3or tra%#ort cha%%e" o3 t9#e US)<
5.6.6.1 US)< de3i%itio%
The 3!1= is only supported for T88. %t is a resource that e'ists in uplin" only. %t has only impact on the physical and
transport channel levels- so there is no definition of shared channel in the loical channels provided by M.1.
The 3!1= is a transport channel shared dynamically between several 32s. The 3!1= is mapped to one or several
physical channels such that a specified part of the uplin" resources is employed.
The 3!1= is defined as a shared uplin" channel for which resource allocation is performed by //1 in 1ontrollin
/&1. The allocation reCuests and allocation messaes- includin 32 identification- are transmitted on !=11=- which
is mapped on /.1= and 3!1=;7.1= and 8!1=. !everal 3!1=s can be multiple'ed on a 11Tr1= in the physical
layer- the transport formats of the 3!1=s have to be selected from the transport format combination set of this
11Tr1=. 2ach 11Tr1= is mapped on one or more P3!1=s. %f the transport format combination subset of a 11Tr1=
contains more than one transport format combination- a T71% can be transmitted inside the P3!1=- or blind detection
can be applied in the &ode 0.
%nterleavin for the 3!1= may be applied over a multiplicity of radio frames.
%n every radio frame- one or several P3!1=s can be used in the uplin". Therefore- the 3!1= supports physical channel
multiple'in. M.1 multiple'in of different 32s shall not be applied within a radio frame- i.e. within one radio frame
a P3!1= is assined to a sinle 32. =owever- M.1 multiple'in is allowed on a frame by frame basis- i.e. one
P3!1= may be allocated to different 32s at each frame.
The transport format combination set on the 3!1= can chane with each transmission time interval.
5.6.6.2 Reource a""ocatio% a%d U* ide%ti3icatio% o% US)<
The information which physical uplin" shared channels to transmit on and when is sent by //1 on the !=11= loical
channel- which is mapped on /.1= and 3!1=;7.1= and 8!1=. The transmitted 5ayer 3 messaes contain
information about the assined P3!1=s and the timin of the allocation.
5.6.6.3 Mode" o3 US)< i% UTR$(
7iure ,@ captures the wor"in assumption on the 3plin" !hared 1hannel (3!1=). The two /51s point to loical
channel (8T1=) specific /51<entities of specific users while M.1 refers to the provision of M.1 sublayer functions
for all users.
The M.1 sublayer of a 3!1= is split between the 1ontrollin /&1 and !/&1. 7or a iven user- the /51 sublayer is
terminated in its !/&1. !ince %ur can support 3!1= data streams- the users on that 3!1= can depend on different
!/&1s. 7or a iven user- the 1ontrollin /&1 and the !ervin /&1 can be separate /&1s. The M.1 in the networ"
ta"es care of mappin uplin" data either from a common channel (/.1=- not shown in this fiure)- 81= or the 3!1=.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (1 Release 1$
.llocations of uplin" capacity are reCuested by the 32s and sinalled to the 32s on the !=11= (!hared channel
control channel)- which is mapped on /.1= and 3!1=;7.1= and 8!1=.
32*
M.1
/51*
!/&1 , !/&1 *
3!1=
8ata for
32 ,Q*
32,
!/&1s
/51,
1ontrollin /&1
&ode 0
%ur or local
M.1<d, M.1<d*
32
3u
M.1<c;sh
!inallin
for 32 ,Q*
/51
/.1=;
7.1=
,i-ure 1+. 1odel of uplink shared channel (0S9: in 0TRAN (T88 onl4
5.6.6.- Protoco" ter6i%atio%
The protocol termination points for 3!1= in control and user planes are presented in 7iure ,A and 7iure *+-
respectively. The 3!1= is for T88 only.
32
&ode 0
//1
/51
P=K P=K
M.1
1ontrollin
/&1
!/&1
//1
/51
M.1
M.1 M.1
,i-ure 1'. Protocol ter/ination points for 0S9:6 control plane (T88 onl4
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (! Release 1$
32
&ode 0
/51
P=K P=K
M.1
1ontrollin
/&1
!/&1
/51
M.1
M.1 M.1
,i-ure !$. Protocol ter/ination points for 0S9:6 user plane (T88 onl4
5.6./ Protoco" ter6i%atio% 3or tra%#ort cha%%e" o3 t9#e ;)<
!ystem information on 01= can include information that is available only in &ode 0- and need to be updated very
freCuently (each *+<,++ ms)- such as uplin" interference in the cell. .lso- for the system information oriinatin from
the /&1- it is assumed that the updatin of system information is at least one manitude less (minutes) than the
repetition freCuency on the 01= (in the order of ,s). The system information oriinatin from the 1/&1 should be sent
transparently to &ode 0- which then handles the repetition. Protocol termination for the 01= shall therefore be
distributed between the &ode 0 and the 1/&1- resultin in less sinallin on %ub and lower processor load. &ote that
the /51 sublayer is transparent for this transport channel type.
32 &ode0
/51
M.1
P=K
/51
M.1
P=K
//1
//1
//1
1/&1
,i-ure !1. Protocol ter/ination for <9:
5.6.= Protoco" ter6i%atio% 3or tra%#ort cha%%e" o3 t9#e P)<
%n order to enable co<ordinated schedulin between P1= and 7.1=;8!1= the correspondin M.1 schedulin
functions shall be allocated in the same node. M.1<c;sh is terminated in 1/&1. . natural implication is that /51 and
//1 also are terminated in 1/&1.
&ote that the /51 sublayer is transparent for this channel.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (3 Release 1$
32
&ode 0
//1
P=K P=K
M.1
1ontrollin
/&1
//1
M.1
/51 /51
,i-ure !!. Protocol ter/ination for P9:
5.6.9 Protoco" ter6i%atio% 3or <S-4S)<
5.6.9.1 <S-4S)< de3i%itio%
The =!<8!1= is a resource that e'ists in downlin" only. %t has only impact on the physical and transport channel
levels- so there is no definition of shared channel in the loical channels provided by M.1.
The =!<8!1= is a transport channel for which a common pool of radio resources is shared dynamically between
several 32s. The =!<8!1= is mapped to one or several physical channels such that a specified part of the downlin"
resources is employed. 7or the =!<8!1= no macrodiversity is applied- i.e. a specific =!<8!1= is transmitted in a
sinle cell only.
< %n 1255N81= state the =!<8!1= is defined as an e'tension to 81= transmission. Physical channel sinallin
is used for indicatin to a 32 when it has been scheduled and then the necessary sinallin information for the
32 to decode the =!<P8!1=.
< %n 788 and ,.*@ Mcps T88 mode- the =!<8!1= can be used to transmit both dedicated control plane and user
plane data to the 32 in 1255N7.1=- 1255NP1= and 3/.NP1= state.
%n every =!<8!1= TT%- one or several =!<P8!1=s can be used in the downlin". Therefore- the =!<8!1= supports
code multiple'in. M.1 multiple'in of different 32s shall not be applied within an =!<8!1= TT%- i.e. within one
=!<8!1= TT% an =!<P8!1= is assined to a sinle 32. =owever- M.1 multiple'in is allowed on a TT% by TT%
basis- i.e. one =!<P8!1= may be allocated to different 32s at each TT%.
5.6.9.2 Reource a""ocatio% a%d U* ide%ti3icatio% o% <S-4S)<
7or each =!<8!1= TT%- each =!<!11= carries =!<8!1= related downlin" sinallin for one 32- alon with a 32
identity (via a 32 specific 1/1) that identifies the 32 for which this information is necessary in order to decode the
scheduled =!<P8!1=.
5.6.9.3 Protoco" ter6i%atio%
The protocol termination points for =!<8!1= in the control (811=) and user planes (8T1=) are presented in fiure
:.>.A.3<, and fiure :.>.A.3<*- respectively. %n 788 and ,.*@ Mcps T88- the protocol termination presented in fiure
:.>.A.3<, applies for 011= and P11= in 1255N7.1=- 1255NP1= or 3/.NP1= state. Two confiurations e'ist- a
1onfiuration with M.1<c;sh and a 1onfiuration without M.1<c;sh.
< 1onfiuration with M.1<c;shD %n this case- the M.1<hs;M.1<ehs in &ode 0 is located below M.1<c;sh in
1/&1.
< 1onfiuration without M.1<c;shD %n this case- the 1/&1 does not have any function for the =!<8!1=. M.1<d
in !/&1 is located directly above M.1<hs;M.1<ehs in &ode 0- i.e. in the =!<8!1= the !/&1 is directly
connected to the &ode 0- thus bypassin the 8/&1.
0oth confiurations are transparent to both the 32 and &ode 0. 7iures :.>.A.3<* and :.>.A.3<3 show the respective user
plane protocol architecture with termination points for the above two confiurations.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (( Release 1$
CCC! = CC! :
BCC! = PCC! (. an, 1.22 M&)s ( on-y):


32 &ode 0
//1
/51
P=K P=K
!/&1
//1
/51
M.1
M.1
M.1 M.1
,i-ure "#)#'#3&1. Protocol ter/ination points for :S&8S9:6 control plane
32 &ode 0
/51
P=K P=K
!/&1
/51
M.1 M.1
M.1 M.1
P81P
P81P
,i-ure "#)#'#3&!. Protocol ter/ination points for :S&8S9:6 user plane
5.6.10 Protoco" ter6i%atio% 3or *-4)<
5.6.10.1 *-4)< de3i%itio%
The 2<81= is a resource that e'ists in uplin" only. %t has only impact on the physical and transport channel levels- it is
not visible in the loical channels provided by M.1.
The 2<81= is a transport channel that is subject to &ode<0 schedulin. The 2<81= is defined as an e'tension to 81=
transmission.
5.6.10.2 Reource a""ocatio% a%d U* ide%ti3icatio% re"ated to *-4)<
Physical channel sinallin from the &ode<0 is used for indicatin to the 32 what amount of uplin" resources it is
allowed to use. .lso the 32 sends schedulin reCuests to the &ode<0 about the resource needs.
!chedulin information is sent on a common physical channel and a 32 identity is used to address the different 32s.
5.6.10.3 Protoco" ter6i%atio%
The protocol termination points for 2<81= in the control and user planes are presented in fiure :.>.,+.3<, and fiure
:.>.,+.3<*- respectively.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (" Release 1$

32 &ode 0
//1
/51
P=K P=K
!/&1
//1
/51
M.1 M.1
M.1 M.1
,i-ure "#)#1$#3&1. Protocol ter/ination points for 7&89: for 899:6 control plane

32 &ode 0
/51
P=K P=K
!/&1
/51
M.1 M.1
M.1 M.1
P81P
P81P
,i-ure "#)#1$#3&!. Protocol ter/ination points for 7&89:6 user plane

32 &ode 0
/51
P=K P=K
1/&1
/51
M.1 M.1
M.1 M.1
//1
//1
,i-ure "#)#1$#3&3. Protocol ter/ination points for 7&89: for 999:6 control plane
5.6.11 Protoco" ter6i%atio% 3or M;MS
5.6.11.1 M;MS de3i%itio%
The M0M! feature is downlin" unidirectional.
M0M! services can be provided in point<to<point and point<to<multipoint. 7or the point<to<multipoint there e'ist three
loical channels specifically for M0M!D M11=- M!1= and MT1=.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' () Release 1$
5.6.11.2 Reource a""ocatio% re"ated to M;MS
The radio bearer allocation for the M11= is indicated in system information on the 011=. The radio bearer allocations
for M!1= and MT1= are indicated on M11=.
5.6.11.3 Protoco" ter6i%atio%
The protocol termination points for M11= and M!1= in the control plane and MT1= in the user plane are presented
in fiure :.>.,,.3<, and fiure :.>.,,.3<*- respectively.

32
&ode 0
//1
P=K P=K
M.1
1ontrollin
/&1
M.1
/51
//1
/51
,i-ure "#)#11#3&1. Protocol ter/ination points for 199: and 1S9:6 control plane

32
&ode 0
P81P
P=K P=K
M.1
1ontrollin
/&1
M.1
/51
P81P
/51
,i-ure "#)#11#3&!. Protocol ter/ination points for 1T9:6 user plane
7iure :.>.,,.3<3 illustrates the protocol termination for MT1= in M0M!- which is used in p<t<m transmission in case
of %P Multicast distribution.
0ased on the confiuration in 0M<!1 the P81P sub<layer may perform header compression;decompression for the
M0M! traffic.
The P81P sub<layer may operate with the /71 3+A: header compression protocol. %n that case- header compression
should be performed under /71 3+A: 3<mode.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (* Release 1$

32
&ode 0
P81P
P=K P=K
M.1
1ontrollin
/&1
M.1
/51
/51
0M<!1
!K&1
P81P
!K&1
T&5 T&5
,i-ure "#)#11#3&3. Protocol Stack for 1T9: (P&T&1 in case of IP /ulticast distri3ution
%n case M/&1 is used- fiure :.>.,,.3<9 illustrates the protocol termination for M11= in M0M!- which is M0M! p<t<
m control channel.
M0!7& M11= %nformation 1ontrol function is split between M/&1 and 1/&1. The M/&1 controls the loical
resources of the /&!s that are used for M0!7& operation within the M0!7& cluster(s). The M/&1 informs the
1/&1 of the M11= confiuration (usin transfer of M11= %nformation 1ontrol messaes) and schedule information
to be used (included in /&!.P as defined in F*+G) .The 1/&1 performs the M11= confiuration and sends the
M11= information accordinly.

32
&ode 0
//1
P=K P=K
M.1
1ontrollin
/&1
M.1
/51
//1
/51
/&!.P
M0M! Master
/&1
/&!.P
M11= %1
M11= %1
,i-ure "#)#11#3&(. Protocol Stack for 199:
6 Uer 8de%ti3icatio% a%d RR) )o%%ectio% Mo&i"it9
6.1 U* ide%ti3icatio% o% the radio i%ter3ace
. /adio &etwor" Temporary %dentity (/&T%) is used as an 32 identifier on /.1=;7.1=- or- for T88 mode- also on
8!1= by the //1- or on P1= by the //1- when a //1 connection e'ists. 7or the =!<8!1= the 32 identification is
included by the physical layer with the help of a 32<specific 1/1.
efinition of *1 i,entifiers
!everal types of /&T%s e'ist. One is used within the !ervin /&1 and it is denoted by !ervin /&1 /&T% (!</&T%).
. second type is used within a cell controlled by a 1/&1- when applicable- and it is denoted by 1ell /&T% (1</&T%).
. third type is used only for T88 within a cell controlled by a 1/&1 when a 8!1= is allocated and it is denoted by
8!1=</&T%. . fourth type is used within a cell controlled by a 1/&1 when an =!<8!1= is confiured and it is
denoted by =!<8!1=</&T% (=</&T%). . fifth type is used within a cell when an 2<81= is confiured to a 32 and it
is denoted by 2</&T%.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (+ Release 1$
!</&T% is allocated for all 32s havin a //1 connection. %t is allocated by the !ervin /&1 and it is uniCue within the
!ervin /&1. !</&T% is reallocated always when the !ervin /&1 for the //1 connection is chaned and deallocated
when the //1 connection is released.
%n addition for each 32 havin an //1 connection- there is an identifier of its current servin /&1- which is denoted
as !/&1 identifier. The !/&1 identifier toether with !</&T% is a uniCue identifier of the //1 connection within
P5M&. The combination of !/&1 identifier and !</&T% is referred to as 3</&T% (3T/.& /adio &etwor" Temporary
%dentity)- which is used on the radio interface.
1</&T% for a 32 is allocated by a controllin /&1 and it is uniCue within one cell controlled by the allocatin 1/&1.
1</&T% can be reallocated when a 32 accesses a new cell with the cell update procedure.
%n T88 mode- 8!1=</&T% for a 32 is allocated by controllin /&1 when a 8!1= channel is confiured. 8!1=<
/&T% is uniCue within the cell carryin the 8!1=.
Ohen a 32 is in 1255N81= state- =</&T% for the 32 is allocated by a controllin /&1 and it is uniCue within one
cell controlled by the allocatin 1/&1. =</&T% is reallocated when an =!<8!1= cell chane is performed. %n 788
and ,.*@ Mcps T88 mode- when a 32 is in 1255N7.1=- 1255NP1= or 3/.NP1= state- =</&T% for the 32 is
allocated by a controllin /&1 and it may be uniCue or shared amon users within one cell controlled by the allocatin
1/&1.
2</&T% for a 32 is allocated by the &ode<0 and it is valid within one cell. 2</&T% may be reallocated when the
servin 2<81= cell chanes. !everal 32s may use the same 2</&T%. The 2</&T% may be allocated to a 32 in
1255N81=- 1255N7.1= (788 and ,.*@ Mcps T88 only) and 1255NP1= (788 and ,.*@ Mcps T88 only).
*sage of *1 i,entifiers
3</&T% is allocated to an 32 havin a //1 connection. %t identifies the 32 within 3T/.& and is used as a 32
identifier in cell update- 3/. update- //1 connection reestablishment and (3T/.& oriinated) pain messaes and
associated responses on the radio interface. The !/&1 identifier within the 3</&T% is used by the 1ontrollin /&1 to
route the received uplin" messaes towards the !ervin /&1.
1</&T% is used as a 32 identifier in all other 811=;8T1= common channel messaes on the radio interface.
%n T88 mode- 8!1=</&T% is used as a 32 identifier for 8T1= and 811= in downlin" when mapped onto 8!1=
transport channel.
=</&T% is used as a 32 identifier for the =!<8!1=.
2</&T% is used as a 32 identifier when controllin 32 uplin" resources on the 2<81=.
&.! identifiers are used as the 32 identifier in the initial access 111= messae on the radio interface.
6.2 U* co%%ectio% to UTR$(
The different levels of 32 connection to 3T/.& are listed belowD
# &o sinallin connection e'ist
The 32 has no relation to 3T/.&- only to 1&. 7or data transfer- a sinallin connection has to be established.
# !inallin connection e'ist
There is a //1 connection between 32 and 3T/.&. The 32 position can be "nown on different levelsD
# 3T/.& /eistration .rea (3/.) level
The 32 position is "nown on 3T/.& reistration area level. 3/. is a specified set of cell- which can be
identified on the 011=.
# 1ell level
The 32 position is "nown on cell level. 8ifferent channel types can be used for data transferD
# 1ommon transport channels (/.1=- 7.1=- 8!1=- =!<8!1=- 2<81=)E
# 8edicated transport channels (81=- 2<81=).
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' (' Release 1$
/ U* 6ode
Two modes of operation are currently defined for the 32- idle mode and connected mode F:- >G.
.fter power on- the 32 stays in idle mode until it transmits a reCuest to establish an //1 connection. %n idle mode the
32 is identified by non<access stratum identities such as %M!%- TM!% and P<TM!%. %n addition- the 3T/.& has no own
information about the individual idle mode 32s- and can only address e.. all 32s in a cell or all 32s monitorin a
specific pain occasion.
The connected mode is entered when the //1 connection is established. . //1 connection is established between the
32 and a /&1 called !/&1. The 32 is assined a radio networ" temporary identity (3</&T% and possibly in addition
1</&T% or- only for T88- 8!1=</&T% or- only for 788 and ,.*@ Mcps T88- =</&T% and 2</&T%) to be used as 32
identity on common transport channels. //1 connection is within a 3T/.& identified with the 3</&T%.
The 32 leaves the connected mode and returns to idle mode when the //1 connection is released or at //1
connection failure.
/eception of !M! cell broadcast can be done in both idle and connected mode.
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' "$ Release 1$
$%%e. $ (i%3or6ati5e)+
)ha%2e hitor9
9han-e histor4
8ate TSG = TSG 8oc# 9R Re2 Su3ject;9o//ent >ld New
0-01999 RP-03 RP-99259 - $##ro5ed at TSG-R$( ?3 a%d #"aced u%der )ha%2e )o%tro" - 3.0.0
0601999 RP-0- RP-99331 001 $dditio% o3 )o66o% Pac7et )ha%%e" ()P)< ) 3.0.0 3.1.0
RP-0- RP-99332 002 Pro#oed 6odi3icatio% o3 M$) 3u%ctio% 3.0.0 3.1.0
RP-0- RP-99399 003 1 $dditio% o3 ci#heri%2 6ode" decri#tio% 3.0.0 3.1.0
1001999 RP-05 RP-99-60 00- Modi3icatio% o3 )-R(T8 de3i%itio% 3.1.0 3.2.0
RP-05 RP-99-60 005 $dditio% o3 i%te2rit9 #rotectio% 3u%ctio% o% RR) 3.1.0 3.2.0
RP-05 RP-99-60 006 )"ari3icatio% o% the ua2e o3 )))< 5 4))< "o2ica" cha%%e" 3.1.0 3.2.0
RP-05 RP-99-60 00/ Re6o5a" o3 @uic7 re#eat 3u%ctio% 3ro6 R!) 3.1.0 3.2.0
RP-05 RP-995/5 00= 8%troductio% o3 Pac7et 4ata )o%5er2e%ce Protoco" (P4)P) i% the
#rotoco" architecture
3.1.0 3.2.0
RP-05 RP-99-60 009 4e"etio% o3 $%%e. ; (i%3or6ati5e) 3.1.0 3.2.0
RP-05 RP-99-60 010 )orrectio% o3 )i#heri%2 #eci3icatio% (editoria" correctio%) 3.1.0 3.2.0
RP-05 RP-99-60 011 2 ;roadcat0Mu"ticat 3u%ctio% 3.1.0 3.2.0
RP-05 RP-99-60 012 4ecri#tio% o3 Ti6i%2 $d5a%ce 6echa%i6 3or T44 3.1.0 3.2.0
RP-05 RP-99-60 013 M$) #ri6iti5e additio% a%d 6odi3icatio% (har6o%iAatio% o3 T44
1ith '44)
3.1.0 3.2.0
RP-05 RP-99-60 01- 86#act o3 t1o ci#her 7e9 o"utio% o% 6u"ti#"e.i%2 at R!) a%d M$)
"e5e"
3.1.0 3.2.0
RP-05 RP-99-60 015 1 Su##ort o3 4i33ere%t $cce Ser5ice )"ae (c"ari3icatio% o3 #ree%t
te.t)
3.1.0 3.2.0
RP-05 RP-99-60 016 1 Su##ort o3 US)<04S)< i2%a""i%2 (i%troductio% o3 S<))<, ee TS
25.321)
3.1.0 3.2.0
RP-05 RP-99-60 01/ 4))< 6a##ed to 4)< i% R!) tra%#are%t 6ode 3.1.0 3.2.0
RP-05 RP-995/6 01= 2 Ma##i%2 o3 ;))< "o2ica" cha%%e" o%to '$)< tra%#ort cha%%e" 3.1.0 3.2.0
RP-05 RP-99-60 019 1 M$) P4U 3or6at 3or P))< 3.1.0 3.2.0
RP-05 RP-99-60 020 *ditoria" cha%2e re2ardi%2 hared cha%%e" 3or T44 3.1.0 3.2.0
RP-05 RP-99-60 021 Su##ort o3 U#"i%7 S9%chro%iAatio% 'eature i% U! cha%%e" (T44
o%"9)
3.1.0 3.2.0
RP-05 RP-99-60 022 RR) 3u%ctio% 3.1.0 3.2.0
RP-05 RP-99-60 023 Modi3icatio% o3 ter6i%atio% #oi%t 3or ;)< 3.1.0 3.2.0
RP-05 RP-99-60 02- U#dated decri#tio% o3 U* 6ode 3.1.0 3.2.0
RP-05 RP-99-60 025 *%ha%ced #rotoco" architecture 3.1.0 3.2.0
1201999 RP-06 RP-99621 026 1 Su##ort o3 hared cha%%e" o#eratio% i% T44 3.2.0 3.3.0
RP-06 RP-99620 02/ $"i2%6e%t to M$)-c0h 6er2e 3.2.0 3.3.0
RP-06 RP-99621 02= Radio 8%ter3ace 'u%ctio% 3or )e"" ;roadcat 3.2.0 3.3.0
RP-06 RP-99620 030 1 *ditoria" iue 3.2.0 3.3.0
RP-06 RP-99621 031 1 4e3i%itio% o3 ci#heri%2 u%it 3.2.0 3.3.0
0302000 RP-0/ RP-00003- 032 )orrectio% o3 the )'( "e%2th 3.3.0 3.-.0
RP-0/ RP-00003- 03- Re6o5a" o3 S)< 3.3.0 3.-.0
0602000 RP-0= RP-00021- 036 2 )i#heri%2 re"ated correctio% 3.-.0 3.5.0
RP-0= RP-00021- 03/ )"ari3icatio% o3 ci#heri%2 #ara6eter 3.-.0 3.5.0
RP-0= RP-00021- 03= 1 Si2%a""i%2 radio &earer 3.-.0 3.5.0
RP-0= RP-00021- 0-0 Re#"ace6e%t o3 du#"icated i%3or6atio% o% ci#heri%2 decri#tio% &9
re3ere%ce
3.-.0 3.5.0
0902000 RP-09 RP-000352 0-1 R!) 6ode 3or S<))< 3.5.0 3.6.0
0302001 RP-11 RP-010019 0-3 1 )orrectio% 3or R$)<0)P)< 3.6.0 3./.0
RP-11 RP-010019 0-- 2 )orrectio% to Si2%a""i%2 Radio ;earer 3.6.0 3./.0
RP-11 RP-010019 0-5 1 *ditoria" u#date 3or Re"eaeB99 3.6.0 3./.0
RP-11 RP-010019 0-6 Re6o5a" o3 '$US)< 3.6.0 3./.0
RP-11 RP-010019 0-/ 1 Re6o5a" o3 :4M$ cha%%e" 3.6.0 3./.0
RP-11 RP-010019 0-= 1 U* Mode" )ha%%e" %u6&eri%2 3.6.0 3./.0
RP-11 RP-010019 0-9 Re%a6i%2 o3 49%a6ic Tra%#ort )ha%%e" T9#e S1itchi%2 3.6.0 3./.0
RP-11 RP-010019 050 Re6o5a" o3 #a9"oad u%it co%ce#t 3.6.0 3./.0
RP-11 RP-01003/ 0-2 1.2=Mc# T44 3./.0 -.0.0
0602001 RP-12 RP-010302 05- )"ari3icatio% i% the er5ice #ro5ided to u##er "a9er &9 R!) -.0.0 -.1.0
RP-12 RP-010302 056 )"ea%u# o3 !a9er 2 er5ice a%d 3u%ctio% -.0.0 -.1.0
0902001 RP-1- RP-010/53 059 )"ea% u# o3 R!) 3u%ctio% -.1.0 -.2.0
RP-1- RP-010/53 061 )orrectio% o% tra%#ort cha%%e" %u6&eri%2 -.1.0 -.2.0
0302002 RP-15 RP-02009- 062 1 8%troductio% o3 <S4P$ -.2.0 5.0.0
0602002 RP-16 RP-020321 065 8%troductio% o3 4S)<-R(T8 5.0.0 5.1.0
RP-16 RP-0203-1 066 <S4P$ #eci3ic correctio% 5.0.0 5.1.0
0902002 RP-1/ RP-0206/1 069 1 )"ari3icatio% o% R!) co%%ectio% 5.1.0 5.2.0
1202003 RP-22 - - U#2rade to Re"eae 6 - %o tech%ica" cha%2e 5.2.0 6.0.0
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' "1 Release 1$
120200- RP-26 RP-0-0-=- 0/1 8%troductio% o3 *%ha%ced U#"i%7 6.0.0 6.1.0
0302005 RP-2/ RP-050111 0/2 U%co6#"ete "o2ica" cha%%e" ide%ti3icatio% 3or '$)< 6.1.0 6.2.0
RP-2/ RP-05006/ 0/- !o"e 4! R!) P4U iAe cha%2e 6.1.0 6.2.0
RP-2/ RP-0500/5 0/5 8%troductio% o3 M;MS 6.1.0 6.2.0
0602005 RP-2= RP-05030= 00// 'eature )"ea%-u#+ Re6o5a" o3 4S)< ('44) 6.2.0 6.3.0
RP-2= RP-050309 00/9 'eature )"ea%-u#+ Re6o5a" o3 )P)< 6.2.0 6.3.0
0902005 RP-29 RP-050-59 00=1 )orrectio% the 6a##i%2 o3 P))< to '$)< 6.3.0 6.-.0
0302006 RP-31 RP-06009= 00=2 /.6= M#c T44 :#tio% (Re"eae /) 6.-.0 /.0.0
030200/ RP-35 RP-0/016- 00=3 !2 e%ha%ce6e%t+ Sta2e 2 /.0.0 /.1.0
060200/ RP-36 RP-0/0-03 00=- 1 8%troductio% o3 *%ha%ced )*!!C'$)< tate i% '44 /.1.0 /.2.0
RP-36 RP-0/0-0- 00=5 )orrectio% to the 8%troductio% o3 86#ro5ed !2 u##ort 3or hi2h data
rate
/.1.0 /.2.0
090200/ RP-3/ RP-0/0623 00=/ - )"ari3icatio% o% *-4)< a%d <S-4S)< !o2ica" )ha%%e" 8de%titie /.2.0 /.3.0
RP-3/ RP-0/0626 0090 )orrectio% to the i%troductio% o3 86#ro5ed !2 u##ort 3or hi2h data
rate
/.2.0 /.3.0
120200/ RP-3= RP-0/0909 0091 8%troductio% o3 )S 5oice o5er <SP$ /.3.0 =.0.0
RP-3= RP-0/090= 0092 8%troductio% o3 the 86#ro5ed !2 i% the u#"i%7 /.3.0 =.0.0
030200= RP-39 RP-0=01/6 0095 )orrectio% o3 3i2ure =.0.0 =.1.0
RP-39 RP-0=0202 0096 )orrectio% o3 3i2ure a%d additio% o3 6ii%2 re3ere%ce to M$)-i0i =.0.0 =.1.0
050200= RP--0 RP-0=0-15 009/ 8%troductio% o3 U#"i%7 *%ha%ced )*!!C'$)< i% 25.301 =.1.0 =.2.0
090200= RP--1 RP-0=06=/ 009= )"ari3icatio% o3 the )S )ou%ter ha%d"i%2 =.2.0 =.3.0
120200= RP--2 RP-0=1025 0099 - 8%troductio% o3 e%ha%ced )*!!C'$)<, )*!!CP)< a%d UR$CP)<
3or 1.2=Mc# T44
=.3.0 =.-.0
RP--2 RP-0=1023 0100 - 8%troductio% o3 M;MS 86#ro5ed So"utio% =.3.0 =.-.0
0302009 RP--3 RP-090265 0101 - )orrectio% o% M;MS 86#ro5ed So"utio% =.-.0 =.5.0
1202009 RP--6 - - - U#2rade to the Re"eae 9 - %o tech%ica" cha%2e =.5.0 9.0.0
0302010 RP--/ RP-1002== 0103 - )orrectio% o3 Protoco" ter6i%atio% #oi%t 3or *-4)< 3or )))<(R9) 9.0.0 9.1.0
0602010 RP--= RP-100533 0109 1 8%co%ite%c9 i% Btra%#ara%c9B de3i%itio% i% 25.301 -Re"-9 9.1.0 9.2.0
0302011 RP-51 - - - U#2raded to R*!-10 - %o tech%ica" cha%2e 9.2.0 10.0.0
0902012 RP-5/ - - - U#2raded to R*!-11 - %o tech%ica" cha%2e 10.0.0 11.0.0
3GPP
3GPP TS !"#3$1 %11#$#$ (!$1!&$' "! Release 1$