Sunteți pe pagina 1din 144

3GPP TS 24.007 V9.0.

0 (2009-12)
Technical Specification
3rd Generation Partnership Project;
Technical Specification Group Core Network and Terminals;
Mobile radio interface signalling laer 3;
General aspects
!"elease #$

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
GSM, UMTS, layer 3, network, LT
3GPP
Postal address
3GPP support office address
!"0 #o$te %e& L$'(ole& - So)*(a +nt()ol(&
Val,onne - -#+./
Tel.0 133 4 92 94 42 00 -a20 133 4 93 !" 47 1!
%nternet
*tt)033www.34)).or4
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 %&'(() *#'('( !%((#+,%$ % "elease #
/ontent&
1ontents.................................................................................................................................................... 3
7oreword................................................................................................................................................... 8
9 !cope...................................................................................................................................................... :
* /eferences.............................................................................................................................................. :
3 ;efinitions and abbreviations................................................................................................................. <
3.9 ;efinitions..............................................................................................................................................................<
3.* .bbreviations.........................................................................................................................................................<
= %ntroduction............................................................................................................................................ <
=.9 General...................................................................................................................................................................<
=.* .pplicability of functional bloc"s........................................................................................................................9+
=.3 Techni>ue of description......................................................................................................................................9+
8 !tructure of layer 3 functions............................................................................................................... 93
8.9 0asic roups of functions.....................................................................................................................................93
8.* Protocol architecture............................................................................................................................................9=
: !ervices provided by sinallin layer 3 at the M! side........................................................................*=
:.9 /eistration services............................................................................................................................................*=
:.* 1all 1ontrol services............................................................................................................................................*?
:.3 1all independent !upplementary !ervices !upport.............................................................................................33
:.= !hort Messae !ervices !upport..........................................................................................................................3=
:.8 !ession Manaement !ervices for GP/!@!ervices..............................................................................................3=
:.: /eistration !ervices for GP/!@!ervices............................................................................................................=+
:.? !ervices provided to !&;1P entities by GP/! 5oical 5in" 1ontrol services..................................................=*
:.< 5ocation services at the type . 5M3 side...........................................................................................................=8
? !ervices provided by sinallin layer 3 on the &etwor" side...............................................................=:
?.9 1all control services.............................................................................................................................................=:
?.* 1all independent !upplementary !ervices !upport.............................................................................................83
?.3 !hort Messae !ervices !upport..........................................................................................................................8=
?.= !ervices provided to !&;1P and !M! entities by GP/! 5oical 5in" 1ontrol services..................................8=
?.8 !ession Manaement !ervices for GP/! and M0M!.........................................................................................8:
?.: 5ocation services at the &etwor" side.................................................................................................................8<
< !ervices assumed from sinallin layers 9 and *.................................................................................:+
<.9 Priority..................................................................................................................................................................:+
<.* 3nac"nowleded information transfer.................................................................................................................:+
<.3 .c"nowleded information transfer....................................................................................................................:+
<.= /andom access.....................................................................................................................................................:9
<.8 1hannel manaement and measurements............................................................................................................:9
, %nterlayer service interfaces on the M! side.........................................................................................:9
,.9 !ervices provided by the /adio /esource Manaement entity............................................................................:9
,.* !ervices provided by the Mobility Manaement entity.......................................................................................:8
,.3 !ervices provided by radio resource manaement entity for GP/! services......................................................:,
,.= !ervices provided by the 551 entity for GP/! services (G!M only)................................................................?9
,.8 !ervices provided by the GMM for GP/! services.............................................................................................?*
9+ %nterlayer service interfaces on the &etwor" side...............................................................................?:
9+.9 !ervices provided by the /adio /esource Manaement entity..........................................................................?:
9+.* !ervices provided by the Mobility Manaement entity.....................................................................................?,
9+.3 !ervices provided by radio resource manaement entity for GP/! services....................................................<9
9+.= !ervices provided by the 551 entity for GP/! services...................................................................................<*
9+.8 !ervices provided by the GMM for GP/! services...........................................................................................<3
9+.: !ervices provided by the /adio /esource Manaement entity for 1T! on the fi'ed part................................<8
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3 "elease #
99 53 Messaes....................................................................................................................................... <:
99.9 General...............................................................................................................................................................<:
99.* !tandard 53 messaes........................................................................................................................................<<
99.3 &on standard 53 messaes...............................................................................................................................9+*
99.= Aandlin of superfluous information...............................................................................................................9+=
0.9 The 0asic /ules.............................................................................................................................. 99=
0.9.9 1ore /ules......................................................................................................................................................99=
0.9.* !pare parts......................................................................................................................................................99:
0.9.3 Predefined sets................................................................................................................................................99?
0.9.= 5abellin Parts................................................................................................................................................99<
0.9.8 Goodies...........................................................................................................................................................99<
0.* .dvanced rules............................................................................................................................... 99<
0.*.9 /ule .*B 2'ponent notation...........................................................................................................................99<
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ & "elease #
-orewor%
This Technical !pecification (T!) has been produced by the 3
rd
Generation Partnership Project (3GPP).
The present document defines the architecture of layer 3 and its sublayers on the G!M 3m interface- i.e. the interface
between Mobile !tation and networ" within the 3GPP system.
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 followsB
Cersion '.y.(
whereB
' the first diitB
9 presented to T!G for informationD
* presented to T!G for approvalD
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 %&'(() *#'('( !%((#+,%$ - "elease #
1 S'o)e
The present document defines the principal architecture of layer 3 and its sublayers on the G!M 3m interface- i.e. the
interface between Mobile !tation (M!) and networ"D for the 1M sublayer- the description is restricted to paradimatic
e'amples- call control- supplementary services- and short messae services for non@GP/! services. %t also defines the
basic messae format and error handlin applied by the layer 3 protocols.
7or 1T! services- the present document defines the principal architecture of layer 3 on the G!M 3mE interface- i.e. the
interface between a 1T! capable Mobile !tation (1T!@M!) and a 7i'ed Part (7P).
The correspondin protocols are defined in other Technical !pecifications- see subclause =.3.=.
7or non@GP/! services the communication between sublayers and adjacent layers and the services provided by the
sublayers are distributed by use of abstract service primitives. 0ut only e'ternally observable behaviour resultin from
the description is normatively prescribed by the present document.
7or GP/! services in addition the local information transfer and stimuli sent between sublayers is informatively
included within .nne' 1 of in the present document.
This document also defines the principal architecture of the 2P! &.! layer 3 protocol and its sublayers- includin the
messae format applied by layer 3.
%n the present document M! is also used as a synonym for 32.
2 #e5eren'e&
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- subse>uent 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.
F9G G!M +9.+*(/,?)B H;iital cellular telecommunications system (Phase *I)D General description of
a G!M Public 5and Mobile &etwor" (P5M&)H.
F9aG 3GPP T/ *9.,+8B HVocabulary for 3GPP !pecificationsH.
F*G 3GPP T! *3.9+9B HGeneral 3MT! .rchitectureH.
F3G 3GPP T! ==.++9B HMobile !tation @ 0ase !tation !ystem (M! @ 0!!) interfaceD General aspects
and principlesH.
F3aG 3GPP T! *3.+:+B HGeneral Pac"et /adio !ervice (GP/!) descriptionD !tae *H.
F3bG G!M +3.8:(/,<)B H;iital cellular telecommunications system (Phase *I)D G!M 1ordless
Telephony !ystem (1T!)- Phase 9D 1T! .rchitecture ;escriptionD !tae *H.
F3cG 3GPP T! *3.*?9B H7unctional stae * description of location servicesH.
F=G 3GPP T! ==.++8B H;ata 5in" (;5) layerD General aspectsH.
F8G 3GPP T! ==.++:B HMobile !tation @ 0ase !tation !ystem (M! @ 0!!) interfaceD ;ata 5in" (;5)
layer specificationH.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ . "elease #
F8aG 3GPP T! ==.+9=B H%ndividual e>uipment type re>uirements and interwor"inD !pecial
conformance testin functionsH.
F:G 3GPP T! *=.++<B HMobile radio interface 5ayer 3 specification 1ore &etwor" Protocols@!tae 3H.
F:aG 3GPP T! *3.9+<B HMobile radio interface 5ayer 3 specification 1ore &etwor" Protocols !tae *
(structured procedures)H.
F:bG 3GPP T! ==.+9<B HMobile radio interface layer 3 specificationD /adio /esource 1ontrol ProtocolH.
F?G 3GPP T! *=.+9+B HMobile radio interface 5ayer 3D !upplementary services specificationD General
aspectsH.
F<G 3GPP T! *=.+99B HPoint@to@Point (PP) !hort Messae !ervice (!M!) support on mobile radio
interfaceH.
F<aG 3GPP T! ==.+?9B H5ocation !ervices (51!)D Mobile radio interface layer 3 51! specificationH.
F,G 3GPP T! *=.+<+B HMobile radio 5ayer 3 supplementary services specificationD 7ormats and
codinH.
F9+G 3GPP T! *=.+<9B H5ine identification supplementary servicesD !tae 3H.
F9+aG 3GPP T! ==.+:+B HGeneral Pac"et /adio !ervices (GP/!)D Mobile !tation (M!) @ 0ase !tation
!ystem (0!!) interfaceD /adio 5in" 1ontrolJMedium .ccess 1ontrol (/51JM.1) protocolH.
F9+bG 3GPP T! ==.+8:B HG!M 1ordless Telephony !ystem (1T!)- phase 9D 1T! radio interface 5ayer 3
specificationH.
F99G 3GPP T! *=.+<*B H1all 7orwardin (17) supplementary services @ !tae 3H.
F99aG 3GPP T! ==.+:=B HGeneral Pac"et /adio !ervice (GP/!)D Mobile !tation @ !ervin GP/!
!upport &ode (M!@!G!&) 5oical 5in" 1ontrol (551) layer specificationH.
F9*G 3GPP T! *=.+<3B H1all Kaitin (1K) and 1all Aold (AO5;) supplementary servicesD !tae 3H.
F9*aG 3GPP T! ==.+:8B HGeneral Pac"et /adio !ervice (GP/!)D Mobile !tation (M!) @ !ervin GP/!
!upport &ode (!G!&)D !ubnetwor" ;ependent 1onverence Protocol (!&;1P)H.
F93G 3GPP T! *=.+<=B HMultiParty (MPTL) supplementary servicesD !tae 3H.
F9=G 3GPP T! *=.+<8B H1losed 3ser Group (13G) supplementary servicesD !tae 3H.
F98G 3GPP T! *=.+<:B H.dvice of 1hare (.o1) supplementary servicesD !tae 3H.
F9:G 3GPP T! *=.+<<B H1all 0arrin (10) supplementary servicesD !tae 3H.
F9?G 3GPP T! *=.+,+B H3nstructured !upplementary !ervice ;ata (3!!;) @ !tae 3H.
F9?aG 3GPP T! 3=.9+,B HTerminal loical test interfaceD !pecial conformance testin functionsH.
F9<G %T3@T /ecommendation M.*++B H%nformation technoloy @ Open !ystems %nterconnection @ 0asic
/eference ModelB The basic modelH.
F9,G 3GPP T! ==.+:<B HGroup 1all 1ontrol (G11) ProtocolH.
F*+G 3GPP T! *3.99+B H3MT! .ccess !tratum !ervices and 7unctionsH.
F*9G 3GPP T! *=.+3+B H5ocation !ervices (51!)D !upplementary service operations N !tae 3H.
F**G 3GPP T! *3.*89B H&etwor" !harinD .rchitecture and functional descriptionH.
F*3G 3GPP T! *8.=93B H3T/.& %u interface /.&.P sinallinH.
F*=G 3GPP T! 3:.339B H2volved 3niversal Terrestrial /adio .ccess (2@3T/.)D /adio /esource
1ontrol (//1) protocol specificationH.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ) "elease #
F*8G 3GPP T! *=.3+9B H&on@.ccess@!tratum (&.!) protocol for 2volved Pac"et !ystem (2P!)D
!tae 3H.
F*:G 3GPP T! 3:.8+,B H2volved 3niversal Terrestrial /adio .ccess (2@3T/.)D !pecial conformance
testin function for 3ser 2>uipment (32)H.
F*?G 3GPP T! *3.*9:B H!inle /adio Coice 1all 1ontinuity (!/C11)D !tae *H.
3 6e5(n(t(on& an% a,,re7(at(on&
3.1 6e5(n(t(on&
7or the purposes of the present document- the terms and definitions iven in 3GPP T/ *9.,+8 F9G apply.
3.2 +,,re7(at(on&
7or the purposes of the present document- the abbreviations defined in 3GPP T/ *9.,+8 F9aG and the followin applyB
GMM GP/! Mobility Manaement
M&! Mobile &etwor" !inallin
&@P;3 &etwor"@Protocol ;ata 3nit
!M !ession Manaement
3;T 3ser ;ata Transfer
1T! 1ordless Telephony !ystem
51! 5o1ation !ervices
MO1& Multi@Operator 1ore &etwor"
4 8ntro%$'t(on
4.1 General
7our models are defined for 5ayer 3- one model for non@GP/! services- one for GP/! services supportin 1lass 1
M!s only- one model for GP/!@services supportin 1lass . and 1lass 0 M!s and one model for 2P! services. (The
third model is a combination of the first two models listed). %n the present document GP/! services and 2P! services
will be used as synonyms.
The layer 3 for non@GP/! services provides the functions necessaryB
@ for /adio /esource (//) manaementD
@ for Mobility Manaement (MM)D and
@ for the 1onnection Manaement (1M) functions- i.e. functions for the control- provision- and support of services
offered by the networ"D amon which there are- e..B
@ the functions to establish- maintain and terminate circuit@switched connections across a G!M P5M& and
other networ"s to which the G!M P5M& is connectedD
@ supportin functions for supplementary services controlD
@ supportin functions for short messaes service controlD
@ supportin functions for location services control (only for a type . 5M3).
The layer 3 for non@GP/! services is composed of three sublayers comprisinB
@ the /adio /esource Manaement (//) functionsD
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ / "elease #
@ the Mobility Manaement (MM) functionsD and
@ the 1onnection Manaement (1M) functions.
Khen 1T! services are added to non@GP/! services- the followin functions are addedB
@ 1T! /adio /esource Manaement (1T!@//) functions to //D and
@ 1T! Mobility Manaement (1T!@MM) functions to MM.
The layer 3 for GP/! services is composed of four sublayers comprisinB
@ the /adio /esource Manaement (//) functionsD
@ the Mobility Manaement (GMM)D
@ for the 5oical 5in" 1ontrol (551)D
@ the 1onnection Manaement (1M) functions.
The 1onnection Manaement (1M) sublayer is composed of functional bloc"s forB
@ 1all 1ontrol (11) for non@GP/! servicesD
@ !hort Messae !ervice !upport (!M!) for non@GP/! servicesD
@ GP/! !hort Messae !ervice !upport (G!M!) (for GP/! services supportin 1lass .- 0 and 1 M!s)D
@ !ession Manaement (!M) (for GP/! services supportin 1lass .- 0 and 1 M!s)D
@ !upplementary !ervices !upport (!!) for non@GP/! servicesD
@ Group 1all 1ontrol for non@GP/! servicesD
@ 0roadcast 1all 1ontrol (011) for non@GP/! servicesD
@ 1onnection Manaement of Pac"et ;ata on !inallin channels for non@GP/! services;
@ 5ocation !ervices support (51!) for non@GP/! services (only for a type . 5M3).
Kithin the conte't of 51!- for G!M 51!- the services defined for an M! are e>ually applicable to a type . 5M3-
unless otherwise stated. Aowever- services defined specifically for a type . 5M3 are not applicable to an M!. The
followin is a list of services essential for a type . 5M3.
The layer 3 for non@GP/! services provides the functions necessaryB
@ for /adio /esource (//) manaementD
@ for Mobility Manaement (MM)D and
@ supportin functions for location service control.
The layer 3 for non@GP/! services is composed of three sublayers comprisinB
@ the /adio /esource Manaement (//) functionsD
@ the Mobility Manaement (MM) functionsD and
@ the 1onnection Manaement (1M) functions.
The 1onnection Manaement (1M) sublayer is composed of a functional bloc" forB
@ location services support (51!) for non@GP/! services.
The present document does not consider the distribution of sinallin functions amon the different networ"
e>uipments. The sinallin functions are described between two systems which represent the M! side and the networ"
side of the radio interface of layer 3. Only the functions in the networ" for sinallin communication with one M! is
considered.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ # "elease #
7or GP/! services- in addition to the sinallin functions also the user data transfer is included in the present
document.
The layer 3 for 2P! services is composed of four sublayers comprisinB
@ the 2P! /adio /esource Manaement (//) functionsD
@ the 2P! Mobility Manaement (2MM) functionsD and
@ the 1onnection Manaement (1M) functions.
The 1onnection Manaement (1M) sublayer is composed of a functional bloc" forB
@ the 2P! !ession Manaement (2!M) functions.
4.2 +))l('a,(l(ty o5 5$n't(onal ,lo'k&
&ot for all functional bloc"s listed in subclause =.9- support in the M! or in the networ" is mandatoryB
@ !upport of Group 1all 1ontrol is optional in the M! and in the networ".
@ !upport of 0roadcast 1all 1ontrol is optional in the M! and in the networ".
@ 1onnection Manaement of Pac"et ;ata on !inallin channels. is optional in the M! and in the networ".
@ !upport of GP/! services is optional in the M! and in the networ".
@ !upport of 1T! services is optional in the M!. 1T! services are not applicable to the networ".
@ !upport of 51! services is optional in the M! and in the networ"- but not optional in 5M3.
7urther conditions and constraints are defined in other Technical !pecifications.
4.3 Te'*n(9$e o5 %e&'r()t(on
5ayer 3 and its sub@layers are specified byB
@ their service specification- see subclause =.3.9D
@ their protocol specification- see subclause =.3.3D
@ the specification of functions- see clause 8.
4.3.1 Ser7('e %e&'r()t(on
The services of sinallin layer 3 and its sublayers are described in terms ofB
@ services provided to upper (sub@)layers at the service access pointsD
@ services assumed from lower (sub@)layers at the service access points.
5ayer 3 and its supportin lower layers provide the Mobile &etwor" !inallin (M&!) !ervice and 3ser ;ata Transfer
(3;T) !ervice (for GP/! services only) to the upper layers.
The service providedJassumed at the service access points are described by means of abstract service primitives and
parameters as recommended in %T3@T /ecommendation M.*++ F9<G.
4.3.2 +,&tra't &er7('e )r(:(t(7e&
The abstract service primitives consist of re>uests- responses- indications and confirmations. The eneral synta' of a
primitive is specified in 3GPP T/ *9.,+8 F9aG.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,( "elease #
4.3.3 Proto'ol& an% )eer-to-)eer 'o::$n('at(on
0y use of the services provided by lower (sub@)layers- peer entities in a (sub@)layer in the M! and the networ" e'chane
information. 2'chane of information between two peer entities is performed accordin to the
correspondin (sub@)layer protocols. . protocol is a set of rules and formats by which the information (control
information and user data) is e'chaned between the two peers. The information is e'chaned by use of messaes
which are defined in the protocol. (Therefore- the messaes are also called Protocol ;ata 3nits- P;3s).
There are several protocols of the // sublayer- one protocol of the 551 sublayer- three protocols of the MM sublayer-
and several protocols of the 1M sublayer. 7or each functional bloc" of the 1M sublayer as defined in subclause =.9
there is one protocol. The 1M protocols are specified in the Technical !pecifications identified in subclause =.3.=.
%n the model used in the present document- there areB
9) for non@GP/! servicesB
@ one // sub@layer entity in the M! and one // sub@layer entity in the networ"D
@ one MM sub@layer entity in the M! and one MM sub@layer entity in the networ"D
@ for each functional bloc" of the 1M sublayer as defined in subclause =.9 which is supported in the M! (in the
networ")- there are- dependin on the protocol- one or more entities in the M! (in the networ"). Two
different entities of the same functional bloc" in the M! (in the networ") are called parallel entities. The
entities of the same functional bloc" in the M! correspond in a one@to@one relation to the entities of the
functional bloc" in the networ". The correspondin entities are called peer entitiesD
*) for 1T! services (in addition to non@GP/! services)B
@ one // sub@layer entity in the M! and one in the 1T! fi'ed part. These // sub@layers include one 1T!@//
sub@entity on each sideD
@ one MM sub@layer entity in the M! and one in the 1T! fi'ed part These MM sub@layers include one 1T!@
MM sub@entity on each sideD
@ for each functional bloc" of the 1M sublayer as defined in subclause =.9 which is supported in the M! (in the
fi'ed part)- there are- dependin on the protocol- one or more entities in the M! (in the fi'ed part). Two
different entities of the same functional bloc" in the M! (in the fi'ed part) are called parallel entities. The
entities of the same functional bloc" in the M! correspond in a one@to@one relation to the entities of the
functional bloc" in the fi'ed part. The correspondin entities are called peer entitiesD
3) for GP/! services supportin 1lass 1 M!sB
@ one // sublayer entity (//) in the M! and one // sublayer entity in the networ"D
@ si' 551 sublayer entities (Oo!9@Oo!=- sinallin- !M!) in the M! and si' 551 sublayer entities in the
networ"D
@ one MM sublayer entity (GMM) in the M! and one MM sublayer entity in the networ" (GMM)D
@ one !M entity in the M!#s 1M sublayer and one !M sublayer entity in the networ"#s 1M sublayerD
@ one or more G!M! functional bloc"s in the 1M sublayer if supportedD
=) for non@GP/! and GP/! services supportin 1lass . and 1lass 0 M!sB
@ two // sublayer entities (//) in the M! and two // sublayer entities in the networ"D
@ si' 551 sublayer entities (Oo!9@Oo!=- sinallin- !M!) in the M! and si' 551 sublayer entities in the
networ"D
@ two MM sublayer entities (GMM I MM) in the M! and one or two MM sublayer entities in the networ"
(GMM or MM)D
@ one !M entity in the M!#s 1M sublayer and one !M entity in the networ"#s 1M sublayerD
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,, "elease #
@ for each functional bloc" of the 1M sublayer as defined in subclause =.9 which is supported in the M! (in the
networ")- there are- dependin on the protocol- one or more entities in the M! (in the networ"). Two
different entities of the same functional bloc" in the M! (in the networ") are called parallel entities. The
entities of the same functional bloc" in the M! correspond in a one@to@one relation to the entities of the
functional bloc" in the networ". The correspondin entities are called peer entitiesD
8) for 2P! servicesB
@ one // entity in the M! and one // entity in the networ"D
@ one 2MM entity in the M! and one 2MM entity in the networ"D
@ for each functional bloc" of the 1M sublayer as defined in subclause =.9 which is supported in the M! (in the
networ")- there are- dependin on the protocol- one or more entities in the M! (in the networ"). Two
different entities of the same functional bloc" in the M! (in the networ") are called parallel entities. The
entities of the same functional bloc" in the M! correspond in a one@to@one relation to the entities of the
functional bloc" in the networ". The correspondin entities are called peer entities.
.s each sub@layer entity is specified by one and only one protocol- it is also called a protocol entity or protocol control
entity.
7or GP/!@services supportin 1lass . and 1lass 0 M!s- the MM entities of the MM@sublayer are able to e'chane
information by means of GMM P;3s as well as MM P;3#s. This means if a mobile is GP/! attached- non@GP/!
mobility manaement procedures may ma"e use of G/P! mobility manaement messaes.
Khen two peer protocol entities e'chane P;3s- a transaction is said to be established (orB to be activeD orB to e'ist). %t
depends from the protocol when e'actly a protocol entity considers the transaction to be active- normally this is the
caseB
@ from the moment when it has passed the first suitable messae to lower (sub@) layers or received the first suitable
messae from its peer entityD
@ up to the moment when it has released the transaction.
4.3.4 /ontent& o5 layer 3 relate% Te'*n('al S)e'(5('at(on&
@ The /adio /esource (//) manaement protocol is defined in 3GPP T! ==.+9< F:bGD
@ the Mobility Manaement (MM) protocol is defined in 3GPP T! *=.++< F:GD
@ the !ession Manaement (!M) protocol is defined in 3GPP T! *=.++< F:GD
@ the 1all 1ontrol (11) protocol is defined in 3GPP T! *=.++< F:GD
@ the !upplementary !ervices (!!) protocol is defined in 3GPP T! *=.+9+ F?G- 3GPP T! *=.+<'- 3GPP T! *=.+,'-
and 3GPP T! *=.+3+ F*9GD
@ the !hort Messae !ervice (!M!) protocol is defined in 3GPP T! *=.+99 F<GD
@ the Group 1all 1ontrol (G11) protocol is defined in 3GPP T! ==.+:< F9,GD
@ the 5oical 5in" 1ontrol (551) protocol is defined in 3GPP T! ==.+:= F99aGD
@ the GP/! /adio /esource (G//) protocol is defined in 3GPP T! ==.+:+ F9+aG and 3GPP T! *=.++< F:GD
@ the 1T! /adio /esource (1T!@//) sub@protocol is defined in 3GPP T! ==.+8: F9+bGD
@ the 1T! Mobility Manaement (1T!@MM) sub@protocol is defined in 3GPP T! ==.+8: F9+bGD
@ the 1T! additions to the 1all 1ontrol (11) protocol are defined in 3GPP T! ==.+8: F9+bGD
@ the 5ocation !ervices (51!) protocol for a type . 5M3 is defined in 3GPP T! *3.*?9 F3cG and
3GPP T! ==.+?9 F<aGD
@ the 2P! /adio /esource (//) manaement protocol is defined in 3GPP T! 3:.339 F*=GD
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,% "elease #
@ the 2P! Mobility Manaement (2MM) protocol is defined in 3GPP T! *=.3+9 F*8GD
@ the 2P! !ession Manaement (2!M) protocol is defined in 3GPP T! *=.3+9 F*8G.
" Str$'t$re o5 layer 3 5$n't(on&
".1 ;a&(' 4ro$)& o5 5$n't(on&
Most functions of layer 3 and its sub@layers are described by the service specifications and protocol specifications of
the (sub@)layers.
These functions are in the model reali(ed by protocol control entities- see subclause =.3.3.
%n addition- routin functions are contained in layer 3 which are related to the transport of messaes- e.. multiple'in
and splittin. These routin functions are defined in the /adio /esource Manaement and Mobility Manaement
sub@layers.
9) They have the tas" to pass the messaes from upper (sub@)layers to lower (sub@)layers.
*) They also have the tas" to pass messaes provided by lower (sub@layers) to the appropriate sub@layer and- if
applicable- entity.
The routin functions with tas" * ma"e use of the protocol discriminator (P;) which is part of the messae header.
. 1M sublayer protocol may also define a transaction identifier (T%)- procedure transaction identity (PT%) or 2P! bearer
identity as a part of the messae header. This is at least the case if there are parallel entities of the same functional
bloc"- see subclause =.3.3. %f they are a part of a messae- the T%- PT%- 2P! bearer identity- or both PT% and 2P! bearer
identity are also used by the routin functions.
@ The MM@sublayer routin function passes the messaes of the 1M entities as well as of the MM- GMM and
1T!@MM entities of its own sublayer to the service access point of //- G//- 551 or 1T!@//. 7urthermore it
multiple'es them in case of parallel transactions.
@ The routin function of /adio /esource Manaement distributes the messaes to be sent accordin to their
messae type and protocol discriminator (P;)- to the actual channel confiuration- and- if applicable- to further
information received from upper sub@layers to the appropriate service access point of layer * (identified by !.P%
and loical channel). Pain messaes received from the PP1A are always routed to GMM- while pain
messaes received from the P1A are distributed to GMM or MM based on the temporary identifier (TM!% or
T55). 7or 2P! services- the Pain messaes received from the P1A are always routed to 2MM.
@ The messaes provided at the different service access points of layer * are distributed by the // sublayer routin
function accordin to their protocol discriminator (P;). Messaes with a P; e>ual to // are passed to the //
entity of the own sublayer- all other messaes are passed to the MM sublayer at the service access point //@
!.P.
@ The routin function of MM@sublayer passes !tandard 53 messaes accordin to the protocol discriminator (P;)
and- if applicable- the transaction identifier (T%) or the P;P address towards the MM entity or towards the 1M
entities via the various MM@!.P#s. GP/! 53 messaes are routed to mobility manaement or session
manaement accordin to the protocol discriminator.
@ 7or 2P! services- the routin function of 2P! &.! passes standard 53 messaes accordin to the protocol
discriminator (P;) and- if applicable- the procedure transaction identity (PT%) andJor 2P! bearer identity towards
the 2MM entity or towards the 1M (2!M) entities of the various 2P! &.! !.P#s.
@ The routin function of 551 passes the messaes accordin to the !.P%s to the MM sublayer or to the !&;1P
entities.
The messae (messae header or other parts of the messae) are neither chaned nor removed by the // routin
function or MM routin function before passin it to the appropriate service access point.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,3 "elease #
".2 Proto'ol ar'*(te't$re
The protocol architecture is visuali(ed for each of the three modelsB
@ 7iure 8.9J3GPP T! *=.++? shows the protocol architecture for a M! not supportin the GP/! service-
restrictin the representation of 1M sublayer protocols to three paradimatic e'amples- 11- !!- and !M!. The
51! protocol entity of a type . 5M3 would be included in the same manner. &ote that the protocol stac" for a
class 1 GP/! service may be present in the M!- but it is not active simultaneously.
@ 7iure 8.* shows the protocol architecture for a M! supportin the 1lass 1 GP/! service. (&ote that the
protocol stac" for a circuit switched services may be present in the M!- but it is not active simultaneously).
@ 7iure 8.3 shows the protocol architecture for non@GP/! and GP/!@services supportin 1lass . and 1lass 0
M!s.
@ 7iure 8.= shows the protocol architecture for a M! supportin 1T! services in addition to non@GP/! services.
@ 7iure 8.8 shows the protocol architecture for a M! supportin the P! mode of operation 3MT! service.
@ 7iure 8.: shows the protocol architecture for 3MT! services supportin 1!JP! mode of operation M!s.
@ 7iure 8.? shows the protocol architecture for a M! supportin 2P! services.
@ 7iure 8.< shows the protocol architecture for an M! supportin 2P! services and 1! fallbac".
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,& "elease #
.<T0 T*e L/S )roto'ol ent(ty 5or a ty)e + LMU wo$l% ,e (n'l$%e% (n t*e 5(4$re (n t*e &a:e :anner a& t*e
)roto'ol ent(t(e& 5or //, SS an% SMS.
0igure -',1 Protocol 2rchitecture not supporting GP"S ser3ice + MS side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,- "elease #

P;P
551@sublayer
//@sublayer
MM@sublayer
G//@!.P
P
/
.
1
A
P
P
1
A
P
.
G
1
A
P
0
1
1
A
P
;
T
1
A
P
.
1
1
A
!.P%
Oo!9@!.P Oo!*@!.P Oo!3@!.P Oo!=@!.P
G!M!
M&!M!@!.P
G//
(shared mode //)
55!M!@!.P
551 manaement
entity
55GMM@!.P
GMM!M@!.P
GMM//@
!.P
!2!!%O&
M.&.G2M2&T
/
.
1
A
P
1
A
.
G
1
A
0
1
1
A
P
&
1
A
T%
GMM/2G@!.P
1M
P; J T55%
GMM
!&!M@!.P
!M/2G@!.P
!&@!.P
services (!&;1P)
3ser payload
!!
M&!!@!.P
T%
GMM!!@!.P
0igure -'%1 Protocol architecture supporting GP"S class C MSs4 MS + side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,. "elease #

GMM!M@
!.P
551
sublayer
MM@sublayer
Oo!9@=
!.PPs
3ser payload
services (!&;1P)
!&@!.P
GMM

GMM
coord
M&!M!@!.P
GMM/2G
@!.P
55GMM@
!.P
MM!M!@
!.P
MM11@!.P MM!!!.P
55!M!@!.P
M&!!@!.P M&11@!.P
GMM!M!@
!.P
T% T% P;P T%
1M
11 !!
G!M!
T%
P; J T55%
//@!.P
G//@!.P
//@sublayer
GMM//@!.P
G//
(shared mode //)
//
P
;
T
1
A
P
.
1
1
A
P
/
.
1
A
P
P
1
A
P
.
G
1
A
P
0
1
1
A
/
.
1
A
P
1
A
.
G
1
A
0
1
1
A
P
&
1
A
T
1
A
!
;
1
1
A
P;
distribution
//
(dedicated mode //)
MM
MM
coord
P;
!&!M@!.P
!M/2G@!.P
!M
%nternal structure
see fiure 8.*
%ncl.
@ 7.11A
@ !.11A
GMM!!*@
!.P
GMM!M@
!.P
T%
0igure -'353GPP TS %&'(()1 Protocol architecture supporting GP"S class 2 and 6 MSs4 MS + side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,) "elease #
/
T
S
+
#
/
=
/
T
S
+
G
/
=
/
T
S
S
+
/
/
=
/
T
S
-
+
/
/
=
S+P8 0
S+P8 3
##
MM
P6
MM
// SS SMS
MM#G-S+P
MM//-S+P
MMSS-S+P
MMSMS-S+P
// SS
SMS
M7689:
N:T;7"<
S:"*8C:
M.//-S+P M.SS-S+P M.SMS-S+P
/
T
S
;
/
=
/
T
S
P
/
=
/
T
S
S
+
/
/
=
##-S+P
##
L
+
>

#
3
S
8
G
.
+
L
L
8
.
G
?##
T8
T8 T8
P6
SP6
?/TS-## ?@ /TS-##
/TS-## ##
SP6
?/TS-MM ?@ /TS-MM
/TS-MM MM
0igure -'&53GPP TS %&'(()1 Protocol architecture supporting CTS ser3ices in addition to non+ GP"S
ser3ices4 MS + side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,/ "elease #

MM@sublayer
G!M!
M&!M!@!.P
PMM!M!@!.P
GMM!M@!.P
!2!!%O&
M.&.G2M2&T
T%
GMM/2G@
!.P
1M
P;
GMM
!M/2G@!.P
.ccess !tratum sublayer
/.0M.!@!.P
GMM.!@!.P
//1
P;1P
/.0M!M@!.P
P;1Pn@!.P
GMM/.0MQ!.P
0M1
P;1P*@!.P
P;1P9@!.P
P;P
RABM
/.09@!.P
/.0
2ntity
9

/.0
2ntity
*

/.0
2ntity
n

/.0
1ontrol
/.0n@!.P /.0*@!.P
!!
M&!M!@!.P
GMM!!@!.P
T%
0igure -'-53GPP TS %&'(()1 Protocol architecture of Non 2ccess Stratum supporting PS mode of
operation MSs4 MS+side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,# "elease #

GMM!M@
!.P
MM@sublayer
GMM

GMM
coord
M&!M!@!.P
GMM/2G
@!.P
MM!M!@
!.P
MM11@!.P MM!!!.P
PMM!M!
@!.P
M&!!@!.P M&11@!.P
GMM!M!@
!.P
T% T% P;P T%
1M
11 !! G!M!
T%
P;
MM
MM
coord
P;
!M/2G@!.P
/
.
0
M
!
M
@
!
.
P

RABM
/.09@!.P
/.0
2ntity
9

/.0
2ntity
*

/.0
2ntity
n

/.0
1ontrol
/.0n@!.P /.0*@!.P
!M
G
M
M
/
.
0
M
@
!
.
P

.ccess !tratum sublayer
/.0M.!@!.P GMM.!@!.P
//1
P;1P
P;1Pn@!.P
0M1
P;1P*@!.P
P;1P9@!.P //@!.P
GMM!!!.P
T%
GMM!!*!.P
0igure -'.5%&'(()1 Protocol architecture of Non 2ccess Stratum supporting CS5PS mode of operation
MSs4 MS = side
&OT2B !M! un@related parts of this fiure- e.. !&;1P should be modified for 3MT!.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %( "elease #
2MM2!M@!.P
1M
//1 P;1P
2@3T/.& .ccess !tratum sublayer
2MM.!@!.P
/0 9
0earer
1ontrol
/0 *
/0 n
P;1P9@!.P
2MM
P;1P*@!.P P;1P3@!.P
/09@!.P /0*@!.P /0n@!.P
/0M.!@!.P
2!M
2MM/2G@!.P
2!M/2G@!.P
P;
MM !ublayer
20%
0igure -')53GPP TS %&'(()1 Protocol architecture of Non 2ccess Stratum supporting PS mode of
operation MSs4 MS+side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %, "elease #
20%
2MM2!M@!.P
1M
MM@sublayer
//1
P;1P
2@3T/.& .ccess !tratum sublayer
2MM.!@!.P
G!M!
2!M!
2MM!M!@!.P
T%
/0 9
0earer
1ontrol
/0 *
/0 n
P;1P9@!.P
2MM
2MM
1oord
MM
MM
1oord
P;1P*@!.P P;1Pn@!.P
/09@!.P /0*@!.P /0n@!.P
/0M.!@!.P
2!M
2MM/2G@!.P
2!M/2G@!.P M&!M!@!.P
G!M!
11
M&11@!.P
G!M!
!!
M&!!@!.P
P;
T%
//@!.P
MM11@!.P
T%
MM!!@!.P
G2/.&J3T/.&
.ccess !tratum sublayer
P;
0igure -'/53GPP TS %&'(()1 Protocol architecture of Non 2ccess Stratum supporting CS5PS mode ,
or CS5PS mode % of operation MSs4 MS+side
.s shown in fiure 8.9 a hierarchy of 3 sublayers is definedB
@ the // sublayer provides services to the MM sublayer and utili(es the services of sinallin layer *D
@ the MM sublayer provides common services to the entities of the 1onnection Manaement (1M) sublayerD
@ the 1M sublayer includes- amon others- the 11- !!- and !M! entities- which are independent entities.
7iure 8.* defines four sublayers for GP/! services supportin 1lass 1 M!sB
@ the // sublayer provides services to the MM and 551 sublayersD
@ the 551 sublayer provides services to the MM sublayer- the !&;1P and G!M! entities and uses services of the
// sublayerD
@ the MM sublayer provides services to the !M and !! entities of the 1M. The MM sublayer includes one GMMD
@ the 1M sublayer includes the !M- !! and G!M! entities. The !M entity provides services to the !&;1P entity
and uses services of the MM sublayer. The G!M! entity is identical to the !M! entity for non@GP/! services
e'cept it uses the services from the 551 sublayer. The !! entity is identical to the one for non@GP/! services
e'cept it uses the services from the 551 or P! sinallin connection.
7iure 8.3 defines four sublayers for non@GP/! and GP/!@services supportin 1lass . and 1lass 0 M!sB
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %% "elease #
@ the // sublayer provides services to the MM and 551 sublayersD
@ the 551 sublayer provides services to the MM sublayer- the !&;1P and G!M! entities and uses services of the
// sublayerD
@ the MM sublayer provides services to the !&;1P entity and to the entities of the 1onnection Manaement (1M)
sublayer. %n addition to the MM entity for non@GP/! services- the MM sublayer further includes one GMM
entityD
@ the 1M sublayer includes- amon others- the 11- !!- G!M! and !M entities- which are independent entitiesD
@ the !M entity provides services to the !&;1P entity and uses services of the MM sublayer.
The G!M! entity is an e'tension of the !M! entity for non@GP/! services. 7or messae transfer it uses the
services both from the 551 sublayer and the MM entity of the MM sublayer. 7urthermore it retrieves from the
MM entity information about which transport service to use.
7iure 8.= defines three sub@layers for 1T! servicesB
@ the // sublayer provides services (includin 1T! services) to the MM sublayer and uses the services of
sinallin layer *D
@ the MM sublayer provides common services to the entities of the 1onnection Manaement (1M) sublayerD it
provides also specific 1T! services to the entities above 1MD
@ the 1M sublayer includes- amon others- the 11- !!- and !M! entities- which are independent entities.
7iure 8.8 defines three sublayers for 3MT! P! domain services supportin P! mode of operationB
@ the .ccess !tratum (.!) sublayer provides services to the MM sublayer and the /.0 Manaer (/.0M) entity.
- the MM sublayer provides services to the !M- !! and G!M! entities of the 1M. The MM sublayer includes
one GMM entityD
@ the 1M sublayer includes the !M- !! and G!M! entities. The !M entity provides services to the /.0M entity
and uses services of the MM sublayer. The G!M! entity is identical to the !M! entity for GP/! services in
G!M e'cept it uses the services from the GMM sublayer. The !! entity is identical to the one for non@GP/!
services e'cept it uses the services from the 551 or P! sinallin connectionD
@ the /.0M hides the concepts of /.0s that can be activatedJreleased while a P;P conte't is active. %f 35 data
in the terminal is to be sent on a /.0 (&!.P%) that has been released the /.0M will trier a service re>uest
procedure in GMM.
7iure 8.: defines three sublayers for 3MT! 1! domain services and 3MT! P! domain services supportin 1!JP!
mode of operation M!sB
@ the .ccess !tratum (.!) sublayer provides services to the MM sublayer and the /.0 Manaer (/.0M) entityD
@ the MM sublayer provides services to the entities of the 1onnection Manaement (1M) sublayer. %n addition to
the MM entity for 1! domain services- the MM sublayer further includes one GMM entityD
@ the 1M sublayer includes- amon others- the 11- !!- G!M! and !M entities- which are independent entitiesD
@ the !M entity provides services to the /.0M entity and uses services of the MM sublayer.
The G!M! entity is an e'tension of the !M! entity for 1! domain services. 7or messae transfer it uses the
services both from the GMM entity of the MM sublayer and the MM entity of the MM sublayer. 7urthermore it
retrieves from the MM entity information about which transport service to useD
@ the /.0M hides the concepts of /.0s that can be activatedJreleased while a P;P conte't is active. %f 35 data
in the terminal is to be sent on a /.0 (&!.P%) that has been released- the /.0M will trier a service re>uest
procedure in GMM.
7iure 8.? defines three sublayers for 2P! P! domain servicesB
@ the .ccess !tratum (.!) sublayer provides services to the MM sublayerD
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %3 "elease #
@ the MM sublayer provides services to the entities of the 1onnection Manaement (1M) sublayer. The MM
sublayer further includes one 2MM entityD
@ the 1M sublayer includes 2!M entitiesD
@ the 2!M entity provides services to the 0earer 1ontrol (01) entity and uses services of the MM sublayerD
@ the 01 entity hides the concepts of radio bearers that can be establishedJreleased while an 2P! bearer conte't is
active. %f uplin" data in the terminal is to be sent- and 2P! bearers have been released- the 01 will trier a
service re>uest procedure in 2MM.
7iure 8.< defines three sublayers for 2P! domain services and non@2P! domain services supportin 1!JP! mode 9 or
1!JP! mode * of operation M!sB
@ the .ccess !tratum (.!) sublayer provides services to the MM sublayerD
@ the MM sublayer provides services to the entities of the 1onnection Manaement (1M) sublayer. %n addition to
the MM entity for non@2P! services- the MM sublayer further includes one 2MM entityD
@ the 1M sublayer includes amon others- the 11- !!- 2!M! and 2!M entities- which are independent entitiesD
@ the 2!M entity provides services to the 0earer 1ontrol (01) entity and uses services of the MM sublayer.
The 2!M! entity is an e'tension of the !M! entity for non@2P! services. 7or messae transfer- it uses the
services from the 2MM entity of the MM sublayerD
@ the 01 entity hides the concepts of radio bearers that can be establishedJreleased while an 2P! bearer conte't is
active. %f uplin" data in the M! is to be sent- and all 2P! bearers have been released- the 01 will trier a
service re>uest procedure in 2MM.
! Ser7('e& )ro7(%e% ,y &(4nall(n4 layer 3 at t*e MS
&(%e
The different classes of services provided by sinallin layer 3 at the M! side are accessible at the followin service
access pointsB
@ reistration services at the MM/2G@!.P or GMM/2G@!.PD
@ 1all 1ontrol services for normal and emerency calls includin call related !upplementary !ervices !upport
services at the M&11@!.PD
@ !hort Messae !ervices !upport services at the M&!M!@!.PD
@ 1all independent !upplementary !ervices !upport services at the M&!!@!.PD
@ 5ocation !ervices !upport services at the M&51!@!.PD
@ other services correspondin to further functional bloc"s of the 1M sublayer at the appropriate service access
points. These services are not further described in this clauseD
@ !ession Manaement services at the !M/2G@!.P and at the !&!M@!.PD
@ 5oical 5in" 1ontrol services at the Oo!9@!.P- Oo!*@!.P- Oo!3@!.P and Oo!=@!.P.
!.1 #e4(&trat(on &er7('e&
The reistration services (location updatin- %M!% attachJdetach) are provided at the service access point
MM/2G@!.P. .s opposed to all other M&@!ervices- these services are provided by and can be directly accessed at the
Mobility Manaement sublayer.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %& "elease #
!.1.1 Ser7('e &tate %(a4ra: 5or MS not &$))ort(n4 GP#S &er7('e
The reistration services provided at the service access point MM/2G@!.P are illustrated in the state of fiure :.9
below.
MM#-.#G-#A
8.6
MM#-.#G-#A
8.6
MM#-#G-8.G
UP-
6+T6
.<T
UP-
6+T6
B+8T
UP-
6+T8.G
MM#-#G-/.-
MM#-
#G-#A
MM#-#G-#A
MM#-#G-#A
MM#-.#G-
#A-8.6
0igure .',1 "egistration ser3ices pro3ided at MM":G+S2P + MS side
!.1.2 Ser7('e )r(:(t(7e&
Table .',1 Primiti3es and Parameters at the MM":G+S2P + MS side
P"8M8T8*: P2"2M:T:" ":0:":NC:
MM#C#GC#A 8MS8 !.1.2.1
MM#C#GC/.- - !.1.2.2
MM#C.#GC#A - !.1.2.4
MM#C.#GC8.6 'a$&e !.1.2."
!.1.2.1 MM#C#GC#A
/eistration re>uest- triered by activation of the %M!%- e..- by activation of the M! with inserted !%M- insertion of
the !%M into the activated M!- pressin of a reset button.
!.1.2.2 MM#C#GC/.-
/eistration confirmation. %ndicates to the user that the M! is ready to start a transaction.
!.1.2.3 Vo(%
!.1.2.4 MM#C.#GC#A
/e>uest to cancel the reistration- stimulated either by removin the !%M or automatically in the power off phase.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %- "elease #
!.1.2." MM#C.#GC8.6
%ndication that reistration has been cancelled or that reistration was not possible. Only emerency services are
available to the user.
!.1.3 #e4(&trat(on Ser7('e& 5or /TS-Ser7('e&
The reistration services (attachJdetach- enrolmentJde@enrolment) are provided for 1T! services at the service access
point MM/2G@!.P.
Table .','31 Primiti3es and Parameters at the MM":G+S2P + MS side for CTS
P"8M8T8*: P2"2M:T:" ":0:":NC:
MM#C/TSC+TT+/=C#A 8MS8 !.1.3.1
MM#C/TSC+TT+/=C/.- - !.1.3.2
MM#C/TSC+TT+/=C#D 8-PS8, 'a$&e !.1.3.3
MM#C/TSC6T+/=C8.6 - !.1.3.4
MM#C/TSC.#<LLC#A 8MS8 !.1.3."
MM#C/TSC.#<LLC/.- - !.1.3.!
MM#C/TSC.#<LLC#D 8-PS8, 'a$&e !.1.3.7
MM#C/TSC
6C.#<LLC8.6
- !.1.3.E
!.1.3.1 MM#C/TS C+TT+/=C#A
M! initiates the 1T! attach. 1T!@MM is re>uested to send a 1T! .TT.1A /2O32!T messae to the fi'ed part.
!.1.3.2 MM#C/TS C+TT+/=C/.-
The 1T! attach was successful. The fi'ed part confirmed the attach- i.e. the 1T! .TT.1A .112PT messae was
received by the M!.
!.1.3.3 MM#C/TS C+TT+/=C#D
The 1T! attach has failed. The fi'ed part rejected the attach attempt- i.e. the 1T! .TT.1A /2R21T messae was
received by the M!.
!.1.3.4 MM#C/TS C6T+/=C8.6
M! initiates 1T! detach. 1T!@MM is re>uested to send a 1T! ;2T.1A %&;%1.T%O& messae. The detach
procedure is initiated.
!.1.3." MM#C/TS C.#<LLC#A
M! initiates the 1T! enrolment. 1T!@MM is re>uested to send a 1T! 2&/O5M2&T /2O32!T messae to the fi'ed
part.
!.1.3.! MM#C/TS C.#<LLC/.-
The 1T! enrolment was successful. The fi'ed part confirmed the enrolment- i.e. the 1T! 2&/O5M2&T .112PT
messae was received by the M!.
!.1.3.7 MM#C/TS C.#<LLC#D
The 1T! enrolment has failed. The fi'ed part rejected the enrolment attempt- i.e. the 1T! 2&/O5M2&T /2R21T
messae was received by the M!.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %. "elease #
!.1.3.E MM#C/TS C6C.#<LLC8.6
7P initiates 1T! de@enrolment. 1T!@MM is re>uested to send a 1T! ;2@2&/O5M2&T %&;%1.T%O& messae. The
de@enrolment procedure is initiated.
!.2 /all /ontrol &er7('e&
The 1all 1ontrol services are provided by multiple 11 entities at the service access point M&11@!.P.
The 1all 1ontrol service class consists of the followin servicesB
@ Mobile oriinated and Mobile terminated call establishment for normal callsD
@ Mobile oriinated call establishment for emerency callsD
@ call maintaininD
@ call terminationD
@ call related !upplementary !ervices !upport.
!.2.1 Ser7('e &tate %(a4ra:
The 1all 1ontrol services provided at the service access point M&11@!.P are illustrated in the state diaram of
fiure :.*.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %) "elease #
RELEASE
REQUEST
DISONNECT
INDICATION
STATES
3,4,7,8,9,10
DISCONNECT
REQUEST
CALL INIT
NO CALL
PROCEEDING
RELEASE
REQUEST
CALL
DELIVERED
ACTIVE
CALL
RECEIVED
CONNECT
REQUEST
MT CALL
CONFIRMED
CALL
PRESENT
NULL 0
1
3
4 19
10
19
12
6
9
7
8
11
MNCC-SETUP-IND
MNCC-REJ-REQ
MNCC-REL-
REQ
MNCC-
DISC-
IND
MNCC-
REL-
IND
MNCC-REJ-IND
MNCC-SETUP-REQ
MNCC-DISC-
REQ
MNCC-
DISC-
IND
MNCC-CALL-
CONF-REQ
MNCC-
SETUP-
RSP
MNCC-
ALERT-
REQ
MNCC-
SETUP-RSP
MNCC-SETUP-
COMPL-IND (ERR)
MNCC-
DISC-
IND
MNCC-
DISC-
REQ
MNCC-SETUP-COMP-IND
MNCC-SETUP-
CNF
MNCC-
SETUP-
CNF
MNCC-
ALERT-
IND
MNCC-REL-
REQ
MNCC-
PROGRESS-
IND
MNCC-CALL
PROC-IND
MNCC-
REL-
CNF
MNCC-
FACILITY-
IND
ANY STATE
EXCEPT 0
ANY STATE
MNCC-
REL-
IND
0
ANY STATE
EXCEPT 0,19
MNCC-
FACILITY
REQ
0igure .'%1 Ser3ice graph of Call Control entit + MS side !page , of %$
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %/ "elease #
10 ACTIVE
28 M0
MODIFY
MNCC-MODIFY-CNF MNCC-MODIFY-REQ
MNCC-DTMF-START-REQ
CNF
MNCC-DTMF-STOP-REQ
CNF
MNCC-SYNC-IND (res ass)
MNCC-SYNC-IND (channel mode
modify)
MNCC-NOTIFY-REQ
IND
MNCC-MODIFY-IND
MNCC-SYNC-IND (res ass)
MNCC-SYNC-IND (channel mode
modify)
0igure .'%1 Ser3ice graph of Call Control entit + MS side 2cti3e state !page % of %$
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ %# "elease #
!.2.2 Ser7('e )r(:(t(7e&
Table .'%1 Primiti3es and parameters at MNCC+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
M.//CSTUPC#A STUP or M#G./> STUP !.2.2.1
M.//CSTUPC8.6 STUP !.2.2.2
M.//CSTUPC#SP /<../T !.2.2.3
M.//CSTUPC/.- /<../T !.2.2.4
M.//CSTUPC/<MPLTC#A - !.2.2."
M.//CSTUPC/<MPLTC8.6 - !.2.2.!
M.//C#DC#A #L+S /<MPLT !.2.2.7
M.//C#DC8.6 'a$&e !.2.2.E
M.//C/+LLC/<.-C#A /+LL /<.-8#M6 !.2.2.9
M.//C/+LL P#</C8.6 /+LL P#</68.G !.2.2.10
M.//CP#<G#SSC8.6 P#<G#SS !.2.2.11
M.//C+L#TC#A +L#T8.G !.2.2.12
M.//C+L#TC8.6 +L#T8.G !.2.2.13
M.//C.<T8->C#A .<T8-> !.2.2.14
M.//C.<T8->C8.6 .<T8-> !.2.2.1"
M.//C68S/C#A 68S/<../T !.2.2.1!
M.//C68S/C8.6 68S/<../T !.2.2.17
M.//C#LC#A #L+S !.2.2.1E
M.//C#LC8.6 #L+S !.2.2.19
M.//C#LC/.- #L+S or #L+S /<MPLT !.2.2.20
M.//C-+/8L8T>C#A 5a'(l(ty !.2.2.21
M.//C-+/8L8T>C8.6 5a'(l(ty !.2.2.22
M.//CST+#TC6TM-C#A ST+#T 6TM- !.2.2.23
M.//CST+#TC6TM-C/.- ST+#T 6TM- +/F or ST+#T 6TM- #D !.2.2.24
M.//CST<PC6TM-C#A ST<P 6TM- !.2.2.2"
M.//CST<PC6TM-C/.- ST<P 6TM- +/F !.2.2.2!
M.//CM<68->C#A M<68-> !.2.2.27
M.//CM<68->C8.6 M<68-> !.2.2.2E
M.//CM<68->C#S M<68-> /<MPLT !.2.2.29
M.//CM<68->C/.- M<68-> /<MPLT !.2.2.30
M.//CS>./C8.6 'a$&e (re&. a&&., '*annel :o%e :o%(5y) !.2.2.31
!.2.2.1 M.//CSTUPC#A
/e>uest to send a !2T3P or 2M2/G2&1L !2T3P messae to initiate Mobile oriinatin establishment of either a
normal or an emerency call.
!.2.2.2 M.//CSTUPC8.6
/eceipt of a !2T3P messae- the Mobile terminated call establishment has been initiated.
!.2.2.3 M.//CSTUPC#S
/esponse to send a 1O&&21T messae to indicate call acceptance by the Mobile terminated userD call control is
re>uested to attach the user connection (if it is not yet attached).
!.2.2.4 M.//CSTUPC/.-
/eceipt of a 1O&&21T messae- the Mobile oriinated call has been accepted by the remote called user.
!.2.2." M.//CSTUPC/<MPLC#A
/e>uest to send a 1O&&21T .1$&OK52;G2 messae- the mobile oriinatin call has been accepted.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3( "elease #
!.2.2.! M.//CSTUPC/<MPLC8.6
/eceipt of a 1O&&21T .1$&OK52;G2 messae- the Mobile terminated call establishment has been completedD for
a data call- the user is informed that the user connection is attached.
!.2.2.7 M.//C#DC#A
/e>uest to reject a Mobile terminated call if the call is refused or if the call cannot be accepted- e..- because of missin
compatibility.
!.2.2.E M.//C#DC8.6
%ndication that the Mobile oriinated call has been rejected- e.. if the MM connection cannot be provided or if the call
establishment initiation has been rejected by the networ".
!.2.2.9 M.//C/+LLC/<.-C#A
/e>uest to confirm a Mobile terminated call by sendin a 1.55 1O&7%/M2; messae. . bearer capability different
from that iven in M&11Q!2T3PQ%&; may be offered to the remote callin user.
!.2.2.10 M.//C/+LLCP#</C8.6
%ndication to the Mobile oriinatin user that call establishment has been initiated in the &etwor" and no more call
establishment information will be accepted by the &etwor".
!.2.2.11 M.//CP#<G#SSC8.6
%ndication to the Mobile user that a P/OG/2!! messae or a messae containin a progress %2 has been received- e..-
because the call is proressin in the P5M&J%!;& environment- or because the call has left the P5M&J%!;&
environment- or because in@band tonesJannouncement are available.
!.2.2.12 M.//C+L#TC#A
/e>uest to send an .52/T%&G messae from the called Mobile user to the remote callin user to indicate that user
alertin has been initiated.
!.2.2.13 M.//C+L#TC8.6
%ndication of the receipt of an .52/T%&G messae- alertin to the remote called user has been initiated.
!.2.2.14 M.//C.<T8->C#A
/e>uest to send information pertainin to a call- such as user suspended- to the &etwor" by the Mobile user.
!.2.2.1" M.//C.<T8->C8.6
%ndication to the Mobile user that information pertainin to a call- such as remote user suspended- has been received
from the &etwor".
!.2.2.1! M.//C68S/C#A
/e>uest to send a ;%!1O&&21T messae to the &etwor" in order to clear the end@to@end connection.
!.2.2.17 M.//C68S/C8.6
%ndication of reception of a ;%!1O&&21T messae- by which the &etwor" indicates that the end@to@end connection is
cleared.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3, "elease #
!.2.2.1E M.//C#LC#A
/e>uest of the Mobile user to send a /252.!2 messae to inform the &etwor" that the user intends to release the call
reference and the correspondin MM connection so that the &etwor" can release its MM connection and the
correspondent call reference.
!.2.2.19 M.//C#LC8.6
%ndication to the Mobile oriinatin or terminated user that a /252.!2 messae has been received and the &etwor"
intends to release its MM connection. The Mobile user is re>uested to release the call reference and the correspondin
MM connection.
!.2.2.20 M.//C#LC/.-
1onfirmation of the Mobile user#s re>uest to release the MM connection and call reference in the &etwor". The Mobile
user may release the call reference and the correspondin MM connection.
!.2.2.21 M.//C-+/8L8T>C#A
/e>uest to transport a facility %2 for a call related supplementary service invocation.
!.2.2.22 M.//C-+/8L8T>C8.6
%ndication that a facility %2 for a call related supplementary service invocation has been received.
!.2.2.23 M.//CST+#TC6TM-C#A
/e>uest to send a !T./T ;TM7 messae in order to start a ;TM7 control operation.
!.2.2.24 M.//CST+#TC6TM-C/.-
1onfirmation of the receipt of a !T./T ;TM7 .1$&OK52;G2 or !T./T ;TM7 /2R21T messae that the start
of a ;TM7 control operation has been ac"nowleded or rejected.
!.2.2.2" M.//CST<PC6TM-C#A
/e>uest to send a !TOP ;TM7 messae in order to stop a ;TM7 control operation.
!.2.2.2! M.//CST<PC6TM-C/.-
1onfirmation of the receipt of !TOP ;TM7 .1$&OK52;G2 messae- the ;TM7 control operation has been
stopped.
!.2.2.27 M.//CM<68->C#A
/e>uest to start Mobile oriinatin in@call modification by sendin a MO;%7L messae.
!.2.2.2E M.//CM<68->C8.6
/212%PT O7 . MO;%7L messae- a Mobile terminatin in@call modification has been initiated.
!.2.2.29 M.//CM<68->C#S
/esponse to send a MO;%7L 1OMP52T2 messae to indicate Mobile terminatin in@call modification completion by
the Mobile user.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3% "elease #
!.2.2.30 M.//CM<68->C/.-
/eceipt of a MO;%7L 1OMP52T2 messae- the Mobile oriinatin in@call modification has been completed.
!.2.2.31 M.//CS>./C8.6
%ndication that a dedicated channel assinment has been performed (res. ass. S Hresource assinedH) andJor the channel
mode has been chaned.
!.3 /all (n%e)en%ent S$))le:entary Ser7('e& S$))ort
!.3.1 Ser7('e &tate %(a4ra:
The primitives provided by the call independent !upplementary !ervices !upport entity and the transitions between
permitted states are shown in fiure :.3.
86L
/<..
M.SS-.6-#A
8.6
M.SS--+/8L8T>-#A
8.6
M.SS-.6-#A
8.6
M.SS-;G8.-#A
8.6
ST+TS0
86L - .o SS &(4nall(n4 tran&a't(on )en%(n4.
/<.. - SS &(4nall(n4 tran&a't(on e&ta,l(&*e%.
0igure .'31 Ser3ice graph of the call independent Supplementar Ser3ices Support entit + MS side
!.3.2 Ser7('e )r(:(t(7e&
Table .'31 Primiti3es and Parameters at MNSS+S2P + MS side
P"8M8T8*:S P2"2M:T:"S
(8n5o ele:ent& o5 :e&&a4e)
":0:":NC:
M.SSC;G8.C#A #G8ST# !.3.2.1
M.SSC;G8.C8.6 #G8ST# !.3.2.2
M.SSC-+/8L8T>C#A -+/8L8T> !.3.2.3
M.SSC-+/8L8T>C8.6 -+/8L8T> !.3.2.4
M.SSC.6C#A #L /<MPLT !.3.2."
M.SSC.6C8.6 #L /<MPLT !.3.2.!
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 33 "elease #
!.3.2.1 M.SSC;G8.C#A
/e>uest to send a /2G%!T2/ messae in order to establish a sinallin transaction for the provision of call
independent supplementary services. The re>uest for a call independent supplementary service invocation may be
included.
!.3.2.2 M.SSC;G8.C8.6
/eceipt of a /2G%!T2/ messae- a sinallin transaction is established for the provision of call independent
supplementary services after receipt of a /2G%!T2/ messae. The indication of a supplementary service invocation
may be included.
!.3.2.3 M.SSC-+/8L8T>C#A
/e>uest to send a 7.1%5%TL messae for the provision of a call independent supplementary service invocation.
!.3.2.4 M.SSC-+/8L8T>C8.6
/eceipt of a 7.1%5%TL messae for a call independent supplementary service invocation.
!.3.2." M.SSC.6C#A
/e>uest to send a /252.!2 1OMP52T2 messae in order to release the sinallin transaction. The re>uest for
transfer of a supplementary service facility may be included.
!.3.2.! M.SSC.6C8.6
/eceipt of a /252.!2 1OMP52T2 messae- the sinallin transaction has been released. The indication of a
supplementary service facility may be included.
!.4 S*ort Me&&a4e Ser7('e& S$))ort
The service provided by the 1M sublayer to support the short messae service are defined in
3GPP T! *=.+99 F<G.
!." Se&&(on Mana4e:ent Ser7('e& 5or GP#S-Ser7('e&
!ession Manaement services are provided at the !M/2G@!.P and the !&!M@!.P. The procedures for GP/! !ession
Manaement (i.e. P;P conte't activation- P;P conte't deactivation and P;P conte't modification) and M0M! !ession
Manaement (i.e. M0M! conte't activation and M0M! conte't deactivation) are available at the !M/2G@!.P.
0efore any user data transfer is initiated (e.via !&;1P in G!M case)- the P;P conte't activation procedure must be
performed. %n case of M0M!- the M! must also perform the procedures needed in order to activate a multicast service.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3& "elease #
!.".1 Se&&(on Mana4e:ent Ser7('e& 5or SM#G-S+P
Table .'-',1 Primiti3es and Parameters at SM":G+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
SM#G-P6P-+/T8V+T-#A P6P a%%re&&, AoS, .S+P8, +P., Proto'ol 'on5(4$rat(on
o)t(on&
!.".1.1
SM#G-P6P-+/T8V+T-/.- P6P a%%re&&, AoS, .S+P8, Proto'ol 'on5(4$rat(on
o)t(on&
!.".1.2
SM#G-P6P-+/T8V+T-#D /a$&e, .S+P8, Proto'ol 'on5(4$rat(on o)t(on& !.".1.3
SM#G-P6P-+/T8V+T-8.6 P6P a%%re&&, +P., )roto'ol 'on5(4$rat(on o)t(on& !.".1.4
SM#G-P6P-+/T8V+T-#D-#SP /a$&e, P6P a%%re&&, +P., )roto'ol 'on5(4$rat(on
o)t(on&, M;MS )roto'ol 'on5(4$rat(on o)t(on&
!.".1.14
SM#G-P6P-6+/T8V+T-#A .S+P8(&) tear %own (n%('ator, 'a$&e, )roto'ol
'on5(4$rat(on o)t(on&, M;MS )roto'ol 'on5(4$rat(on
o)t(on&
!.".1."
SM#G-P6P-6+/T8V+T-/.- .S+P8(&), )roto'ol 'on5(4$rat(on o)t(on&, M;MS
)roto'ol 'on5(4$rat(on o)t(on&
!.".1.!
SM#G-P6P-6+/T8V+T-8.6 .S+P8(&) (&), tear %own (n%('ator, 'a$&e, )roto'ol
'on5(4$rat(on o)t(on&, M;MS )roto'ol 'on5(4$rat(on
o)t(on&
!.".1.7
SM#G-P6P-M<68->-8.6 AoS, .S+P8, )roto'ol 'on5(4$rat(on o)t(on& !.".1.E
SM#G-P6P-M<68->-#A AoS, .S+P8, T-T, )roto'ol 'on5(4$rat(on o)t(on& !.".1.1E
SM#G-P6P-M<68->-/.- AoS, .S+P8, )roto'ol 'on5(4$rat(on o)t(on& !.".1.19
SM#G-P6P-M<68->-#D /a$&e, .S+P8, )roto'ol 'on5(4$rat(on o)t(on& !.".1.20
SM#G-P6P-+/T8V+T-S/-#A AoS, .S+P8, T-T, Pr(:ary .S+P8, )roto'ol
'on5(4$rat(on o)t(on&
!.".1.1"
SM#G-P6P-+/T8V+T-S/-/.- AoS, .S+P8, )roto'ol 'on5(4$rat(on o)t(on& !.".1.1!
SM#G-P6P-+/T8V+T-S/-#D /a$&e, .S+P8, )roto'ol 'on5(4$rat(on o)t(on& !.".1.17
SM#G-M;MS-+/T8V+T-#A M$lt('a&t a%%re&&, &$))orte% M;MS ,earer 'a)a,(l(t(e&,
.S+P8, +P., M;MS )roto'ol 'on5(4$rat(on o)t(on&
!.".1.21
SM#G-M;MS-+/T8V+T-/.- M$lt('a&t a%%re&&, .S+P8, M;MS )roto'ol 'on5(4$rat(on
o)t(on&
!.".1.22
SM#G-M;MS-+/T8V+T-#D /a$&e, .S+P8, M;MS )roto'ol 'on5(4$rat(on o)t(on& !.".1.23
SM#G-M;MS-+/T8V+T-8.6 M$lt('a&t a%%re&&, +P., M;MS )roto'ol 'on5(4$rat(on
o)t(on&
!.".1.24
!.".1.1 SM#G-P6P-+/T8V+T-#A
The M! initiates a primary P;P conte't activation. !M is re>uested to send the .1T%C.T2 P;P 1O&T2MT
/2O32!T messae to the networ". The P;P conte't is pendin activation.
!.".1.2 SM#G-P6P-+/T8V+T-/.-
The M! initiated primary P;P conte't activation succeeded. The networ" confirmed the P;P conte't activation- i.e. the
.1T%C.T2 P;P 1O&T2MT .112PT messae was received from the networ". %n G!M- this implies that !M has
ordered !&;1P to establish the needed 551 lin". %n the 3MT! case- this implies that the /51 lin" towards the /&1
has been established and that the !M has been informed about this from the /.0M service entity in the M!. (/.0M@
/.0 Manaement service entity is 77! and could lead to update of the protocol architecture in fiure 8.* and 8.3) The
P;P conte't is active.
!.".1.3 SM#G-P6P-+/T8V+T-#D
The P;P primary conte't activation failed- the P;P conte't is not activated. One reason for failure is that the networ"
rejected the activation attempt- which means the .1T%C.T2 P;P 1O&T2MT /2R21T messae was received.
.nother reason is e.. that it was not possible to establish the needed 551 lin" in the G!M case.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3- "elease #
!.".1.4 SM#G-P6P-+/T8V+T-8.6
The networ" as"ed for a P;P conte't activation. The /2O32!T P;P 1O&T2MT .1T%C.T%O& messae was
received from the networ". The M! reacts either by initiatin a new primary P;P conte't activation or by rejectin the
networ"#s re>uest.
!.".1." SM#G-P6P-6+/T8V+T-#A
The M! initiates a P;P conte't deactivationB !M is re>uested to send a ;2.1T%C.T2 P;P 1O&T2MT /2O32!T
messae to the networ". The P;P conte't is pendin deactivation. Presence of the teardown indicator will lead to
deactivation of all P;P conte'ts coupled to the identified P;P address. &!.P%(s) to be deallocated from the !&;1P
entity via the !&!M@!.P for the G!M case- are included in the primitive.
!.".1.! SM#G-P6P-6+/T8V+T-/.-
The M! initiated P;P conte't deactivation has been done. The networ" confirmed the P;P conte't deactivation- i.e. the
;2.1T%C.T2 P;P 1O&T2MT .112PT messae was received from the networ". 7or G!M !M has ordered !&;1P
to locally release not further needed 551 lin"s. %n the 3MT! case- the release of the /51 lin" towards the /&1 ta"es
place as a result of a /.0 release trier from the networ" side. !M has been informed about this from the /.0M
service entity in the M!. (/.0M@ /.0 Manaement service entity is 77! and could lead to update of the protocol
architecture in fiure 8.* and 8.3.) The P;P conte't has been deactivated.
!.".1.7 SM#G-P6P-6+/T8V+T-8.6
. networ" initiated P;P conte't deactivation has been performed. The ;2.1T%C.T2 P;P 1O&T2MT /2O32!T
messae has been received from the networ". The M! has ac"nowleded with the ;2.1T%C.T2 P;P 1O&T2MT
.112PT messae. The P;P conte't has been deactivated- the related 551 lin"s in G!M or /51 lin"s in 3MT! were
locally released. Presence of the teardown indicator will lead to deactivation of all P;P conte'ts coupled to the
identified P;P address. &!.P% is included in the primitive to allow identification of the P;P conte't(s) needin
deactivation.
!.".1.E SM#G-P6P-M<68->-8.6
. networ" initiated P;P conte't modification has been performed. The MO;%7L P;P 1O&T2MT /2O32!T
messae has been received from the networ". The modification has been ac"nowleded by sendin the MO;%7L P;P
1O&T2MT .112PT messae. One P;P conte't has been modified. 551 lin"s is adjusted.
!.".1.9 Vo(%
!.".1.10 Vo(%
!.".1.11 Vo(%
!.".1.12 Vo(%
!.".1.13 Vo(%
!.".1.14 SM#G-P6P-+/T8V+T-#D-#SP
The networ" re>uested P;P conte't activation failed.
!.".1.1" SM#G-P6P-+/T8V+T-S/-#A
The M! initiates a secondary P;P conte't activation. !M is re>uested to send the .1T%C.T2 !21O&;./L P;P
1O&T2MT /2O32!T messae to the networ". The P;P conte't is pendin activation.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3. "elease #
!.".1.1! SM#G-P6P-+/T8V+T-S/-/.-
The M! initiated secondary P;P conte't activation succeeded. The networ" confirmed the P;P conte't activation- i.e.
the .1T%C.T2 !21O&;./L P;P 1O&T2MT .112PT messae was received from the networ". %n G!M- this
implies that !M has ordered !&;1P to establish the needed 551 lin". %n the 3MT! case- this implies that the /51 lin"
towards the /&1 has been established and that the !M has been informed about this from the /.0M service entity in
the M!. (/.0M@ /.0 Manaement service entity is 77! and could lead to update of the protocol architecture in
fiure 8.* and 8.3) The P;P conte't connected to the same P;P address as the P;P conte't identified by the primary
&!.P% parameter in !M/2G@P;P@.1T%C.T2@!21@/2O is active. (#Primary &!.P%# will point to any one of the
other established P;P conte'ts for a iven P;P address).
!.".1.17 SM#G-P6P-+/T8V+T-S/-#D
The secondary P;P conte't activation failed- the P;P conte't is not activated. One reason for failure is that the networ"
rejected the activation attempt- which means the .1T%C.T2 !21O&;./L P;P 1O&T2MT /2R21T messae was
received. .nother reason is e.. that it was not possible to establish the needed 551 lin" in the G!M case.
!.".1.1E SM#G-P6P-M<68->-#A
.n M! initiated P;P conte't modification is re>uested. The MO;%7L P;P 1O&T2MT /2O32!T messae is sent to
the networ" and pendin acceptance. .ffected P;P conte't is identified via the &!.P% value included in the primitive.
!.".1.19 SM#G-P6P-M<68->-/.-
.n M! initiated P;P conte't modification has been accepted by the networ". The modification is ac"nowleded from
the networ" via the MO;%7L P;P 1O&T2MT .112PT messae. The addressed P;P conte't has been modified. 551
or /51 lin" is adjusted accordin to the Oo! returned from the networ".
!.".1.20 SM#G-P6P-M<68->-#D
.n M! initiated P;P conte't modification has been rejected by the networ". The rejection is sinalled from the
networ" via the MO;%7L P;P 1O&T2MT /2R21T messae with the cause code. The P;P conte't remains active
without chane of Oo!.
!.".1.21 SM#G-M;MS-+/T8V+T-#A
The M! initiates an M0M! conte't activation as re>uested by the networ". !M is re>uested to send the .1T%C.T2
M0M! 1O&T2MT /2O32!T messae to the networ". The M0M! conte't is pendin activation waitin for the
networ" confirmation.
!.".1.22 SM#G-M;MS-+/T8V+T-/.-
The M0M! conte't activation succeeded. The networ" confirmed the M0M! conte't activation- i.e. the .1T%C.T2
M0M! 1O&T2MT .112PT messae was received from the networ". The M0M! conte't is active.
!.".1.23 SM#G-M;MS-+/T8V+T-#D
The M0M! conte't activation failed- the M0M! conte't is not activated.
!.".1.24 SM#G-M;MS-+/T8V+T-#D-#SP
The networ" re>uested M0M! conte't activation failed. !M is re>uested to send the /2O32!T M0M! 1O&T2MT
.1T%C.T%O& /2R21T messae to the networ".
!.".1.2" SM#G-M;MS-+/T8V+T-8.6
The networ" as"ed for an M0M! conte't activation. The /2O32!T M0M! 1O&T2MT .1T%C.T%O& messae was
received from the networ". The M! reacts either by initiatin the activation of the M0M! conte't or by rejectin the
re>uest from the networ".
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3) "elease #
The !ession Manaement services provided at the service access point !M/2G@!.P are illustrated in the state
machines of fiures :.= and :.8 below. &ote- that each state machine describes only one P;PJM0M! conte't within the
!M entity.
.1T%C2
!M/2G@P;P@.1T%C.T2@/2O
.1T%C2
P2&;%&G
!M/2G@P;P@.1T%C.T2@1&7
%&.1T%C2
!M/2G@P;P@MO;%7L@%&;
!M/2G@P;P@;2.1T%C.T2@%&;
MO;%7L
P2&;%&G
!M/2G@P;P@MO;%7L@/2O
!M/2G@P;P@MO;%7L@1&7
%&.1T%C2
P2&;%&G
!M/2G@P;P@;2.1T%C.T2@/2O
!M/2G@P;P@;2.1T%C.T2@1&7
!M/2G@P;P@.1T%C.T2@!21@/2O
!M/2G@P;P@.1T%C.T2@!21@1&7
!M/2G@P;P@.1T%C.T2@%&;
!M/2G@P;P@.1T%C.T2@/2R@/!P
!M/2G@P;P@MO;%7L@/2R
!M/2G@P;P@.1T%C.T2@/2R
!M/2G@P;P@.1T%C.T2@!21@/2R
0igure .'&1 Session Management ser3ice states at the SM":G+S2P for GP"S P>P conte?t
handling + MS side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3/ "elease #

.1T%C2
!M/2G@M0M!@.1T%C.T2@/2O
.1T%C2
P2&;%&G
!M/2G@M0M!@.1T%C.T2@1&7
%&.1T%C2
!M/2G@P;P@;2.1T%C.T2@%&;
!M/2G@M0M!@.1T%C.T2@%&;

!M/2G@M0M!@.1T%C.T2@/2R@/!P

!M/2G@M0M!@.1T%C.T2@/2R

0igure .'-1 Session Management ser3ice states at the SM":G+S2P for M6MS conte?t handling + MS
side
!.".2 Se&&(on Mana4e:ent Ser7('e& 5or S.SM-S+P (GSM only)
The !&!M@!.P service primitives are defined in 3GPP T! ==.+:8 F9*aG.
!.".3 Se&&(on Mana4e:ent Ser7('e& 5or #+;MSM-S+P (UMTS only)
Table .'-'31 Ser3ice primiti3es and parameters at "26MSM+S2P + MS side
P"8M8T8*: P2"2M:T:"
!message4 info elements of message4
other parameters$
"eference
#+;MSM-+/T8V+T-8.6 .S+P8, AoS !.".3.1
#+;MSM-+/T8V+T-#SP .S+P8 !.".3.2
#+;MSM-6+/T8V+T-8.6 .S+P8& !.".3.3
#+;MSM-6+/T8V+T-#SP .S+P8& !.".3.4
#+;MSM-6+/T8V+T-#A .S+P8 !.".3."
#+;MSM-M<68->-8.6 .S+P8, AoS !.".3.!
#+;MSM-M<68->-#SP - !.".3.7
#+;MSM-ST+TUS-#A - /a$&e !.".3.E
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ 3# "elease #
!.".3.1 #+;MSM-+/T8V+T-8.6
%ndication used by the !M entity to inform the /.0M entity that an &!.P% has been activated for data transfer (e.. an
activate P;P 1onte't re>uest has been sent to the networ"). %t also informs the /.0M entity about the re>uested Oo!
profile for this &!.P%. The indication is sent by !M towards /.0M durin an onoin P;P conte't activation
procedure.
!.".3.2 #+;MSM-+/T8V+T-#SP
/esponse used by the /.0M entity to inform the !M entity that the indicated &!.P% is now in use and that a /.0 for
the indicated &!.P% is established.
!.".3.3 #+;MSM-6+/T8V+T-8.6
%ndication used by the !M entity to inform the /.0M entity that an &!.P%s has been de@allocated and cannot be used
by the /.0M entity anymore. The re>uest is sent by !M towards /.0M durin an onoin M! initiated as well as
networ" initiated P;P conte't de@activation procedure or durin local de@activation of a P;P conte't.
!.".3.4 #+;MSM-6+/T8V+T-#SP
This messae is the response to /.0M!M@;2.1T%C.T2@%&; used by the /.0M entity to inform the !M entity that
the &!.P% indicated is no loner in use. %t is either sent immediately when there is no correspondin bearer active or it
is sent after reception and processin of /.0M.!@/.0@/252.!2@%&; from access stratum.
!.".3." #+;MSM-6+/T8V+T-#A
This primitive is used by the /.0M entity to inform the !M entity that the /.0 for an &!.P% has been released. This
primitive is only sent for bearer with a /T@Oo! classes.
!.".3.! #+;MSM-M<68->-8.6
%ndication used by the !M entity to indicate the chane of the Oo! for an &!.P%. The indication is sent by !M towards
/.0M durin an onoin P;P conte't modification procedure.
!.".3.7 #+;MSM-M<68->-#SP
/esponse used by the /.0M entity to inform the !M entity that the indicated &!.P% and Oo! profile are now in use
and the /.0 for the &!.P% is established andJor released- if necessary.
!.".3.E #+;MSM-ST+TUS-#A
This primitive is used by the /.0M entity to inform the !M entity that /.0M cannot continue its operation due to
errors at the lower layer (i.e. .ccess !tratum) or at the /.0M layer. The 1ause parameter indicates the cause of the
error.
!.! #e4(&trat(on Ser7('e& 5or GP#S-Ser7('e&
The attachJdetach procedures comprise the reistration services which are provided at the GMM/2G@!.P.
%t shall be noted- that the reistration services for mobiles of class . or 0 may depend on the service states for GP/!
and non@GP/! services. Therefore the internal access points MM1OO/; and the GMM1OO/; (see fiure 8.3) are
used by GMM and MM to inform each other about the relevant conditions. &o service primitives between the entities
within the same sublayer- i.e. the MM sublayer- are defined in the present document. The Mobility Manaement for
class . and 0 mobiles is further specified in 3GPP T! *=.++< F:G.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &( "elease #
!.!.1 #e4(&trat(on Ser7('e& 5or GMM#G-S+P
Table .'.',1 Ser3ice primiti3es and parameters at GMM":G+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
GMM#G-+TT+/=-#A atta'*-ty)e, #+6>-t(:er, ST+.6;>-t(:er !.!.1.1
GMM#G-+TT+/=-/.- PLM.& MT-'a)&, atta'*-ty)e. !.!.1.2
GMM#G-+TT+/=-#D 'a$&e !.!.1.3
GMM#G-6T+/=-#A %eta'*-ty)e, )ower-o553nor:al-%eta'* !.!.1.4
GMM#G-6T+/=-/.- %eta'*-ty)e !.!.1."
GMM#G-6T+/=-8.6 %eta'*-ty)e !.!.1.!
!.!.1.1 GMM#G-+TT+/=-#A
M! initiates the GP/! andJor %M!% attach. GMM is re>uested to send an .TT.1A /2O32!T messae to the networ".
The attachment is reistration pendin in the M!.
!.!.1.2 GMM#G-+TT+/=-/.-
The attach (either GP/!@attach or %M!%@attach or both) was successful. The networ" confirmed the attach- i.e. the
.TT.1A .112PT messae was received by the M!. The 551 and // sublayer will be informed by GMM about the
T55% to be used.
!.!.1.3 GMM#G-+TT+/=-#D
The attach (either GP/!@attach or %M!%@attach or both) has failed. The networ" rejected the attach attempt- i.e. the
messae .TT.1A /2R21T was received from the networ".
!.!.1.4 GMM#G-6T+/=-#A
M! initiates GP/! andJor %M!% detachB GMM is re>uested to send a ;2T.1A /2O32!T messae- the detach
procedure is initiated. %n case of M! initiated detach at power@off- the procedure is terminated in the M! after sendin
the ;2T.1A /2O32!T messae.
!.!.1." GMM#G-6T+/=-/.-
The M! initiated detach (either GP/!@attach or %M!%@attach or both) has been completed.
The networ" confirmed the detach- i.e. the messae ;2T.1A .112PT was received from the networ". This finali(es
the detach procedure (normal- not at power off). .ny P;P conte't possibly activated before is deactivated.
!.!.1.! GMM#G-6T+/=-8.6
. networ" initiated detach has been performed. Or the detach has been performed locally due to e'piration of the
standby timer or a failed routin area update. %n the first case the ;2T.1A /2O32!T messae was from the networ".
.ny P;P conte't possibly activated before is deactivated.
The reistration services provided at the service access point GMM/2G@!.P are illustrated in the state machine of
fiure :.: below. &ote- that in state reistered the M! may be suspended from GP/! mobility manaement due to an
onoin 1! connection. The reistration procedure /outin .rea 3pdatin- which is not provided at the GMM/2G@
!.P- is not visible within the diaram.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &, "elease #

%;52
/2G%!T/.@
T%O& P2&;.
GMM/2G@
.TT.1A@/2O
GMM/2G@.TT.1A@17&
GMM/2G@
.TT.1A@/2R
GMM/2G@;2T.1A@17&
/2G%!T2/2;
GMM/2G@;2T.1A
@%&;

GMM/2G@;2T.1A
@/2O (power off)
GMM/2G@;2T.1A@/2O
(not power off)
;2@
/2G%!T/.@
T%O& P2&;.
0igure .'.1 "egistration ser3ices states at GMM":G+S2P for GP"S attach and detach + MS side
!.7 Ser7('e& )ro7(%e% to S.6/P ent(t(e& ,y GP#S Lo4('al L(nk
/ontrol &er7('e&
This clause is informative- the service primitives are defined in 3GPP T! ==.+:= F99aG. They are included here to
provide a complete overview of the radio interface protocol architecture.
5oical 5in" 1ontrol services are provided at the Oo!9@!.P @ Oo!= !.P towards the !&;1P and at the 55!M!@!.P
towards !M!.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &% "elease #
!.7.1 Ser7('e &tate %(a4ra: 5or AoS1-S+P, AoS2-S+P, AoS3-S+P an%
AoS4-S+P

55@2!T.05%!A@/2O
55@2!T.05%!A@%&;
55@2!T.05%!A@1&7
55@2!T.05%!A@/!P
55@3&%T;.T.@/2OJ%&;
55@3&%T;.T.@/2OJ%&;
55@/252.!2@%&;

55@3&%T;.T.@/2OJ%&;
55@;.T.@/2OJ1&7J%&;
%;52
K.%T
2!T
55@/252.!2@1&7


55@/252.!2@/2O
55@/252.!2@%&;

55@/252.!2@/2O

55@/252.!2@/2O
55@/252.!2@%&;
K.%T
;%!1.
.0M
2!T
0igure .')1 States to establish and release 26M mode operation
!.7.2 Ser7('e )r(:(t(7e& 5or AoS1-S+P, AoS2-S+P, AoS3-S+P an% AoS4-
S+P
Table .')'%1 Ser3ice primiti3es and parameters at @oS, to @oS& + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
LL-ST+;L8S=-#A TLL8, S.6/P re9$e&te% )ara:eter& (G86) !.7.2.1
LL-ST+;L8S=-/.- TLL8, S.6/P ne4ot(ate% )ara:eter& (G86) !.7.2.2
LL-ST+;L8S=-8.6 TLL8, S.6/P re9$e&te% )ara:eter& (G86), .201 !.7.2.3
LL-ST+;L8S=-#SP TLL8, S.6/P ne4ot(ate% )ara:eter& (G86) !.7.2.4
LL-#L+S-#A TLL8 !.7.2."
LL-#L+S-/-. TLL8 !.7.2.!
LL-#L+S-8.6 TLL8 !.7.2.7
LL-G86-#A TLL8, S.6/P re9$e&te% )ara:eter& (G86) !.7.2.E
LL-G86-8.6 TLL8, S.6/P re9$e&te% )ara:eter& (G86), .201 !.7.2.9
LL-G86-#SP TLL8, S.6/P ne4ot(ate% )ara:eter& (G86) !.7.2.10
LL-G86-/.- TLL8, S.6/P ne4ot(ate% )ara:eter& (G86), .201 !.7.2.11
LL-6+T+-#A TLL8, .-P6U, lo'al re5eren'e !.7.2.12
LL-6+T+-/.- TLL8, lo'al re5eren'e !.7.2.13
LL-6+T+-8.6 TLL8, .-P6U !.7.2.14
LL-U.8T6+T+-#A TLL8, .-P6U, )rote't, '()*er !.7.2.1"
LL-U.8T6+T+-8.6 TLL8, .-P6U !.7.2.1!
LL-ST+TUS-8.6 TLL8, 'a$&e !.7.2.17
!.7.2.1 LL-ST+;L8S=-#A
. 551 !.0M frame will be sent to establish the 551 .0M mode.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &3 "elease #
!.7.2.2 LL-ST+;L8S=-/.-
. 551 3. frame is received- the 551 .0M mode has been established.
!.7.2.3 LL-ST+;L8S=-8.6
. 551 !.0M frame is received.
!.7.2.4 LL-ST+;L8S=-#SP
. 551 3. frame will be sent- the .0M mode is established.
!.7.2." LL-#L+S-#A
. 551 ;%!1 frame will be sent to chane to 551 .;M mode.
!.7.2.! LL-#L+S-/.-
The 551 lin" has been disconnected- 551 is in .;M mode.
!.7.2.7 LL-#L+S-8.6
551 is in idle mode.
!.7.2.E LL-G86-#A
.n 551 M%; frame will be sent.
!.7.2.9 LL-G86-8.6
.n 551 M%; frame has been received.
!.7.2.10 LL-G86-#SP
.n 551 M%; frame will be sent as a response to a received M%; frame.
!.7.2.11 LL-G86-/.-
.n 551 M%; frame has been received as a response to a sent M%; frame.
!.7.2.12 LL-6+T+-#A
.n 551 % frame will be sent to the peer entity.
!.7.2.13 LL-6+T+-/.-
!uccessful reception of an 551 % frame has been ac"nowleded by the peer entity.
!.7.2.14 LL-6+T+-8.6
.n 551 % frame has been received from the peer entity.
!.7.2.1" LL-U.8T6+T+-#A
.n 551 3% frame will be sent to the peer entity.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ && "elease #
!.7.2.1! LL-U.8T6+T+-8.6
.n 551 3% frame has been received from the peer entity.
!.7.2.17 LL-ST+TUS-8.6
%ndication used by 551 to transfer 551 failures to the !&;1P sublayer. The failure may also be caused due to errors at
the /51JM.1 layer.
!.E Lo'at(on &er7('e& at t*e ty)e + LMU &(%e
The location services (e.. transfer of timin related measurement information by a type . 5M3) are provided at the
service access point M&51!@!.P. The service provided by the 1M sublayer to support the location services is defined
in 3GPP T! ==.+?9 F<aG.
!.E.1 Ser7('e &tate %(a4ra:
The positionin services provided at the service access point M&51!@!.P are illustrated in the state diaram of
fiure :.<.
1onnected
%dle
M&51!@02G%&@/2O
%&;
M&51!@2&;@/2O
%&;
M&51!@2&;@/2O
%&;
M&51!@7.1%5%TL@/2O
%&;
ST+TS0
86L - .o L/S &(4nall(n4 tran&a't(on )en%(n4.
/<.. - L/S &(4nall(n4 tran&a't(on e&ta,l(&*e%.
0igure .'/1 Ser3ice graph of the 9ocation Ser3ices Support entit + tpe 2 9MA side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &- "elease #
!.E.2 Ser7('e )r(:(t(7e&
Table .'/1 Primiti3es and Parameters at MN9CS+S2P + tpe 2 9MA side
P"8M8T8*:S P2"2M:T:"S
(8n5o ele:ent& o5 :e&&a4e)
":0:":NC:
M.L/SC;G8.C#A #G8ST# !.E.2.1
M.L/SC;G8.C8.6 #G8ST# !.E.2.2
M.L/SC-+/8L8T>C#A -+/8L8T> !.E.2.3
M.L/SC-+/8L8T>C8.6 -+/8L8T> !.E.2.4
M.L/SC.6C#A #L+S /<MPLT !.E.2."
M.L/SC.6C8.6 #L+S /<MPLT !.E.2.!
!.E.2.1 M.L/SC;G8.C#A
/e>uest to send a /2G%!T2/ messae in order to establish a sinallin transaction for the provision of location
services. The re>uest for transfer of a location service facility may be included.
!.E.2.2 M.L/SC;G8.C8.6
/eceipt of a /2G%!T2/ messae- a sinallin transaction is established for the provision of location services after
receipt of a /2G%!T2/ messae. The indication of a location service facility may be included.
!.E.2.3 M.L/SC-+/8L8T>C#A
/e>uest to send a 7.1%5%TL messae for the provision of a location service invocation. The re>uest for transfer of a
location service facility may be included.
!.E.2.4 M.L/SC-+/8L8T>C8.6
/eceipt of a 7.1%5%TL messae- a location service facility has been re>uested.
!.E.2." M.L/SC.6C#A
/e>uest to send a /252.!2 1OMP52T2 messae in order to release the sinallin transaction. The re>uest for
transfer of a location service facility may be included.
!.E.2.! M.L/SC.6C8.6
/eceipt of a /252.!2 1OMP52T2 messae- the sinallin transaction has been released. The indication of a location
service facility may be included.
7 Ser7('e& )ro7(%e% ,y &(4nall(n4 layer 3 on t*e
.etwork &(%e
%n this clause- the services provided by sinallin layer 3 on the networ" side are described which belon to the 1M
sub@layer functional bloc"s of 11- !M!- 51!- and !!. The services correspondin to further functional bloc"s of the
1M sublayer are not further described in this clause.
7.1 /all 'ontrol &er7('e&
The 1all 1ontrol services are provided by multiple 11 entities at the service access point M&11@!.P.
The 1all 1ontrol service class consists of the followin servicesB
@ call establishmentD
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &. "elease #
@ call maintaininD
@ call terminationD
@ call related !upplementary !ervices !upport.
7.1.1 Ser7('e &tate %(a4ra:
The 1all 1ontrol services provided at the service access point M&11@!.P are illustrated in fiure ?.9.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &) "elease #
RELEASE
REQUEST
DISONNECT
INDICATION
DISCONNECT
REQUEST
CALL INIT
NO CALL
PROCEEDING
CALL
DILIVERED
ACTIVE
CALL
RECEIVED
CONNECT
REQUEST
MT CALL
CONFIRMED
CALL
PRESENT
NULL
0
1
3
4
10
19
12
6
9
7
8
11
MNCC-
REL-
IND
MNCC-REJ-IND
MNCC-SETUP-REQ
MNCC-
DISC-
IND
MNCC-
DISC-
REQ
MNCC-
ALERT-
IND
MNCC-
FACILITY-
IND
ANY STATE
EXCEPT 0
ANY STATE
MNCC-
REL-
IND
0
ANY STATE
EXCEPT 0,19
MNCC-
FACILITY
REQ
MNCC-SETUP-REQ
MNCC-REJ-IND
STATES
4,6,8,9,10
MNCC-
REL-CNF
MNCC-
DISC-
IND
MNCC-
CALL-
CONF-
IND
MNCC-
ALERT-
IND
MNCC-
SETUP-
CNF
MNCC-
SETUP-CNF
MNCC-SETUP-COMPL-REQ
MNCC-CALL
PROC-REQ
CONNECT
INDICATION
28
MNCC-
PROGRESS-
REQ MNCC-
ALERT-
REQ
MNCC-
SETUP-
RSP
MNCC-REL
REQ
0igure )',1 !page , of %$ Ser3ice graph of Call Control entit + Network side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &/ "elease #
10 +/T8V
27 MT
M<68->
M.//-M<68->-/.- M.//-M<68->-#A
M.//-ST+#T-6TM--8.6
#SP
M.//-ST<P-6TM--8.6
#SP
M.//-.<T8->-#A
8.6
M.//-M<68->-8.6
0igure )',1 !page % of %$ Ser3ice graph of Call Control entit + Network side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ &# "elease #
7.1.2 Ser7('e )r(:(t(7e&
Table )',1 Primiti3es and Parameters at MNCC+S2P + Network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
M.//CSTUPC#A STUP (n'l. Mo,(le 86 or M#G./> STUP 7.1.2.1
M.//CSTUPC8.6 STUP 7.1.2.2
M.//CSTUPC#SP /<../T 7.1.2.3
M.//CSTUPC/.- /<../T 7.1.2.4
M.//CSTUPC/<MPLC#A /<../T +/F.<BL6G 7.1.2."
M.//CSTUPC/<MPLC8.6 /<../T +/F.<BL6G 7.1.2.!
M.//C#DC#A #L+S /<MPLT 7.1.2.7
M.//C#DC8.6 'a$&e 7.1.2.E
M.//C/+LLC/<.-C8.6 /+LL /<.-8#M6 7.1.2.9
M.//C/+LL P#</C#A /+LL P#</68.G 7.1.2.10
M.//CP#<G#SSC#A P#<G#SS 7.1.2.11
M.//C+L#TC#A +L#T8.G 7.1.2.12
M.//C+L#TC8.6 +L#T8.G 7.1.2.13
M.//C.<T8->C#A .<T8-> 7.1.2.14
M.//C.<T8->C8.6 .<T8-> 7.1.2.1"
M.//C68S/C#A 68S/<../T 7.1.2.1!
M.//C68S/C8.6 68S/<../T 7.1.2.17
M.//C#LC#A #L+S or 68S/<../T 7.1.2.1E
M.//C#LC8.6 #L+S 7.1.2.19
M.//C#LC/.- #L+S or #L+S /<MPLT 7.1.2.20
M.//C-+/8L8T>C#A 5a'(l(ty 7.1.2.21
M.//C-+/8L8T>C8.6 5a'(l(ty 7.1.2.22
M.//CST+#TC6TM-C8.6 ST+#T 6TM- 7.1.2.23
M.//CST+#TC6TM-C#SP ST+#T 6TM- +/F or ST+#T 6TM- #D 7.1.2.24
M.//CST<PC6TM-C8.6 ST<P 6TM- 7.1.2.2"
M.//CST<PC6TM-C#SP ST<P 6TM- +/F 7.1.2.2!
M.//CM<68->C#A M<68-> or ;/-)ara:eter 7.1.2.27
M.//CM<68->C8.6 ;/-)ara:eter 7.1.2.2E
M.//CM<68-> #S M<68-> /<MPLT 7.1.2.29
M.//CM<68->C/.- ;/-)ara:eter 7.1.2.30
7.1.2.1 M.//CSTUPC#A
/e>uest to send a !2T3P messae to initiate Mobile terminated establishment.
7.1.2.2 M.//CSTUPC8.6
/eceipt of a !2T3P or 2M2/G2&1L !2T3P messae- the Mobile oriinatin call establishment has been initiated.
7.1.2.3 M.//CSTUPC#SP
/esponse to send a 1O&&21T messae to indicate call acceptance by the remote user.
7.1.2.4 M.//CSTUPC/.-
/eceipt of a 1O&&21T messae- the Mobile terminated call has been accepted.
7.1.2." M.//CSTUPC/<MPLC#A
/e>uest to send a 1O&&21T .1$&OK52;G2 messae- the Mobile terminated call establishment has been
completed.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -( "elease #
7.1.2.! M.//CSTUPC/<MPLC8.6
%ndication of the receipt of a 1O&&21T .1$&OK52;G2 messae- the Mobile oriinatin call establishment has
been completed.
7.1.2.7 M.//C#DC#A
/eject the Mobile oriinated call establishment if the call cannot be accepted.
7.1.2.E M.//C#DC8.6
. Mobile terminated call was rejected by the M!- e.. because of missin compatibility.
7.1.2.9 M.//C/+LLC/<.-C8.6
/eceipt of a 1.55 1O&7%/M2; messae- the Mobile terminated call has been confirmed. . bearer capability
different from that iven in M&11Q!2T3PQ/2O may be offered to the remote callin user.
7.1.2.10 M.//C/+LLCP#</C#A
/e>uest to send a 1.55 P/O122;%&G messae to indicate to the Mobile oriinatin user that call establishment has
been initiated in the &etwor" and no more call establishment information will be accepted.
7.1.2.11 M.//CP#<G#SSC#A
/e>uest to send a P/OG/2!! messae or to piy@bac" a proress %2 in a suitable 11 messae in order to ive the
Mobile user information about the call- e.. that the call is proressin in the P5M&J%!;& environment- or that the call
has left the P5M&J%!;& environment- or that in@band tonesJannouncement are available.
7.1.2.12 M.//C+L#TC#A
/e>uest to send an .52/T%&G messae to indicate to the Mobile oriinatin user that remote called user alertin has
been initiated.
7.1.2.13 M.//C+L#TC8.6
/eceipt of an .52/T%&G messae from the Mobile terminated user to be sent to the remote callin user to indicate that
user alertin has been initiated.
7.1.2.14 M.//C.<T8->C#A
/e>uest to send information pertainin to a call- such as user suspended- to the Mobile oriinatin or the Mobile
terminated user.
7.1.2.1" M.//C.<T8->C8.6
%ndication from the Mobile oriinatin or Mobile terminated user of information pertainin to a call- such as remote
user suspended.
7.1.2.1! M.//C68S/C#A
/e>uest to send a ;%!1O&&21T messae to the M! in order to clear the end@to@end connection.
7.1.2.17 M.//C68S/C8.6
/eceipt of a ;%!1O&&21T messae- the M! indicates that the end@to@end connection is cleared.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -, "elease #
7.1.2.1E M.//C#LC#A
/e>uest to send a /252.!2 messae to inform the M! that the networ" intends to release the MM connection and the
correspondent call reference.
7.1.2.19 M.//C#LC8.6
/eceipt of a /252.!2 messae- the M! intends to release its MM connection and call reference. The &etwor" is
re>uested to release its call reference and MM connection.
7.1.2.20 M.//C#LC/.-
The /252.!2 1OMP52T2 messae has been received- the MM connection in the M! has been released- the &etwor"
itself shall release its MM connection and the correspondin call reference.
7.1.2.21 M.//C-+/8L8T>C#A
/e>uest to transport a facility %2 for call related supplementary service invocations.
7.1.2.22 M.//C-+/8L8T>C8.6
%ndication that a facility %2 for call related supplementary service invocations has been received.
7.1.2.23 M.//CST+#TC6TM-C8.6
%ndicate the receipt of a !T./T ;TM7 messae in order to start a ;TM7 control operation.
7.1.2.24 M.//CST+#TC6TM-C#SP
/e>uest to send a !T./T ;TM7 .1$&OK52;G2 or !T./T ;TM7 /2R21T messae in order to ac"nowlede or
reject the start of a ;TM7 control operation.
7.1.2.2" M.//CST<PC6TM-C8.6
%ndicate the receipt of a !TOP ;TM7 messae in order to stop a ;TM7 control operation.
7.1.2.2! M.//CST<PC6TM-C#SP
/e>uest to send a !TOP ;TM7 .1$&OK52;G2 messae in order to ac"nowlede the completion of a ;TM7
control operation.
7.1.2.27 M.//CM<68->C#A
/e>uest to start the Mobile terminatin in@call modification.
7.1.2.2E M.//CM<68->C8.6
/eceipt of a MO;%7L messae- the Mobile oriinatin in@call modification has been initiated.
7.1.2.29 M.//CM<68->C#S
/esponse to send a MO;%7L 1OMP52T2 to indicate to the Mobile user that the mobile oriinatin in@call
modification procedure has been completed.
7.1.2.30 M.//CM<68->C/.-
1onfirmation that the Mobile terminatin in@call modification has been completed.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -% "elease #
7.2 /all (n%e)en%ent S$))le:entary Ser7('e& S$))ort
7.2.1 Ser7('e &tate %(a4ra:
The primitives provided by the call independent !upplementary !ervices !upport entity and the transitions between
permitted states are shown in the service raph of fiure ?.* below.
86L
/<..
M.SS-.6-#A
8.6
M.SS-;G8.-8.6
#A
M.SS--+/8L8T>-#A
8.6
M.SS-.6-#A
8.6
ST+TS0
86L - .o SS &(4nall(n4 tran&a't(on )en%(n4.
/<.. - SS &(4nall(n4 tran&a't(on e&ta,l(&*e%.
0igure )'%1 Ser3ice graph of the call independent Supplementar Ser3ices Support entit + Network
side
7.2.2 Ser7('e )r(:(t(7e&
Table )'%1 Primiti3es and Parameters at MNSS+S2P + Network side
P"8M8T8*:S P2"2M:T:"S
(8n5o ele:ent& o5 :e&&a4e)
":0:":NC:
M.SSC;G8.C#A #G8ST# 7.2.2.1
M.SSC;G8.C8.6 #G8ST# 7.2.2.2
M.SSC-+/8L8T>C#A -+/8L8T> 7.2.2.3
M.SSC-+/8L8T>C8.6 -+/8L8T> 7.2.2.4
M.SSC.6C#A #L+S /<MPLT 7.2.2."
M.SSC.6C8.6 #L+S /<MPLT 7.2.2.!
7.2.2.1 M.SSC;G8.C#A
/e>uest to send a /2G%!T2/ messae in order to establish a sinallin transaction for the provision of call
independent supplementary services. The re>uest for a supplementary service invocation may be included.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -3 "elease #
7.2.2.2 M.SSC;G8.C8.6
/eceipt of a /2G%!T2/ messae- a sinallin transaction is established for the provision of call independent
supplementary services. The indication of a supplementary service invocation may be included.
7.2.2.3 M.SSC-+/8L8T>C#A
/e>uest to send a 7.1%5%TL messae for the provision of a call independent supplementary service facility.
7.2.2.4 M.SSC-+/8L8T>C8.6
/eceipt of a 7.1%5%TL messae- a supplementary service facility has been re>uested.
7.2.2." M.SSC.6C#A
/e>uest to send a /252.!2 1OMP52T2 messae in order to release the sinallin transaction by sendin a
/252.!2 1OMP52T2 messae. The re>uest for transfer of a supplementary service facility may be included.
7.2.2.! M.SSC.6C8.6
%ndication that the sinallin transaction has been released after receipt of a /252.!2 1OMP52T2 messae. The
indication of a supplementary service facility may be included.
7.3 S*ort Me&&a4e Ser7('e& S$))ort
The service provided by the 1M sublayer to support the short messae service are defined in 3GPP T! *=.+99 F<G.
7.4 Ser7('e& )ro7(%e% to S.6/P an% SMS ent(t(e& ,y GP#S
Lo4('al L(nk /ontrol &er7('e&
This clause is informative- the service primitives are defined in 3GPP T! ==.+:= F99aG. They are included here to
provide a complete overview of the radio interface protocol architecture.
On the networ" side- 5oical 5in" 1ontrol services are provided at the Oo!9@!.P @ Oo!= !.P towards the !&;1P
and at the 55!M!@!.P towards !M!.
7.4.1 Ser7('e &tate %(a4ra: 5or AoS1-S+P, AoS2-S+P, AoS3-S+P an%
AoS4-S+P
The service state diaram is identical on the networ" side is identical to the one shown in fiure :.? for the mobile side.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -& "elease #
7.4.2 Ser7('e )r(:(t(7e& 5or AoS1-S+P, AoS2-S+P, AoS3-S+P an% AoS4-
S+P
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
LL-ST+;L8S=-#A TLL8, S.6/P re9$e&te% )ara:eter& (G86) 7.4.2.1
LL-ST+;L8S=-/.- TLL8, S.6/P ne4ot(ate% )ara:eter& (G86), .201 7.4.2.2
LL-ST+;L8S=-8.6 TLL8, S.6/P re9$e&te% )ara:eter& (G86), .201 7.4.2.3
LL-ST+;L8S=-#SP TLL8, S.6/P ne4ot(ate% )ara:eter& (G86) 7.4.2.4
LL-#L+S-#A TLL8 7.4.2."
LL-#L+S-/.- TLL8 7.4.2.!
LL-#L+S-8.6 TLL8 7.4.2.7
LL-G86-#A TLL8, S.6/P re9$e&te% )ara:eter& (G86) 7.4.2.E
LL-G86-8.6 TLL8, S.6/P re9$e&te% )ara:eter& (G86), .201 7.4.2.9
LL-G86-#SP TLL8, S.6/P ne4ot(ate% )ara:eter& (G86) 7.4.2.10
LL-G86-/.- TLL8, S.6/P ne4ot(ate% )ara:eter& (G86), .201 7.4.2.11
LL-6+T+-#A TLL8, .-P6U, lo'al re5eren'e 7.4.2.12
LL-6+T+S.T-8.6 TLL8, lo'al re5eren'e, V(S) 7.4.2.13
LL-6+T+-/.- TLL8, lo'al re5eren'e 7.4.2.14
LL-6+T+-8.6 TLL8, .-P6U 7.4.2.1"
LL-U.8T6+T+-#A TLL8, .-P6U, )rote't, '()*er 7.4.2.1!
LL-U.8T6+T+-8.6 TLL8, .-P6U 7.4.2.17
LL-ST+TUS-8.6 TLL8, 'a$&e 7.4.2.1E
7.4.2.1 LL-ST+;L8S=-#A
. 551 !.0M frame will be sent to establish the 551 .0M mode.
7.4.2.2 LL-ST+;L8S=-/.-
. 551 3. frame is received- the 551 .0M mode has been established.
7.4.2.3 LL-ST+;L8S=-8.6
. 551 !.0M frame is received.
7.4.2.4 LL-ST+;L8S=-#SP
. 551 3. frame will be sent- the .0M mode is established.
7.4.2." LL-#L+S-#A
. 551 ;%!1 frame will be sent to chane to 551 .;M mode.
7.4.2.! LL-#L+S-/.-
The 551 lin" has been disconnected- 551 is in .;M mode.
7.4.2.7 LL-#L+S-8.6
551 is in idle mode.
7.4.2.E LL-G86-#A
.n 551 M%; frame will be sent.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -- "elease #
7.4.2.9 LL-G86-8.6
.n 551 M%; frame is received.
7.4.2.10 LL-G86-#SP
.n 551 M%; frame will be sent as a reply to a received M%; frame.
7.4.2.11 LL-G86-/.-
.n 551 M%; frame has been received as a reply to a sent M%; frame.
7.4.2.12 LL-6+T+-#A
.n 551 % frame will be sent to the peer entity.
7.4.2.13 LL-6+T+S.T-8.6
The sent 551 frame was sent with the C(!) indicated.
7.4.2.14 LL-6+T+-/.-
!uccessful reception of an 551 % frame has been ac"nowleded by the peer entity.
7.4.2.1" LL-6+T+-8.6
.n 551 % frame has been received form the peer entity.
7.4.2.1! LL-U.8T6+T+-#A
.n 551 3% frame will be sent to the peer entity.
7.4.2.17 LL-U.8T6+T+-8.6
.n 551 3% frame has been received from the peer entity.
7.4.2.1E LL-ST+TUS-8.6
%ndication used by 551 to transfer 551 failures to the !&;1P sublayer. The failure may also be caused due to errors at
the /51JM.1 layer.
7." Se&&(on Mana4e:ent Ser7('e& 5or GP#S an% M;MS
On the networ" side !ession Manaement !ervices are provided at the !&!M@!.P and !M/2G@!.P. .t the !M/2G@
!.P- the assumption ta"en is that the M! initiated primary and secondary P;P conte't activation- the M! initiated P;P
conte't modification and deactivation- and the M0M! conte't activation and deactivation are not visible- i.e. the
service for these functions on the networ" side stops in the !M sublayer entity.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -. "elease #
7.".1 Se&&(on Mana4e:ent Ser7('e& 5or SM#G-S+P
Table )'-',1 Primiti3es and Parameters at SM":G+S2P + network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
SM#G-P6P-+/T8V+T-#A P6P a%%re&&, +P., )roto'ol 'on5(4$rat(on o)t(on& 7.".1.1
SM#G-P6P-+/T8V+T-#D /a$&e, P6P a%%re&&, +P., )roto'ol 'on5(4$rat(on
o)t(on&
7.".1.2
SM#G-P6P-6+/T8V+T-#A .S+P8(&), tear%own (n%('ator, 'a$&e, )roto'ol
'on5(4$rat(on o)t(on&, M;MS )roto'ol 'on5(4$rat(on
o)t(on&
7.".1.3
SM#G-P6P-6+/T8V+T-/.- .S+P8(&) , )roto'ol 'on5(4$rat(on o)t(on&, M;MS
)roto'ol 'on5(4$rat(on o)t(on&
7.".1.4
SM#G-P6P-M<68->-#A AoS, .S+P8, )roto'ol 'on5(4$rat(on o)t(on& 7.".1."
SM#G P6P-M<68->-/.- .S+P8, )roto'ol 'on5(4$rat(on o)t(on& 7.".1.!
SM#G P6P-M<68->-#D .S+P8, )roto'ol 'on5(4$rat(on o)t(on& 7.".1.7
SM#G-M;MS-+/T8V+T-#A M$lt('a&t a%%re&&, +P., M;MS )roto'ol 'on5(4$rat(on
o)t(on&
7.".1.E
SM#G-M;MS-+/T8V+T-#D /a$&e, :$lt('a&t a%%re&&, +P., M;MS )roto'ol
'on5(4$rat(on o)t(on&
7.".1.9
7.".1.1 SM#G-P6P-+/T8V+T-#A
The networ" initiates a P;P conte't activation. !M is re>uested to send the /2O32!T P;P 1O&T2MT
.1T%C.T%O& messae to the M!. The P;P conte't is pendin activation. The networ" e'pects that the M! continues
with a normal M! initiated P;P conte't activation. Therefore- at the !M/2G@!.P no confirmation is provided.
7.".1.2 SM#G-P6P-+/T8V+T-#D
The networ" initiated P;P conte't activation failed. 2ither the /2O32!T P;P 1O&T2MT .1T%C.T%O& /2R21T
messae was received from the M!- or lower layer failure or timer e'piry caused abortion of the P;P conte't activation
procedure.
7.".1.3 SM#G-P6P-6+/T8V+T-#A
The networ" initiates a P;P or M0M! conte't deactivation. !M is re>uested to send a ;2.1T%C.T2 P;P
1O&T2MT /2O32!T messae. The P;P conte't is pendin deactivation. Presence of the teardown indicator will lead
to deactivation of all P;P conte'ts coupled to the identified P;P address. &!.P%(s) to be deallocated from the !&;1P
entity via the !&!M@!.P for the G!M case- are included in the primitive.
7.".1.4 SM#G-P6P-6+/T8V+T-/.-
The networ" initiated P;P or M0M! conte't deactivation has been concluded. The M! confirmed the P;P conte't
deactivation- i.e. the ;2.1T%C.T2 P;P 1O&T2MT .112PT messae was received. Then !M ordered !&;1P to
locally release 551 lin"(s) not further needed for the G!M case. %n the 3MT! case- release of affected GTP@3
tunnel(s) towards the /&1 has ta"en place. The P;P conte't is deactivated.
7.".1." SM#G-P6P-M<68->-#A
The networ" initiates a modification of the P;P conte't. !M is re>uested to send a MO;%7L P;P 1O&T2MT
/2O32!T messae to the M!. The P;P conte't is pendin modification.
7.".1.! SM#G-P6P-M<68->-/.-
The P;P conte't modification has been concluded. The M! confirmed the P;P conte't modification- i.e. the MO;%7L
P;P 1O&T2MT .112PT messae was received. Then- for the G!M case- !M ordered !&;1P to adjust the affected
551 lin" as re>uired. 7or the 3MT! case- /.0 properties were updated as re>uired. The P;P conte't is modified.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -) "elease #
7.".1.7 SM#G-P6P-M<68->-#D
The P;P conte't modification has been rejected. ;ue to timer e'piry or lower layer failure the modification procedure
has been aborted.
7.".1.E SM#G-M;MS-+/T8V+T-#A
The networ" initiates an M0M! conte't activation. !M is re>uested to send the /2O32!T M0M! 1O&T2MT
.1T%C.T%O& messae to the M!. The M0M! conte't is pendin activation. The networ" e'pects that the M!
continues with the M0M! conte't activation. Therefore- at the !M/2G@!.P no confirmation is provided.
7.".1.9 SM#G-M;MS-+/T8V+T-#D
The networ" initiated M0M! conte't activation failed. 2ither the /2O32!T M0M! 1O&T2MT /2R21T messae
was received from the M!- or lower layer failure or timer e'piry caused abortion of the M0M! conte't activation
procedure.
7.".2 Se&&(on Mana4e:ent Ser7('e& 5or S.SM-S+P
The !&!M@!.P service primitives are defined in 3GPP T! ==.+:8 F9*aG.
7.! Lo'at(on &er7('e& at t*e .etwork &(%e
The location services (e.. networ" initiation of timin related measurements in a type . 5M3) are provided at the
service access point M&51!@!.P. The service provided by the 1M sublayer to support the location services is defined
in 3GPP T! ==.+?9 F<aG (for communication with a type . 5M3 only).
7.!.1 Ser7('e &tate %(a4ra:
The primitives provided by the call independent 5ocation !ervices !upport entity and the transitions between permitted
states are shown in the service raph of fiure ?.: below.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -/ "elease #
1onnected
%dle
M&51!@02G%&@/2O
%&;
M&51!@2&;@/2O
%&;
M&51!@2&;@/2O
%&;
M&51!@7.1%5%TL@/2O
%&;
ST+TS0
86L - .o L/S &(4nall(n4 tran&a't(on )en%(n4.
/<.. - L/S &(4nall(n4 tran&a't(on e&ta,l(&*e%.
0igure )'.1 Ser3ice graph of the 9ocation Ser3ices Support entit + Network side
7.!.2 Ser7('e )r(:(t(7e&
Table )'.1 Primiti3es and Parameters at MN9CS+S2P + Network side
P"8M8T8*:S P2"2M:T:"S
(8n5o ele:ent& o5 :e&&a4e)
":0:":NC:
M.L/SC;G8.C#A #G8ST# 7.!.2.1
M.L/SC;G8.C8.6 #G8ST# 7.!.2.2
M.L/SC-+/8L8T>C#A -+/8L8T> 7.!.2.3
M.L/SC-+/8L8T>C8.6 -+/8L8T> 7.!.2.4
M.L/SC.6C#A #L+S /<MPLT 7.!.2."
M.L/SC.6C8.6 #L+S /<MPLT 7.!.2.!
7.!.2.1 M.L/SC;G8.C#A
/e>uest to send a /2G%!T2/ messae in order to establish a sinallin transaction for the provision of location
services. The re>uest for a location service invocation may be included.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ -# "elease #
7.!.2.2 M.L/SC;G8.C8.6
/eceipt of a /2G%!T2/ messae- a sinallin transaction is established for the provision of location services. The
indication of a location service invocation may be included.
7.!.2.3 M.L/SC-+/8L8T>C#A
/e>uest to send a 7.1%5%TL messae for the provision of a location service facility.
7.!.2.4 M.L/SC-+/8L8T>C8.6
/eceipt of a 7.1%5%TL messae- a location service facility has been re>uested.
7.!.2." M.L/SC.6C#A
/e>uest to send a /252.!2 1OMP52T2 messae in order to release the sinallin transaction by sendin a
/252.!2 1OMP52T2 messae. The re>uest for transfer of a location service facility may be included.
7.!.2.! M.L/SC.6C8.6
%ndication that the sinallin transaction has been released after receipt of a /252.!2 1OMP52T2 messae. The
indication of a location service facility may be included.
E Ser7('e& a&&$:e% 5ro: &(4nall(n4 layer& 1 an% 2
The services provided by layer * are defined in detail in 3GPP T! ==.++8 F=G. . short summary is iven below.
%n addition- layer 9 communicates directly with layer 3 for information transfer related to channel manaement and to
measurement control. !ee subclause <.8 below.
E.1 Pr(or(ty
Messaes from layer 3 can be sent withB
@ no priorityD
i.e. the messaes are sent in first@in@first@out orderD
@ priorityD
i.e. a messae with this indication is sent as early as possible by layer *.
E.2 Una'knowle%4e% (n5or:at(on tran&5er
Transfer of unac"nowleded information usin the primitives ;5Q3&%TQ;.T.Q /2O32!TJ%&;%1.T%O&.
E.3 +'knowle%4e% (n5or:at(on tran&5er
Transfer of information in multiframe ac"nowleded mode includinB
@ establishment of data lin" connection between 53 entitiesD
@ transfer of information in ac"nowleded modeD
@ release of the data lin" connection.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .( "elease #
The primitives associated with ac"nowleded information transfer areB
@ ;5Q2!T.05%!AQ/2O32!TJ%&;%1.T%O&J1O&7%/M for establishment of ac"nowleded modeD
@ ;5Q;.T.Q/2O32!TJ%&;%1.T%O& for re>uestin the transmission of a messae unit and for indicatin the
reception of a messae unitD
@ ;5Q!3!P2&;Q/2O32!TJ;5Q/252.!2Q1O&7%/M for re>uestin and confirmin the suspension of the
ac"nowleded information transfer in the M! upon channel chaneD
@ ;5Q/2!3M2Q/2O32!TJ;5Q2!T.05%!AQ1O&7%/M for re>uestin and confirmin the resumption of the
ac"nowleded information transfer in the M! after suspension at channel chaneD
@ ;5Q/252.!2Q/2O32!TJ%&;%1.T%O&J1O&7%/M for the termination of ac"nowleded mode operationD
@ ;5Q/21O&&21TQ/2O32!T for re>uestin the re@establishment of ac"nowleded information transfer in the
M! on the old channel after channel chane failure.
E.4 #an%o: a''e&&
The transmissionJreception of a random access burst is controlled by the primitives
;5Q/.&;OMQ.112!!Q/2O32!TJ%&;%1.T%O&J1O&7%/M.
E." /*annel :ana4e:ent an% :ea&$re:ent&
The manaement of channels- i.e. their activation- deactivation- confiuration- deconfiuration- throuh@connection and
disconnection is controlled by the // sublayer in layer 3. The measurements performed by the physical layer are also
controlled by the // sublayer of layer 3 and they are reported to layer 3.
These functions use the primitives MPAQ%&7O/M.T%O&Q/2O32!TJ%&;%1.T%O&J1O&7%/M.T%O&.
9 8nterlayer &er7('e (nter5a'e& on t*e MS &(%e
%n addition to the services described in this clause- the // entity and MM entity also provide services to 1M entities
which do not belon to the functional bloc"s of 11- !M!- and !!. (7or e'ample- the // entity provides service to
Group 1all and 0roadcast 1all entities.) These services are not further described in this clause.
9.1 Ser7('e& )ro7(%e% ,y t*e #a%(o #e&o$r'e Mana4e:ent ent(ty
The /adio /esource Manaement (//) sublayer provides a service to the Mobility Manaement entity (MM).
The // services are used forB
@ establishin control channel connectionsD
@ releasin control channel connectionsD
@ control@data transfer.
The /adio /esource Manaement services are represented by the //@service primitives.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ., "elease #
MS &(%e .etwork &(%e
Mo,(l(ty
Mana4e:ent
&$,layer
#a%(o #e&o$r'e
Mana4e:ent
&$,layer
##-)r(:(t(7e&
## &$,layer )eer-
to-)eer )roto'ol
##
S+P
0igure #',1 Ser3ices pro3ided at ""+S2P + MS side
9.1.1 Ser7('e &tate %(a4ra:
The primitives provided by the /adio /esource Manaement entity and the transition between permitted states are
shown in fiure ,.*.

+ L L
S T + T S
8 6 L
/ < .
P . 6
6 6 8 -
/ + T 6
# # - S T -
# A # # - U . 8 T - 6 + T + - 8 . 6
# # - + ; < # T - 8 . 6
# # - S T - 8 . 6
# # - # L - 8 . 6
# # - + ; < # T -
# A
# # - S T - / . -
# # - S > . / - 8 . 6
( ' ( ) * )
( r e & a & & )
( ' * a n n e l : o % e : o % ( 5 y )
# # - 6 + T + - # A - 8 . 6
# # - U . 8 T - 6 + T + - 8 . 6
0igure #'%1 Ser3ice graph of the "adio "esource Management + MS side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .% "elease #
9.1.2 Ser7('e )r(:(t(7e&
Table #',1 Primiti3es and parameters at the ""+S2P + MS side
P"8M8T8*:S P2"2M:T:"S ":0:":NC:
##CSTC#A Layer 3 :e&&a4e tran&5erre% (n t*e S+;M 5ra:e, /.
%o:a(n (%ent(ty
9.1.2.1
##CSTC8.6 - 9.1.2.2
##CSTC/.- - 9.1.2.3
##C#LC8.6 'a$&e 9.1.2.4
##CS>./C8.6 'a$&e ('()*er(n4, re&. a&&., '*annel :o%e :o%(5y), l(&t o5
(#+; 86, .+S Syn'*ron(Hat(on 8n%('ator, :a2(:$: %ata
rate)
9.1.2."
##C6+T+C#A Layer 3 :e&&a4e, lo'al 5low (%ent(5(er /. %o:a(n (%ent(ty 9.1.2.!
##C6+T+C8.6 Layer 3 :e&&a4e, /. %o:a(n (%ent(ty 9.1.2.7
##CU.8T 6+T+C8.6 Layer 3 :e&&a4e 9.1.2.E
##C+;<#TC#A 'a$&e 9.1.2.9
##C+;<#TC8.6 'a$&e 9.1.2.10
##C+/TC#A re&ele't(on :o%e 9.1.2.11
9.1.2.1 ##CSTC#A
%n .JGb mode it is used by the Mobility Manaement entity to re>uest establishment of a Mobile oriinated //
connection.
The re>uest shall be iven only in the %;52 state when the M! listens to the 111A and the previously selected 011A.
%n %u mode it is used by the Mobility Manaement entity to re>uest the establishment of a sinallin connection to the
1& domain type iven in the parameter 1& domain identity. The re>uest shall be iven only if no sinallin connection
to the specific 1& domain type is established.
9.1.2.2 ##CSTC8.6
%ndicates to the Mobility Manaement entity the establishment of a Mobile terminated // connection. 0y this
indication MM is informed that a transparent connection e'ists and // is in the dedicated mode.
9.1.2.3 ##CSTC/.-
%s used by // to indicate the successful completion of a Mobile oriinated // connection establishment. //
connection e'ists and // is in the dedicated mode.
9.1.2.4 ##C#LC8.6
%s used by // to indicate to the Mobility Manaement entity the release of a // connection when // has received a
1A.&&25 /252.!2 from the &etwor" and has triered a normal release of the data lin" layer. %t is also used to
indicate that a re>uested // connection cannot be established. %n both cases- // returns to %;52 mode.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .3 "elease #
9.1.2." ##CS>./C8.6
%s used for synchroni(in // and the Mobility Manaement entity after the establishment of a Mobile oriinated or
Mobile terminated // connection. This indication is provided to MM in the followin casesB
@ cipherin has been started (cipherin)D
@ interity protection has been started (interity) (3MT! only)D
@ a traffic channel has been assined (res. ass. S Hresource assinedH)D
@ the channel mode has been modified (channel mode modify).
%n %u mode- in case of a resource assinment or channel mode modification- // indicates to the Mobility Manaement
entity the list of /.0 %;s and- optionally-
N the &.! !ynchroni(ation %ndicators associated with the assined or modified radio bearersD or
N the ma'imum data rate (at /51 layer) associated with the assined or modified radio bearers- if no &.!
!ynchroni(ation %ndicator is available.
9.1.2."a Vo(%
9.1.2.", Vo(%
9.1.2.! ##C6+T+C#A
%s used by the Mobility Manaement entity to send control data to its peer entity on the &etwor" side via an e'istin //
connection.
9.1.2.7 ##C6+T+C8.6
%s used by // to indicate control@data- which has been received from its peer entity on the &etwor" side via an e'istin
// connection.
7or 3MT!- //Q;.T.Q%&; is also used to indicate whether control@data has beenB
- successfully interity chec"edD
- unsuccessfully interity chec"edD
- received with no interity protection.
9.1.2.7a Vo(%
9.1.2.E ##CU.8TC6+T+C8.6
%s used by // to provide MM with system info. The system info is received on the current 011A if // is in the %;52
state. %f a // connection has been established- the system info is received on the !.11A.
9.1.2.9 ##C+;<#TC#A
/e>uest to abort an e'istin // connection or a // connection in proress. The data lin"- if already established- shall
be released by a normal release procedure (;%!1J3.) initiated by the M!. This is the only way the M! can trier the
release of a // connection in case of e'ceptional conditions. The // returns to the %;52 state.
9.1.2.10 ##C+;<#TC8.6
%ndication that the // connection has been aborted by a lower layer failure and // has returned to the %;52 state.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .& "elease #
9.1.3 Ser7('e& )ro7(%e% ,y t*e #a%(o #e&o$r'e Mana4e:ent ent(ty 5or /TS
%nside the // sub@layer- the 1T! /adio /esource Manaement (1T!@//) sublayer provides services to the 1T!
Mobility Manaement (1T!@MM) entity.
The 1T!@// services are used forB
@ alive chec".
The 1T! /adio /esource Manaement services are represented by the 1T!@//@service primitives.
Table #','31 Primiti3es and parameters at the ""+S2P + MS side for CTS
P"8M8T8*:S P2"2M:T:"S ":0:":NC:
/TSC##C+L8VC/=/FC8.6 - 9.1.3.1
9.1.3.1 /TSC##C+L8VC/=/FC8.6
%ndicates to the 1T! Mobility Manaement entity that an alive chec" re>uest has been received from the fi'ed part.
9.2 Ser7('e& )ro7(%e% ,y t*e Mo,(l(ty Mana4e:ent ent(ty
The Mobility Manaement (MM) sublayer provides services to the 1all 1ontrol (11) entity- the !upplementary
!ervices !upport (!!) entity- the 5ocation !ervices (51!) entity (only for type . 5M3) and the !hort Messae !ervice
!upport (!M!) entity.
The Mobility Manaement services primitives are discriminated by the MM11- MM!!- MM51! and MM!M! prefi'.

// SS SMS // SS SMS
MM//-
S+P
MMSS-
S+P
MMSMS-
S+P
Mo,(l(ty :ana4e:ent
&$,layer
Mo,(l(ty :ana4e:ent
&$,layer
MM-)r(:(t(7e&
MM )eer-to-)eer
)roto'ol
MS-&(%e .etwork &(%e
.<T0 T*e L/S )roto'ol ent(t(e& 5or 'o::$n('at(on ,etween a ty)e + LMU an% t*e network wo$l% ,e (n'l$%e% (n
t*e 5(4$re (n t*e &a:e :anner a& t*e )roto'ol ent(t(e& 5or //, SS an% SMS.
0igure #'31 Ser3ices pro3ided at the MMCC+S2P4 MMSS+S2P4 MM9CS+S2P4 MMSMS+S2P + MS side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .- "elease #
9.2.1 Ser7('e &tate %(a4ra:
The primitives provided by the Mobility Manaement entity towards 1all 1ontrol- call independent !upplementary
!ervice !upport- 5ocation !ervices !upport for type . 5M3 and towards !hort Messaes !ervice !upport and the
transition between permitted states are illustrated in fiure ,.=.

86L
668-
/+T6
MMGG-U.8T-6+T+-8.6
MMGG-#L-
#A-8.6
MMGG-#ST-/.-
MMGG-#L-
#A38.6
MMGG-ST-#A
MMGG-ST-/.-
MM//-S>./-8.6
('*annel :o%e :o%(5y)
(re& a&&)
MMGG-6+T+-#A 8.6
MMGG-U.8T-6+T+-#A 8.6
MMGG-
P#<MPT-
8.6
MMGG-
P#<MPT-
#D
MMGG-
#L-
#A
MMSS-
ST-
8.6
MMGG-
#ST-
#A
MMGG-
##-
8.6
MMGG-U.8T-
6+T+-#A
/<..
P.6
/<..
SUSP
#-
ST-
P.6
.<T 10 MM//-)r(:(t(7e& only at MM//-S+P.
.<T 20 T*e )re5(2 MMGG (& $&e% 5or &$,&t(t$t(on o5 MM//, MMSS, MML/S or MMSMS.
0igure #'&1 Ser3ice graph of the Mobilit Management entit + MS side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .. "elease #
9.2.2 Ser7('e )r(:(t(7e&
Table #'%1 Primiti3es and Parameters at MMCC+S2P4 MMSS+S2P !for tpe 2 9MA$4 MM9CS+S2P or
MMSMS+S2P + MS side
P"8M8T8*:S P2"2M:T:"S ":0:":NC:
MMGGCSTC#A (&ee note 1) Para:eter& 5or t*e a))ro)r(ate
/M S#V8/ #AUST ((5 any)
9.2.2.1
MMGGCSTC8.6 (&ee note 1) -(r&t /M :e&&a4e 9.2.2.2
MMGGCSTC/.- (&ee note 1) - 9.2.2.3
MMGGC#LC#A (&ee note 1) 'a$&e 9.2.2.4
MMGGC#LC8.6 (&ee note 1) 'a$&e 9.2.2."
MMGGC6+T+C#A (&ee note 1) Layer 3 :e&&a4e 9.2.2.!
MMGGC6+T+C8.6 (&ee note 1) Layer 3 :e&&a4e 9.2.2.7
MMGGCU.8TC6+T+C#A (&ee note 1) Layer 3 :e&&a4e 9.2.2.E
MMGGCU.8TC6+T+C8.6 (&ee note 1) Layer 3 :e&&a4e 9.2.2.9
MM//CS>./C8.6 (&ee note 2) 'a$&e0 re&.a&&I l(&t o5 (#+; 86, .+S
Syn'*ron(Hat(on 8n%('ator, :a2(:$: %ata
rate)
9.2.2.10
MMGGC#STC#A (&ee note 1) 9.2.2.11
MMGGC#STC/.- (&ee note 1) 9.2.2.12
MMGGC##C8.6 (&ee note 1) 'a$&e 9.2.2.13
MMGGCP#<MPTC8.6 (&ee note 1) - 9.2.2.14
MMGGCP#<MPTC#D (&ee note 1) - 9.2.2.1"
.<T 10 MMGG (& $&e% a& &$,&t(t$t(on 5or MM//, MMSS, MML/S or MMSMS.
.<T 20 <nly at MM//-S+P.
9.2.2.1 MMGGCSTC#A
/e>uest used by 11- !!- 51! (for type . 5M3) and !M! respectively- to re>uest establishment of a MM connection.
!everal MM connections may be provided in parallel to the re>uestin entities. The primitive may contain parameters
which are relevant for the 1M !2/C%12 /2O32!T messae- e.. to distinuish a basic call from an emerency call.
9.2.2.2 MMGGCSTC8.6
%ndication to 11- !!- 51! (for type . 5M3) or !M! that a Mobile terminated MM connection has been established
and the first messae has been received from the respective peer entity. !everal MM connections may be provided in
parallel. %f a MM connection already e'ists- a new MM connection usin the same // connection is indicated by this
primitive if MM detects a messae with a new combination of Protocol ;iscriminator (P;) and Transaction
%dentifier (T%).
9.2.2.3 MMGGCSTC/.-
!uccessful confirmation of the MM connection establishment by the MM sublayer to be iven to the appropriate entity
which has re>uested the service.
9.2.2.4 MMGGC#LC#A
3sed by 11- !!- 51! (for type . 5M3) or !M! respectively- to re>uest release of the MM connection. The
correspondin P;JT% will be released and may be used for a new MM connection.
9.2.2." MMGGC#LC8.6
%ndication of the release of an e'istin MM connection or a MM connection in proress. This primitive is used in
e'ceptional cases to indicate that the MM connection cannot be established or "ept any loner and P;JT% have been
released.
9.2.2.! MMGGC6+T+C#A
/e>uest used by the 11- !! or !M! entities for ac"nowleded control@data transmission.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .) "elease #
9.2.2.7 MMGGC6+T+C8.6
%ndication used by MM to transfer the received ac"nowleded control@data to the 11- !!- 51! (for type . 5M3) or
!M! entities.
9.2.2.E MMGGCU.8TC6+T+C#A
/e>uest used by the 11- !!- 51! (for type . 5M3) or !M! entities for unac"nowleded control@data transmission.
9.2.2.9 MMGGCU.8TC6+T+C8.6
%ndication used by MM to transfer the received unac"nowleded control@data to the 11- !!- 51! or !M! entities.
9.2.2.10 MM//CS>./C8.6
%ndication that a dedicated channel assinment has been performed andJor the channel mode has been chaned (only
towards the 11 entity).
%n %u mode- MM indicates the list of the /.0 %;s and- optionally-
N the &.! !ynchroni(ation %ndicators associated with the assined or modified radio bearersD or
N the ma'imum data rate (at /51 layer) associated with the assined or modified radio bearers- if no &.!
!ynchroni(ation %ndicator is available.
;urin a networ"@initiated in@call modification the 11 entity uses the &.! !ynchroni(ation %ndicator or the ma'imum
data rate to determine whether a suitable channel for the new call mode is available.
9.2.2.11 MMGGC#STC#A
/e>uest to establish a MM connection which has been interrupted by a lower layer failure. The interruption must have
been indicated by MMMMQ2//Q%&;.
9.2.2.12 MMGGC#STC/.-
1onfirmation of the successful re@establishment of the MM connection. The MM connection will continue with P;JT%
as it had before.
9.2.2.13 MMGGC##C8.6
%ndication of a lower layer failure interruptin the MM connection. The P;JT% are still "ept by MM. %n case of parallel
transactions this indication is passed to all 1M entities for which a MM connection has been established. %t is left to the
decision of the appropriate 1M entity to either re>uest the re@establishment of the MM connection by
MMMMQ/22!TQ/2O or to release it by MMMMQ/25Q/2O.
9.2.2.14 MMGGCP#<MPTC8.6
%ndication iven by MM to inform of the completion of the MM connection to the 11- !!- 51! (for type . 5M3) or
!M! entities for a mobile station which supports H&etwor" %nitiated MO 1M 1onnection /e>uestH.
9.2.2.1" MMGGCP#<MPTC#D
/esponse to the MMMMQP/OMPTQ%&; indication to the MM entity in a mobile station which supports H&etwor"
%nitiated MO 1M 1onnection /e>uestH in case when it is impossible to establish the prompted 1M connection e.. due
to lac" of free transaction identifiers.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ./ "elease #
9.3 Ser7('e& )ro7(%e% ,y ra%(o re&o$r'e :ana4e:ent ent(ty 5or
GP#S &er7('e&
The service primitives for 3MT! are defined in the present document. The services provided by the .ccess !tratum
(.!) are specified in 3GPP T! *3.99+ F*+G.
9.3.1 Ser7('e )r(:(t(7e& 5or G##-S+P (GSM only)
The G//@!.P service primitives are defined in 3GPP T! ==.+:= F99aG
FFTable ,.3.9- and chapters ,.3.9.9 @ ,.3.9.8 are CoidG
9.3.2 Ser7('e )r(:(t(7e& 5or GMM##-S+P (GSM only)
Table #'3'%1 Primiti3es and Parameters at GMM""+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
GMM##-+SS8G.-#A newTLL8 9.3.2.1
GMM##-P+G-8.6 TLL8 9.3.2.2
9.3.2.1 GMM##-+SS8G.-#A
. new T55% is assined to the // sublayer.
9.3.2.2 GMM##-P+G-8.6
. //@pain messae has been received by the // sublayer.
9.3.3 Ser7('e )r(:(t(7e& 5or #+;M+S-S+P (UMTS only)
Table #'3'31 Primiti3es and parameters at "26M2S+S2P
P"8M8T8*: P2"2M:T:"
!message4 info elements of
message4 other parameters$
":0:":NC:
#+;M+S-#+;-ST+;L8S=-8.6 #+; 86 l(&t 9.3.3.1
#+;M+S-#+;-ST+;L8S=-#S - 9.3.3.2
#+;M+S-#+;-ST+;L8S=-#D 9.3.3.3
#+;M+S-#+;-#L+S-8.6 #+; 86 l(&t 9.3.3.4
#+;M+S-#+;-#L+S-#S - 9.3.3."
#+;M+S-ST+TUS-8.6 /a$&e 9.3.3.!
9.3.3.1 #+;M+S-#+;-ST+;L8S=-8.6
%ndication from the .ccess !tratum layer that radio access bearer setup for the indicated list of /.0 %;s (contains
&!.P%) has commenced.
9.3.3.2 #+;M+S-#+;-ST+;L8S=-#S
/esponse (to /.0M.!@/.0@2!T.05%!A@%&;) used by the /.0M entity to inform the .ccess !tratum sublayer that
the indicated &!.P% (in /.0 %;) is currently or has been activated by the !M.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ .# "elease #
9.3.3.3 #+;M+S-#+;-ST+;L8S=-#D
/esponse (to /.0M.!@/.0@2!T.05%!A@%&;) used by the /.0M entity to inform the .ccess !tratum sublayer that
all of the &!.P%s- indicated by /.0 %; list in the received /.0M.!@/.0@2!T.05%!A@%&;- have not been
activated by the !M@layer and the attempt to setup the radio access bearers shall be rejected.
9.3.3.4 #+;M+S-#+;-#L+S-8.6
%ndication from the .ccess !tratum layer that a radio access bearer for the indicated &!.P% has been released.
9.3.3." #+;M+S-#+;-#L+S-#S
/esponse used by the /.0M entity to inform the .ccess !tratum sublayer that the indicated /.0 %; has been released
in the /.0M.
9.3.3.! #+;M+S-ST+TUS-8.6
%ndication used by the .! sublayer to transfer failures to the /.0M.
9.3.4 Ser7('e )r(:(t(7e& 5or GMM+S-S+P (UMTS only)
Table #'3'&1 Ser3ice primiti3es and parameters at GMM2S+S2P + MS side
P"8M8T8*: P2"2M:T:"
!message4 info elements of message4
other parameters$
":0:":NC:
GMM+S-S/U#8T>-8.6 9.3.4.1
GMM+S-S/U#8T>-#S /F, 8F 9.3.4.2
GMM+S- ST+;L8S=-#A Layer 3-P6U, &ta,l(&*:ent 'a$&e,
Pr(or(ty, /. 6o:a(n 8%ent(ty, MS 8%ent(ty,
L+83#+8
9.3.4.3
GMM+S- ST+;L8S=-/.- 9.3.4.4
GMM+S- ST+;L8S=-#D 9.3.4."
GMM+S- #L+S-#A /. 6o:a(n (%ent(ty 9.3.4.!
GMM+S- #L+S-8.6 /a$&e 9.3.4.7
GMM+S- 6+T+-#A Layer 3-P6U, Pr(or(ty, /. 6o:a(n (%ent(ty 9.3.4.E
GMM+S- 6+T+-8.6 Layer 3-P6U 9.3.4.9
GMM+S-P+G-8.6 MS 8%ent(ty ty)e, Pa4(n4 /a$&e 9.3.4.10
GMM+S-ST+TUS-8.6 /a$&e 9.3.4.11
9.3.4.1 GMM+S-S/U#8T>-8.6
%ndication from the .! sublayer that cipherin (and interity protection) shall be started. The GMM sublayer uses this
primitive as an indication of the completion of the service re>uest procedure.
9.3.4.2 GMM+S-S/U#8T>-#S
1ipherin and interity "eys are assined to the .! sublayer to enable cipherin (and interity protection).
9.3.4.3 GMM+S-ST+;L8S=-#A
To establish a sinallin connection and to carry the initial 5ayer 3@P;3 over the radio interface.
9.3.4.4 GMM+S-ST+;L8S=-/.-
1onfirmation from the .! sublayer that a P! sinallin connection has been established.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )( "elease #
9.3.4." GMM+S-ST+;L8S=-#D
The attempt to establish a P! sinallin connection was rejected by the networ".
9.3.4.! GMM+S- #L+S-#A
/e>uest used by the MM@sublayer to re>uest the release of the P! sinallin connection.
9.3.4.7 GMM+S- #L+S-8.6
%ndication from the .! sublayer that the P! sinallin connection has been released.
9.3.4.E GMM+S- 6+T+-#A
/e>uest used by the MM@sublayer for transfer of data.
9.3.4.9 GMM+S- 6+T+-8.6
%ndication used by the .! sublayer to transfer received data to MM sublayer.
9.3.4.10 GMM+S-P+G-8.6
. pain messae has been received by the .! sublayer.
9.3.4.11 GMM+S-ST+TUS-8.6
%ndication used by the .! sublayer to transfer failures to the MM sublayer.
9.4 Ser7('e& )ro7(%e% ,y t*e LL/ ent(ty 5or GP#S &er7('e& (GSM
only)
This subclause is informative- the service primitives are defined in 3GPP T! ==.+:= F99aG. They are included here to
provide a complete overview of the radio interface protocol architecture.
9.4.1 Ser7('e )r(:(t(7e& 5or LLGMM-S+P
Table #'&',1 Primiti3es and parameters at 99GMM+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
LLGMM-+SS8G.-#A ol%TLL8, newTLL8, F', #+.6, /()*er(n4 +l4or(t*: 9.4.1.1
LLGMM-T#8GG#-#A /a$&e 9.4.1.2
LLGMM-SUSP.6-#A TLL8 9.4.1.4
LLGMM-#SUM-#A TLL8 9.4.1."
LL-U.8T6+T+-#A TLL8, GMM-P6U, )rote't, '()*er 9.4.1.E
LL-U.8T6+T+-8.6 TLL8, GMM-P6U, '()*er 9.4.1.9
LLGMM-ST+TUS-8.6 TLL8, 'a$&e 9.4.1.10
9.4.1.1 LLGMM-+SS8G.-#A
. new T55% andJor a cipherin "ey andJor a cipherin alorithm is assined to the 551 sublayer.
9.4.1.2 LLGMM-T#8GG#-#A
/e>uest to send an 551 P;3 to the networ". 1ause indicates if the primitive is sent to trier an implicit pae
response.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ), "elease #
9.4.1.3 Vo(%
9.4.1.4 LLGMM-SUSP.6-#A
.ll 551 lin"s in .0M mode will cease sendin P;3s. GMM messaes can still be sent and received.
9.4.1." Vo(%
9.4.1.! Vo(%
9.4.1.7 LLGMM-B8.6<B-/.-
The actual 551#s C(/)s for each 551 lin" in .0M mode are transferred to GMM.
9.4.1.E LL-U.8T6+T+-#A
/e>uest to send a GMM messae in unac"nowleded mode to the peer entity.
9.4.1.9 LL-U.8T6+T+-8.6
. GMM messae in unac"nowleded mode has been received from the peer entity.
9.4.1.10 LLGMM-ST+TUS-8.6
%ndication used by 551 to transfer 551 failures to the GMM sublayer. The failure may also be caused due to errors at
the /51JM.1 layer.
9.4.2 Ser7('e )r(:(t(7e& 5or LLSMS-S+P
Table #'&'%1 Ser3ice primiti3es and parameters at 99SMS+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er )ara:eter&)
":0:":NC:
LL-U.8T6+T+-#A TLL8, SMS-/P-P6U, )rote't, '()*er 9.4.2.1
LL-U.8T6+T+-8.6 TLL8, SMS-/P-P6U, 9.4.2.2
9.4.2.1 LL-U.8T6+T+-#A
.n 551 3% frame will be sent to the peer entity.
9.4.2.2 LL-U.8T6+T+-8.6
.n 551 3% frame has been received from the peer entity.
9." Ser7('e& )ro7(%e% ,y t*e GMM 5or GP#S &er7('e&
The GP/! Mobility Manaement (GMM) sublayer provides services to the !ession Manaement (!M) entity-
!upplementary !ervice (!!) entity and the !hort Messae !ervice !upport (G!M!) entity for messae transfer.
9.".1 Ser7('e )r(:(t(7e& 5or GMMSM-S+P
!ession Manaement services may re>uest GP/! service reistration or perform procedures needed to activate a
multicast service before activatin a P;P or an M0M! conte't.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )% "elease #
Table #'-',1 Primiti3es and parameters at GMMSM+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMMSM-ST+;L8S=-#A - 9.".1.1
GMMSM-ST+;L8S=-/.- - 9.".1.2
GMMSM-ST+;L8S=-#D 'a$&e 9.".1.3
GMMSM-#L+S-8.6 - 9.".1.4
GMMSM-U.8T6+T+-#A SM-P6U 9.".1."
GMMSM-U.8T6+T+-8.6 SM-P6U 9.".1.!
9.".1.1 GMMSM-ST+;L8S=-#A
/e>uest from !ession Manaement to send an .TT.1A /2O32!T messae to the networ" to setup a GMM
connection. The re>uest is only performed in case the M! is not already attached. The GP/! attach is then indirectly
caused by a re>uest from !ession Manaement- e.. a re>uested P;P conte't activation or M0M! conte't activation.
9.".1.2 GMMSM-ST+;L8S=-/.-
The networ" has send the .TT.1A .112PT messae to the M!- the indirect attach was successful. &ow- !ession
Manaement can proceed with the !ession Manaement re>uest- e.. the P;P conte't activation or the M0M! conte't
activation..
9.".1.3 GMMSM-ST+;L8S=-#D
The networ" has rejected the attach. The M! has received the .TT.1A /2R21T messae.
9.".1.4 GMMSM-#L+S-8.6
The GP/! Mobility Manaement informs the !ession Manaement that the M! has been GP/! detached- e.. by timer
e'piry- and therefore- the P;P conte't(s) and the M0M! conte't(s)- if any- are not valid anymore.
9.".1." GMMSM-U.8T6+T+-#A
The GMM is re>uested to forward a !M P;3 to 551 in order to send it in unac"nowleded more to the peer entity.
9.".1.! GMMSM-U.8T6+T+-8.6
The GMM forwards a !M P;3- which has been received in unac"nowleded mode via 551 from the peer entity.
9.".2 Vo(%
9.".3 Ser7('e )r(:(t(7e& 5or GMMSMS-S+P
The !hort Messae entity may re>uest from the GMM entity the GMM %M!% reistration state before an MO !M!
transmission is initiated.
Table #'-'31 Primiti3es and parameters at GMMSMS+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMMSMS-#G-ST+T-#A - 9.".3.1
GMMSM- #G-ST+T -#SP #e4(&trat(on &tate 9.".3.2
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )3 "elease #
9.".3.1 GMMSMS-#G-ST+T-#A
/e>uest for the current %M!% reistration state from the !hort Messae entity.
9.".3.2 GMMSM- #G-ST+T -#SP
The current %M!% reistration state is sent to the !hort Messae entity.
9.".4 Ser7('e )r(:(t(7e& 5or PMMSMS-S+P
Table #'-'&1 Primiti3es and Parameters at PMMSMS+S2P + MS side
P"8M8T8*:S P2"2M:T:"S
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
PMMSMSCSTC#A Mo,(le-86 9.".4.1
PMMSMSCSTC/.- - 9.".4.2
PMMSMSC##<#C8.6 /a$&e 9.".4.3
PMMSMSCU.8T6+T+C#A SMS-P6U 9.".4.4
PMMSMSCU.8T6+T+C8.6 SMS-P6U 9.".4."
9.".4.1 PMMSMSCST C#A
The GMM is re>uested to establish a P! sinallin conection.
9.".4.2 PMMSMSCST C/.-
The GMM indicates a P! sinallin connection is established.
9.".4.3 PMMSMSC##<#C8.6
The GMM indicates that a P! sinallin connection has been released.
9.".4.4 PMMSMSCU.8T6+T+C#A
The GMM is re>uested to forward a !M! P;3 in order to send it to the peer entity.
9.".4." PMMSMSCU.8T6+T+C8.6
%ndication used by GMM to transfer the received data to the G!M! entities.
9."." Ser7('e )r(:(t(7e& 5or GMM#+;M-S+P (UMTS only)
Table #'-'-1 Ser3ice primiti3es and parameters at GMM"26M+S2P = MS side
P"8M8T8*: P2"2M:T:"
!message4 info elements of
message4 other parameters$
":0:":NC:
GMM#+;M-#ST+;L8S=-#A 9.".".1
GMM#+;M-#ST+;L8S=-#SP 9.".".2
GMM#+;M-#ST+;L8S=-#D /a$&e 9.".".3
&OT2B 1onfirmation to the /.0MGMM@/22!T.05%!A@/2O is iven to the /.0M in the form of indications
from the .! sublayer that establishment of /.0s has commenced or been completed.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )& "elease #
9.".".1 GMM#+;M-#ST+;L8S=-#A
This primitive is used by the /.0M entity to inform the GMM sublayer that 35 user data has been received for an
&!.P% without an active /.0. GMM shall initiate a service re>uest procedure to re@establish the /.0 for the
&!.P%(!).
9.".".2 GMM#+;M-#ST+;L8S=-#SP
This primitive is used by the GMM sublayer to inform the /.0M entity that the reception of the !ervice /e>uest
messae has been ac"nowleded by the networ".
9.".".3 GMM#+;M-#ST+;L8S=-#D
This primitive is used by the GMM sublayer to inform the /.0M entity that the re@establishment of /.0s by the
service re>uest procedure has failed.
9.".! Ser7('e )r(:(t(7e& 5or GMMSS-S+P
!upplementary !ervices may re>uest GP/! service reistration before sendin !! P;3.
Table #'-'.1 Primiti3es and parameters at GMMSS+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMMSS-ST+;L8S=-#A - 9.".!.1
GMMSS-ST+;L8S=-/.- - 9.".!.2
GMMSS-ST+;L8S=-#D 'a$&e 9.".!.3
GMMSS-#L+S-8.6 - 9.".!.4
GMMSS-U.8T6+T+-#A SS-P6U 9.".!."
GMMSS-U.8T6+T+-8.6 SS-P6U 9.".!.!
9.".!.1 GMMSS-ST+;L8S=-#A
/e>uest from !upplementary !ervices to send an .TT.1A /2O32!T messae to the networ" to setup a GMM
connection. The re>uest is only performed in case the M! is not already attached. The GP/! attach is then indirectly
caused by a sendin of !! P;3.
9.".!.2 GMMSS-ST+;L8S=-/.-
The networ" has send the .TT.1A .112PT messae to the M!- the indirect attach was successful. &ow
!upplementary !ervices can proceed with sendin !! P;3.
9.".!.3 GMMSS-ST+;L8S=-#D
The networ" has rejected the attach. The M! has received the .TT.1A /2R21T messae.
9.".!.4 GMMSS-#L+S-8.6
The GP/! mobility manaement informs the !upplementary !ervices that the M! has been GP/! detached- e.. by
timer e'piry.
9.".!." GMMSS-U.8T6+T+-#A
The GMM is re>uested to forward a !! P;3 to lower layer in order to send it to the peer entity.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )- "elease #
9.".!.! GMMSS-U.8T6+T+-8.6
The GMM forwards a !! P;3- which has been received from the peer entity.
9.".7 Ser7('e )r(:(t(7e& 5or GMMSS2-S+P
The !upplementary !ervice entity may re>uest to the MM andJor GMM entity the MM andJor GMM %M!% reistration
state before an !! P;3 transmission is initiated from the mobile station.
Table #'-')1 Primiti3es and parameters at GMMSS%+S2P + MS side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMMSS2-#G-ST+T-#A - 9.".7.1
GMMSS2- #G-ST+T -#SP #e4(&trat(on &tate 9.".7.2
9.".7.1 GMMSS2-#G-ST+T-#A
/e>uest for the current %M!% reistration state from the !upplementary !ervices entity.
9.".7.2 GMM SS2- #G-ST+T -#SP
The current %M!% reistration state is sent to the !upplementary !ervices entity.
10 8nterlayer &er7('e (nter5a'e& on t*e .etwork &(%e
%n addition to the services described in this clause- the // entity and MM entity also provide services to 1M entities
which do not belon to the functional bloc"s of 11- !M!- and !!. (7or e'ample- the // entity provides service to
Group 1all 1ontrol and 0roadcast 1all 1ontrol entities.) These services are not further described in this clause.
10.1 Ser7('e& )ro7(%e% ,y t*e #a%(o #e&o$r'e Mana4e:ent ent(ty
The /adio /esource Manaement (//) sublayer provides services to the Mobility Manaement entity (MM).
The // services are used forB
@ establishin control channel connectionsD
@ establishin traffic channel connectionsD
@ cipherin mode indicationD
@ releasin control channel connectionsD
@ control@data transfer.
The /adio /esource Manaement services are represented by the // service primitives.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ). "elease #
MS &(%e
.etwork &(%e
Mo,(l(ty
Mana4e:ent
&$,layer
##-
S+P
##-)r(:(t(7e&
## &$,layer )eer-
to-)eer )roto'ol
#a%(o #e&o$r'e
Mana4e:ent
&$,layer
0igure ,(',1 Ser3ices pro3ided at ""+S2P + Network side
10.1.1 Ser7('e &tate %(a4ra:
The primitives provided by the /adio /esource Manaement entity and the transition between permitted states are
shown in fiure 9+.*.

# # - U . 8 T - 6 + T + - # A
# # - # L - # A 8 . 6
# # - # L - # A 8 . 6
# # - + ; < # T - # A 8 . 6
# # - S T - 8 . 6
# # - S > . / - / . -
. o t e 1
# # - S T - # A
# # - # L - # A 8 . 6
# # - + ; < U # T - # A 8 . 6
# # - U . 8 T -
6 + T + - # A
# # - S T - / . -
8 6 L
/ < .
P . 6
# # - S > . / - # A
( r e & a & & )
( ' ( ) * )
( ' * a n n e l : o % e : o % ( 5 y )
# # - 6 + T + - # A 8 . 6
# # - U . 8 T - 6 + T + - # A 8 . 6
# # - 6 + T + - # A 8 . 6

# # - U . 8 T - 6 + T + - # A 8 . 6
ST+TS0
86L0 - .o %e%('ate% '*annel e&ta,l(&*e%.
/<.P.60 - /onne't(on )en%(n4.
6T10 - 6ata tran&5er 1, %e%('ate% '*annel e&ta,l(&*e%.
6T20 - 6ata tran&5er 2, %e%('ate% '*annel e&ta,l(&*e%, '()*er(n4 :o%e &et.
0igure ,('%1 Ser3ice graph of the "adio "esource Management entit + Network side
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )) "elease #
10.1.2 Ser7('e )r(:(t(7e&
Table ,(',1 Primiti3es and Parameters at the ""+S2P + Network side
P"8M8T8*:S P2"2M:T:"S ":0:":NC:
##CSTC#A Para:eter& 5or t*e 8n(t(al layer 3 :e&&a4e 10.1.2.1
##CSTC8.6 8n(t(al layer 3 :e&&a4e 10.1.2.2
##CSTC/.- - 10.1.2.3
##C#LC#A 'a$&e 10.1.2.4
##C#LC8.6 'a$&e 10.1.2."
##CS>./C#A 'a$&e (re&o$r'e a&&(4n, '()*er(n4, '*annel
:o%e :o%(5y), l(&t o5 (#+; 86, .+S
Syn'*ron(Hat(on 8n%('ator)
10.1.2.!
##CS>./C/.- 'a$&e (re&o$r'e a&&(4n, '()*er(n4) 10.1.2.7
##C6+T+C#A Layer 3 :e&&a4e 10.1.2.E
##C6+T+C8.6 Layer 3 :e&&a4e 10.1.2.9
##CU.8TC6+T+C#A Layer 3 :e&&a4e 10.1.2.10
##CU.8TC6+T+C8.6 Layer 3 :e&&a4e 10.1.2.11
##C+;<#TC#A 'a$&e 10.1.2.12
##C+;<#TC8.6 'a$&e 10.1.2.13
10.1.2.1 ##CSTC#A
/e>uest used by the Mobility Manaement entity to re>uest establishment of control channel connections.
10.1.2.2 ##CSTC8.6
%ndication to the Mobility Manaement entity that the establishment of control channel connections has been done.
10.1.2.3 ##CSTC/.-
1onfirmation used by // to confirm the establishment of a re>uested control channel connection.
10.1.2.4 ##C#LC#A
/e>uest used by the Mobility Manaement to release a control channel connection.
10.1.2." ##C#LC8.6
%ndication from // to MM that the main sinallin lin" has been released.
10.1.2.! ##CS>./C#A
/e>uest used by the Mobility Manaement entity for synchroni(ation with the // protocol.
%n %u mode- in case of resource assinment or channel mode modification- Mobility Manaement includes the list of the
/.0 %;s and- optionally- the &.! !ynchroni(ation %ndicators associated with the radio bearers to be assined or
modified.
10.1.2.7 ##CS>./C/.-
1onfirmation used by // that the re>uested synchroni(ation is done.
10.1.2.E ##C6+T+C#A
/e>uest used by the Mobility Manaement entity for ac"nowleded control@data transmission.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )/ "elease #
10.1.2.9 ##C6+T+C8.6
%ndication used by // to transfer received control@data- which should be ac"nowleded- to the Mobility Manaement
entity.
10.1.2.10 ##CU.8TC6+T+C#A
/e>uest used by the Mobility Manaement entity for unac"nowleded control@data transmission.
10.1.2.11 ##CU.8TC6+T+C8.6
%ndication used by // to transfer received control@data- which should not be ac"nowleded- to the Mobility
Manaement entity.
10.1.2.12 ##C+;<#TC#A
/e>uest of the abandon of the // connection.
10.1.2.13 ##C+;<#TC8.6
%ndication that a radio lin" failure has occurred.
10.2 Ser7('e& )ro7(%e% ,y t*e Mo,(l(ty Mana4e:ent ent(ty
The Mobility Manaement (MM) sublayer provides services to the 1all 1ontrol (11) entity- the !upplementary !ervice
!upport (!!) entity- the 5ocation !ervices (51!) (for type . 5M3) and the !hort Messae !ervice !upport (!M!)
entity.
The Mobility Manaement services primitives are reconi(ed by the MM11- MM!!- MM51! and MM!M! prefi'.

/ / S S S M S / / S S S M S
M M / / -
S + P
M M S S -
S + P
M M S M S -
S + P
M o , ( l ( t y : a n a 4 e : e n t
& $ , l a y e r
M o , ( l ( t y : a n a 4 e : e n t
& $ , l a y e r
M M - ) r ( : ( t ( 7 e &
M M ) e e r - t o - ) e e r
) r o t o ' o l
M S - & ( % e . e t w o r k & ( % e
.<T0 T*e L/S )roto'ol ent(t(e& 5or 'o::$n('at(on ,etween a ty)e + LMU an% t*e network wo$l% ,e (n'l$%e% (n
t*e 5(4$re (n t*e &a:e :anner a& t*e )roto'ol ent(t(e& 5or //, SS an% SMS.
0igure ,('31 Ser3ices pro3ided at MMCC+S2P4 MMSS+S2P4 MM9CS+S2P4 MMSMS+S2P + Network side
10.2.1 Ser7('e &tate %(a4ra:
The primitives provided by the Mobility Manaement entity towards 1all 1ontrol- !hort Messaes !ervice !upport-
5ocation !ervices !upport (for a type . 5M3) and call independent !upplementary !ervices !upport as well as the
transition between permitted states are illustrated in fiure 9+.=.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ )# "elease #
8 6 L
/ < .
P . 6
M M G G - U . 8 T - 6 + T + - # A
M M / / - # L - # A 8 . 6
M M G G - S T - # A
M M G G - # L - # A 8 . 6
M M G G - S T - 8 . 6
M M / / - S > . / - # A
( r e & a & & )
( ' * a n n e l : o % e : o % ( 5 y )
M M G G - 6 + T + - # A 8 . 6
M M G G - U . 8 T - 6 + T + - # A 8 . 6
M M / / - 6 + T + - # A 8 . 6
M M / / - U . 8 T - 6 + T + - # A 8 . 6
M M G G - S T - / . -
M M G G - U . 8 T -
6 + T + - # A
6 T
1
M M / / - S > . / - / . -
. o t e 1
6 T
2
.<T 10 t*e )ara:eter& (n ##CS>./C/.- :$&t 'orre&)on% to t*e )ara:eter (n ##CS>./C#A.
.<T 20 MM//-)r(:(t(7e& only at MM//-S+P.
.<T 30 T*e )re5(2 MMGG (& $&e% 5or &$,&t(t$t(on o5 MM//, MMSS, MML/S (5or ty)e + LMU) or MMSMS.
0igure ,('&1 Ser3ice graph of the Mobilit Management entit4 towards Call Control + Network side
10.2.2 Ser7('e )r(:(t(7e&
Table ,('%1 Primiti3es and Parameters at MMCC+S2P4 MMSS+S2P4 MM9CS+S2P4 MMSMS+S2P +
Network side
P"8M8T8*:S P2"2M:T:"S ":0:":NC:
MMGGCSTC#A (&ee note 1) Mo,(le 86 10.2.2.1
MMGGCSTC8.6 (&ee note 1) -(r&t /M :e&&a4e 10.2.2.2
MMGGCSTC/.- (&ee note 1) - 10.2.2.3
MMGGC#LC#A (&ee note 1) 'a$&e 10.2.2.4
MMGGC#LC8.6 (&ee note 1) 'a$&e 10.2.2."
MMGGC6+T+C#A (&ee note 1) Layer 3 :e&&a4e 10.2.2.!
MMGGC6+T+C8.6 (&ee note 1) Layer 3 :e&&a4e 10.2.2.7
MMGGCU.8TC6+T+C#A (&ee note 1) Layer 3 :e&&a4e 10.2.2.E
MMGGCU.8TC6+T+C8.6 (&ee note 1) Layer 3 :e&&a4e 10.2.2.9
MM//CS>./C#A (&ee note 2) 'a$&e (re&o$r'e a&&(4n), l(&t o5
(#+; 86, .+S Syn'*ron(Hat(on
8n%('ator)
10.2.2.10
MM//CS>./C/.- (&ee note 2) 'a$&e (re&o$r'e a&&(4n) 10.2.2.11
.<T 10 MMGG (& $&e% a& &$,&t(t$t(on 5or MM//, MMSS, MML/S (5or ty)e + LMU) or MMSMS.
.<T 20 <nly at MM//-S+P.
10.2.2.1 MMGGCSTC#A
/e>uest by 11- !!- 51! (for type . 5M3) and !M! respectively- for the establishment of a MM connection.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /( "elease #
10.2.2.2 MMGGCSTC8.6
%ndication by the MM sublayer that a MM connection is established.
10.2.2.3 MMGGCSTC/.-
1onfirmation of the MM connection establishment by the MM sublayer.
10.2.2.4 MMGGC#LC#A
/e>uest by 11- !!- 51! (for type . 5M3) or !M! respectively- for the release of the MM connection.
10.2.2." MMGGC#LC8.6
%ndication by the MM sublayer that a MM connection has been released.
10.2.2.! MMGGC6+T+C#A
/e>uest by the 11- !!- 51! (for type . 5M3) or !M! entities for ac"nowleded control@data transmission.
10.2.2.7 MMGGC6+T+C8.6
%ndication used by MM to transfer the received ac"nowleded control@data to the 11- !!- 51! (for type . 5M3) or
!M! entities.
10.2.2.E MMGGCU.8TC6+T+C#A
/e>uest used by the 11- !!- 51! (for type . 5M3) or !M! entities for unac"nowleded control@data transmission.
10.2.2.9 MMGGCU.8TC6+T+C8.6
%ndication used by MM to transfer the received unac"nowleded control@data to the 11- !!- 51! (for type . 5M3) or
!M! entities.
10.2.2.10 MM//CS>./C#A
/e>uest used by the 11 entity to synchroni(e with the MM entity (resource assin).
%n %u mode- the 11 entity includes the list of the /.0 %;s and- optionally- the &.! !ynchroni(ation %ndicators
associated with the re>uested radio bearers.
10.2.2.11 MM//CS>./C/.-
1onfirmation used by the MM to inform the 11 entity that synchroni(ation is completed (resource assin).
10.3 Ser7('e& )ro7(%e% ,y ra%(o re&o$r'e :ana4e:ent ent(ty 5or
GP#S &er7('e&
10.3.1 Ser7('e )r(:(t(7e& 5or G##-S+P
The G//@!.P service primitives are defined in 3GPP T! ==.+:= F99aG
FTable 9+.3.9- and chapters 9+.3.9.9 @ 9+.3.9.8 are CoidG
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /, "elease #
10.3.2 Ser7('e )r(:(t(7e& 5or GMM##-S+P
Table ,('3'%1 Primiti3es and Parameters at GMM""+S2P + network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMM##-P+G-#A TLL8, 8MS8, /8 or /8-l(&t or #+8, )r(or(ty 10.3.2.1
10.3.2.1 GMM##-P+G-#A
/e>uest by GMM to send a //@pain messae to the mobile station.
10.4 Ser7('e& )ro7(%e% ,y t*e LL/ ent(ty 5or GP#S &er7('e&
10.4.1 Ser7('e )r(:(t(7e& 5or LLGMM-S+P
Table ,('&',1 Primiti3es and Parameters at G""+S2P + network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
LLGMM-+SS8G.-#A newTLL8, ol%TLL8, F', +l4or(t*: 10.4.1.1
LLGMM-SUSP.6-#A TLL8, )a4e 10.4.1.3
LLGMM-#SUM-#A TLL8 10.4.1.4
LLGMM-P+G-8.6 TLL8 10.4.1."
LLGMM-P+G-#SP-8.6 TLL8 10.4.1.!
LL-U.8T6+T+-#A TLL8, SMM-P6U, )rote't, '()*er 10.4.1.9
LL-U.8T6+T+-8.6 TLL8, SMM-P6U, '()*er 10.4.1.10
LLGMM-ST+TUS-8.6 TLL8, 'a$&e 10.4.1.11
10.4.1.1 LLGMM-+SS8G.-#A
. new T55% andJor a cipherin "ey andJor a cipherin alorithm is assined to the 55 sublayer. .lso an old T55% can
be unassined.
10.4.1.2 Vo(%
10.4.1.3 LLGMM-SUSP.6-#A
.ll 551 lin"s will cease sendin P;3s. The parameter pae indicates that data shall be sent if available and therefore
pain shall be needed. Or the cause indicates that data shall not be sent until a /2!3M2@/2O is received.
10.4.1.4 LLGMM-#SUM-#A
&ormal 551 frame sendin and reception is possible aain.
10.4.1." Vo(%
10.4.1.! Vo(%
10.4.1.7 LLGMM-P+G-8.6
/e>uires to send a pain messae to the mobile station.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /% "elease #
10.4.1.E LLGMM-P+G-#SP-8.6
. pain response has been received from the mobile.
10.4.1.9 LL-U.8T6+T+-#A
/e>uest to send a !MM messae in unac"nowleded mode to the peer entity.
10.4.1.10 LL-U.8T6+T+-8.6
. !MM messae in unac"nowleded mode has been received from the peer entity.
10.4.1.11 LLGMM-ST+TUS-8.6
%ndication used by 551 to transfer lower layer failures to the GMM sublayer.
10.4.2 Ser7('e )r(:(t(7e& 5or LLSMS-S+P
Table ,('&'%1 Primiti3es and Parameters at 99SMS+S2P + network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
LL-U.8T6+T+-#A TLL8, SMS-/P-P6U, )rote't, '()*er 10.4.2.1
LL-U.8T6+T+-8.6 TLL8, SMS-/P-P6U 10.4.2.2
10.4.2.1 LL-U.8T6+T+-#A
.n 551 3% frame will be sent to the peer entity.
10.4.2.2 LL-U.8T6+T+-8.6
.n 551 3% frame has been received from the peer entity.
10." Ser7('e& )ro7(%e% ,y t*e GMM 5or GP#S &er7('e&
The GP/! Mobility Manaement (GMM) sublayer provides services to the !ession Manaement (!M) entity and the
!hort Messae !ervice !upport (!M!) entity for messae transfer.
10.".1 Ser7('e )r(:(t(7e& 5or GMMSM-S+P
Table ,('-',1 Primiti3es and Parameters at GMMSM+S2P + network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMMSM-#L+S-8.6 - 10.".1.1
GMMSM-U.8T6+T+-#A SM-P6U 10.".1.2
GMMSM-U.8T6+T+-8.6 SM-P6U 10.".1.3
10.".1.1 GMMSM-#L+S-8.6
The GP/! mobility manaement informs the session manaement that the M! has been GP/! detached- e.. by timer
e'piry- and therefore the P;P conte'ts are not valid anymore.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /3 "elease #
10.".1.2 GMMSM-U.8T6+T+-#A
The GMM is re>uested to forward a !M P;3 to 551 in order to send it in unac"nowleded more to the peer entity.
10.".1.3 GMMSM-U.8T6+T+-8.6
The GMM forwards a !M P;3- which has been received in unac"nowleded mode via 551 from the peer entity.
10.".2 Ser7('e )r(:(t(7e& 5or PMMSMS-S+P
Table ,('-'%1 Primiti3es and Parameters at PMMSMS+S2P + Network side
P"8M8T8*:S P2"2M:T:"S
(:e&&a4e, (n5o ele:ent& o5
:e&&a4e, ot*er )ara:eter&)
":0:":NC:
PMMSMSC#LC#A - 10.".2.1
PMMSMSC##<# C8.6 'a$&e 10.".2.2
PMMSMSCU.8T6+T+C#A SMS-P6U 10.".2.3
PMMSMSCU.8T6+T+C8.6 SMS-P6U 10.".2.4
10.".2.1 PMMSMSC#LC#A
The GMM is re>uested to release of a P! sinallin connection.
10.".2.2 PMMSMSC##<#C8.6
The GMM indicates that a P! sinallin connection has been released.
10.".2.3 PMMSMSCU.8T6+T+C#A
The GMM is re>uested to forward a !M! P;3 in order to send to the peer entity.
10.".2.4 PMMSMSCU.8T6+T+C8.6
%ndication used by GMM to transfer the received data to the G!M! entities.
10.".3 Ser7('e )r(:(t(7e& 5or GMMSS-S+P
Table ,('-'31 Primiti3es and Parameters at GMMSS+S2P + network side
P"8M8T8*: P2"2M:T:"
(:e&&a4e, (n5o ele:ent& o5 :e&&a4e, ot*er
)ara:eter&)
":0:":NC:
GMMSS-#L+S-8.6 - 10.".3.1
GMMSS-U.8T6+T+-#A SS-P6U 10.".3.2
GMMSS-U.8T6+T+-8.6 SS-P6U 10.".3.3
10.".3.1 GMMSS-#L+S-8.6
The GP/! mobility manaement informs the !upplementary service that the M! has been GP/! detached- e.. by
timer e'piry.
10.".3.2 GMMSS-U.8T6+T+-#A
The GMM is re>uested to forward a !! P;3 to lower layer in order to send it to the peer entity.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /& "elease #
10.".3.3 GMMSS-U.8T6+T+-8.6
The GMM forwards a !! P;3- which has been received from the peer entity.
10.! Ser7('e& )ro7(%e% ,y t*e #a%(o #e&o$r'e Mana4e:ent ent(ty
5or /TS on t*e 5(2e% )art
%n addition to services described in subclause 9+.9- the 1T! /adio /esource Manaement (1T!@//) inside the //
sublayer provides services to the 1T! Mobility Manaement entity (1T!@MM).
The 1T!@// services are used forB
@ alive chec"D
@ huntinD
@ roup alertin.
The 1T! /adio /esource Manaement services are represented by the 1T!@// service primitives.
10.!.1 Ser7('e )r(:(t(7e&
Table ,('.1 Primiti3es and Parameters at the ""+S2P = 0i?ed part side
P"8M8T8*:S P2"2M:T:"S ":0:":NC:
##C/TSC+L8VC/=/FC#A /TSMS8 10.!.1.1
##C /TSC+L8VC/=/FC8.6 /a$&e 10.!.1.2
##C /TSC=U.T8.GC#A - 10.!.1.3
##C /TSCG#<UPC+L#T8.GC#A /TSMS8, %(&)lay 10.!.1.4
10.!.1.1 ##C /TSC+L8VC/=/FC#A
/e>uest used by the 1T! Mobility Manaement entity to re>uest an alive chec".
10.!.1.2 ##C /TSC+L8VC/=/FC8.6
%ndication to the 1T! Mobility Manaement entity on the results of the alive chec".
10.!.1.3 ##C /TSC=U.T8.GC#A
/e>uest to hunt the mobiles.
10.!.1.4 ##C /TSCG#<UPC+L#T8.GC#A
/e>uest to alert a roup of mobiles.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /- "elease #
11 L3 Me&&a4e&
This clause specifies the eneric methods used in the layer 3 protocol specifications to describe messaes. %t define in
particular a eneric messae structure- that of the Hstandard 53 messaesH. &ot all messaes in layer 3 protocols follow
this structure- but many do- and this clause specifies how to interpret the standard description.
This clause also addresses basic aspects of the handlin of messaes received but not compliant with the allowed
structure. %n most cases- only the conditions that lead to the dianosis of an error are described. The reaction of an entity
receivin a messae leadin to such a dianosis is in eneral specified for each protocol in the relevant protocol
specification.
11.1 General
11.1.1 Me&&a4e&
7or all concerned protocols- concrete messaes are bit strins of variable lenth- formally a succession of a finite-
possibly null- number of bits (i.e.- elements of the set TH+H- H9HU)- with a beinnin and an end.
The services provided by lower layers includes the transmission of such bit strins.
1onsidered as messaes- these bit strins follow some structure (the synta')- enablin to orani(e bits in information
pieces of a different meanin level.
The term message is used as well for a concrete messae (i.e.- a bit@strin- as defined by the ivin of all its bits- in
practice appearin at one point of time in a concrete dialo)- as for a class of concrete messaes sharin a common
structure. . concrete messae is an instance of the correspondin class of messaes. Messae classes can be described
as sets of potential bit strins- and of a common structure- enablin in particular to identify parts meaninful for the co@
operation functions the protocol supports.
%n eneral- in the rest of the clause as in the protocol specifications- the term message will be used to refer to the class. %t
may be used- when the conte't prevents ambiuity- to refer to a messae instance (e..- a received is usually a messae
instance). %n the rest of this clause- the term message instance will be used when needed to refer unambiuously to
specific concrete messae- i.e. to a specific bit strin.
. messae (messae class) can be described directly as a set of bit strins- usin the formal notation described in
.nne' 0.
. messae can also be described as a standard 53 messae- in which case the interpretation of the messae description
in term of a set of bit strins is specified in the ne't sub@clauses.
%n all cases- structurin messaes is based on the underlyin bit strin. Thus- the followin terms are usedB
@ a part of a messae instance is a sub@strin of the correspondin strinD a part of a messae (as a class) is
described by a definition applicable to all instancesD a part of a messae then is both a structural attribute of the
messae as a class- and a set of sub@strins- composed of the sub@strins obtained by applyin the definition to
each possible instanceD for instance- V the first octet W of a messae instance is defined from the moment its
lenth is reater than <- and is the sub@strin composed of the first < bits of the messae instanceD the V first
octet W of a messae as a class is the structural definition iven above- and the set of all <@bit octet strins that
can be obtained as the first octet of one instance of the classD
@ Hpart . follows part 0H means that in the messae the sub@strin correspondin to part 0 is concatenated with the
sub@strin of part 0D
@ the length of a messae instance- or of part of messae instance- is the number of bits of the correspondin sub
strinD riorously spea"in- a messae as a class (or a part seen as a class) has a lenth only if all the
correspondin instances have the same lenthD by e'tension- sentences such as V a messae as a lenth in the
rane so and so W means that the lenth of an instances of the class always fall in the rane.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /. "elease #
11.1.2 <'tet&
%n many places- a messae is described as a succession of octets. .n octet is enerally a succession of < bits. 3nless
otherwise indicated- the term octet is used more restrictively to refer to a part of messae- defined when considerin a
messae as a succession of octets- e..- the first < bits of a messae- or the 9?
th
to the *3
rd
- form an octet- but not the
second bit to the ,
th
.
3nless specified otherwise- the numberin conventions are the followinB
@ Octets in a messae or in a part are numbered from 9 onward- startin at the beinnin of the bit strin. This
numberin can be strictly applied only for messae instances- and for the first part of a messae structurally
identical for all instances.
@ 0its in octets are numbered from < down to 9- startin at the beinnin of the octet.
@ Khen represented as tables showin the different bit positions- octets are presented in the natural occidental
order- i.e.- from the top of a pae downward. 0its in octets are presented with the first bit on the left of the pae.
11.1.3 8nte4er
%n many places- messae parts are described as encodin inteers. Two eneric encodin are defined in this subclause.
11.1.3.1 ;(nary
. messae part is said to encode in binary an inteer to indicate that concrete strins are mapped- for some usae- on
the set of non sined inteers with the followin ruleB
@ 5et " denote the lenth of the bit strin- and let b(i) denote an inteer of value + if the i
th
bit in the strin is H+H-
and 9 otherwise. The encoded inteer n respects the e>uationB
n b i
k i
i tok
=

=

( )*
9
9
11.1.3.2 2-'o:)le:ent ,(nary
. messae part is said to encode in *@complement binary an inteer to indicate that concrete strins are mapped- for
some usae- on the set of sined inteers with the followin ruleB
@ 5et " denote the lenth of the bit strin- and let b(i) denote an inteer of value + if the i
th
bit in the strin is H+H-
and 9 otherwise. The encoded inteer n respects the e>uationB
if then
else
b n b i
n b i
k i
i tok
k i
i tok
k
( ) ( )
( )
9 + *
* *
9
9
9
9
= =
=

=

=

11.1.4 S)are )art&


%n some cases the specification is that which messae instances can be accepted by a receiver comprise more that the
leal messae instances that can be sent. One e'ample of this is the notion of spare bit. . spare bit has to send as the
value indicated in the specification (typically +)- but can be accepted as a + or a 9 by the receiver without error
dianosis. . spare field is a field composed entirely of spare bits.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /) "elease #
11.2 Stan%ar% L3 :e&&a4e&
11.2.1 /o:)onent& o5 a &tan%ar% L3 :e&&a4e
. standard 53 messae consists of an imperative part- itself composed of a header and the rest of imperative part-
followed by a non@imperative part. 0oth the non@header part of the imperative part and the non@imperative part are
composed of successive parts referred as standard information elements.
11.2.1.1 -or:at o5 &tan%ar% (n5or:at(on ele:ent&
. standard %2 may have the followin parts- in that orderB
@ an information element identifier (%2%)D
@ a lenth indicator (5%)D
@ a value part.
. standard %2 has one of the formats shown in table 99.9B
Table ,,',1 0ormats of information elements
0ormat Meaning 8:8 present 98 present *alue part present
T Ty)e only ye& no no
V Val$e only no no ye&
TV Ty)e an% Val$e ye& no ye&
LV Len4t* an% Val$e no ye& ye&
TLV Ty)e, Len4t* an% Val$e ye& ye& ye&
LV- Len4t* an% Val$e no ye& ye&
TLV- Ty)e, Len4t* an% Val$e ye& ye& ye&
!ome %2s may appear in the structure- but not in all instances of messaes. .n %2 is then said to be present or not
present in the messae instance. %f an %2 is not present in a messae instance- none of the three parts is present.
Otherwise- parts must be present accordin to the %2 format.
%n the messae structure- an %2 that is allowed not to be present in all messae instances is said not to be mandatory.
Other %2s are said to be mandatory.
5C@2 and T5C@2 are used for 2P! Mobility Manaement (2MM) and 2P! !ession Manaement (2!M) only.
11.2.1.1.1 8n5or:at(on ele:ent ty)e an% 7al$e )art
2very standard %2 has an information element type which determines the values possible for the value part of the %2-
and the basic meanin of the information. The information element type describes only the value part. !tandard %2s of
the same information element type may appear with different formats. The format used for a iven standard %2 in a
iven messae is specified within the description of the messae.
The value part of a standard %2 either consists of a half octet or one or more octetsD the value part of a standard %2 with
format 5C or T5C consists of an interal number of octets- between + and *88 inclusiveD it then may be empty- i.e.-
consist of (ero octetsD if it consists of a half octet and has format TC- its %2% consists of a half octet- too. 7or 5C@2 and
T5C@2- the value part of a standard %2 consists of an interal number of octets- between + and :8838 inclusive. The
value part of a standard %2 may be further structured into parts- called fields.
11.2.1.1.2 Len4t* (n%('ator
7or 5C or T5C- the lenth indicator (5%) of a standard %2 consists of one octet. 7or 5C@2 and T5C@2- the 5% of a
standard %2 consists of two octets where bit < of octet n contains the most sinificant bit and bit 9 of octet nI9 contains
the least sinificant bit (refer to fiure 99., in subclause 99.*.9.9.= for the relative orderin of the * octets). The 5%
contains the binary encodin of the number of octets of the %2 value part. The 5% of a standard %2 with empty value part
indicates + octets. !tandard %2 of an information element type such that the possible values may have different values
must be formatted with a lenth field- i.e.- 5C- T5C- 5C@2 or T5C@2.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ // "elease #
11.2.1.1.3 8n5or:at(on ele:ent (%ent(5(er
Khen present- the %2% of a standard %2 consists of a half octet or one octet. . standard %2 with %2% consistin of a half
octet has format TC- and its value part consists of a half octet. The value of the %2% depends on the standard %2- not on
its information element type. The %2%- if any- of a iven standard %2 in a iven messae is specified within the
description of the messae. %n some protocol specifications- default %2% values can be indicated. They are to be used if
not indicated in the messae specification. &on mandatory standard %2 in a iven messae- i.e.- %2 which may be not be
present (formally- for which the null strin is acceptable in the messae)- must be formatted with an %2%- i.e.- with
format T- TC- T5C or T5C@2.
11.2.1.1.4 /ate4or(e& o5 8&I or%er o5 o''$rren'e o5 88, L8, an% 7al$e )art
Totally four cateories of standard information elements are definedB
@ information elements of format C or TC with value part consistin of 9J* octet (type 9)D
@ information elements of format T with value part consistin of + octets (type *)D
@ information elements of format C or TC with value part that has fi'ed lenth of at least one octet (type 3)D
@ information elements of format 5C or T5C with value part consistin of (ero- one or more octets (type =)
@ information elements of format 5C@2 or T5C@2 with value part consistin of (ero- one or more octets and a
ma'imum of :8838 octets (type :). This cateory is used in 2P! only.
Type 9 standard information elements of format C provide the value in bit positions <- ?- :- 8 of an octet (see
fiure 99.9) or bits =- 3- *- 9 of an octet (see fiure 99.*).
E 7 ! " 4 3 2 1
- - - - 7al$e )art
0igure ,,',1 Tpe , 8: of format *
E 7 ! " 4 3 2 1
- - - -
7al$e )art
0igure ,,'%1 Tpe , 8: of format *
Type 9 standard information elements of format TC have an %2% of a half octet lenthD they provide the %2% in bit
positions <- ?- :- 8 of an octet and the value part in bit positions =- 3- *- 9 of the same octet- see fiure 99.3.
E 7 ! " 4 3 2 1
7al$e )art 88
0igure ,,'31 Tpe , 8: of format T*
. type * standard %2 has format TD its %2% consists of one octet- its value part is empty- see fiure 99.=.
E 7 ! " 4 3 2 1
88
0igure ,,'&1 Tpe % 8:
. type 3 standard information element has format C or TCD if it has format TC- its %2% consists of one octet and
proceeds the value part in the %2. The value part consists of at least one octet. !ee fiure 99.8 and fiure 99.:.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ /# "elease #
E 7 ! " 4 3 2 1
7al$e
)art
o'tet n
o'tet n 1 k
0igure ,,'-1 Tpe 3 8: of format * !k B (4 ,4 %4 '''$
7al$e
)art
o'tet n
o'tet n 1 k
E 7 ! " 4 3 2 1
88
o'tet n 1 1
0igure ,,'.1 Tpe 3 8: of format T* !k B ,4 %4 '''$
. type = standard information element has format 5C or T5C. %ts 5% precedes the value part- which consists of (ero-
one- or more octetsD if present- its %2% has one octet lenth and precedes the 5%. !ee fiure 99.? and fiure 99.<.
7al$e
)art
o'tet n
o'tet n 1 k
E 7 ! " 4 3 2 1
L8
o'tet n 1 1
0igure ,,')1 Tpe & 8: of format 9* !k B (4 ,4 %4 '''$
7al$e
)art
o'tet n 1 1
o'tet n 1 k
L8
o'tet n 1 2
o'tet n
E 7 ! " 4 3 2 1
88
0igure ,,'/1 Tpe & 8: of format T9* !k B ,4 %4 '''$
. type : standard information element has format T5C@2. The %2% has one octet lenth and precedes the 5% of * octets
and the value part which consists of (ero- one or up to :8838 octets. !ee fiure 99., and fiure 99.9+.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #( "elease #
0igure ,,'#1 Tpe . 8: of format 9*+: !k B ,4 %4 '''$
0igure ,,' ,(1 Tpe . 8: of format T9*+: !k B ,4 %4 '''$
11.2.2 6e&'r()t(on :et*o%& 5or 8 &tr$'t$re
!tandard %2s can be further structured in parts called fields. Two description methods are recommended and described
hereafter.
11.2.2.1 Ta,le&
.ccordin to this description method- the %2 is presented in its ma'imum format- i.e.- T- TC- T5C or T5C@2- in a
picture representin the bits in a table- each line representin an octet. 0its appear in the occidental order- i.e.- from left
of the pae to riht of the pae- and from top of the pae to bottom of the pae.
0o'es so delimited contains typically the field name- possibly an indication of which bits in the field are in the bo'- and
possibly a value (e..- for spare bits).
. specific method can be used in the %2 description to describe a branchin structure- i.e.- a structure variable accordin
to the value of particular fields in the %2. This desin is unusual outside type = and type : %2s- and as- a desin rule-
should be used only in type = and type : %2s.
a) The octet number of an octet within the %2 is defined typically in the table. %t consists of a positive inteer-
possibly of an additional letter- and possibly of an additional asteris"- see clause f). The positive inteer
identifies one octet or a roup of octets.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #, "elease #
b) 2ach octet roup is a self contained entity. The internal structure of an octet roup may be defined in alternative
ways.
c) .n octet roup is formed by usin some e'tension mechanism. The preferred e'tension mechanism is to e'tend
an octet (&) throuh the ne't octet(s) (&a- &b- etc.) by usin bit < in each octet as an e'tension bit.
@ The bit value H+H indicates that the octet roup continues throuh to the ne't octet. The bit value H9H indicates
that this octet is the last octet of the roup. %f one octet (&b) is present- the precedin octets (& and &a) shall
also be present.
@ %n the format descriptions of the individual information elements- bit < is mar"ed H+J9 e'tH if another octet
follows. 0it < is mar"ed H9 e'tH if this is the last octet in the e'tension domain.
@ .dditional octets may be defined in later versions of the protocols (H9 e'tH chaned to H+J9 e'tH) and
e>uipments shall be prepared to receive such additional octetsD the contents of these octets shall be inored.
Aowever the lenth indicated in the formal description of the messaes and of the individual information
elements only ta"es into account this version of the protocols.
d) %n addition to the e'tension mechanism defined above- an octet (&) may be e'tended throuh the ne't octet(s)
(&I9- &I* etc.) by indications in bits ?@9 (of octet &).
e) The mechanisms in c) and d) may be combined.
f) Optional octets are mar"ed with asteris"s (E). .s a desin rule- the presence or absence of an optional octet
should be determinable from information in the %2 and precedin the optional octet. 1are should be ta"en not to
introduce ambiuities with optional octets.
) .t the end of the %2- additional octets may be added in later versions of the protocols also without usin the
mechanisms defined in c) and d). 2>uipments shall be prepared to receive such additional octetsD the contents of
these octets shall be inored. Aowever the lenth indicated in the formal description of the messaes and of the
individual information elements only ta"es into account this version of the protocols.
11.2.2.1.1 /o:)a't notat(on
The compact notation described in .nne' 0 can be used to describe the value part of a standard %2. This method is
recommended for comple' structures- or for a branchin structure not respectin octet boundaries.
11.2.3 8:)erat(7e )art o5 a &tan%ar% L3 :e&&a4e
The imperative part of a standard 53 messae is composed of a header possibly followed by mandatory standard %2s
havin the format C- 5C or 5C@2.
11.2.3.1 Stan%ar% L3 :e&&a4e *ea%er
The header of a standard 53 messae is composed of two octets- and structured in three main parts- the protocol
discriminator (9J* octet)- a messae type octet- and a half octet used in some cases as a Transaction %dentifier- in some
other cases as a sub@protocol discriminator- and called s"ip indicator otherwise.
7or the 2P! protocols 2MM and 2!M- a standard 53 messae can be either a plain &.! messae or a security
protected &.! messaeB
@ The header of a plain &.! messae is composed of two or three octets- and structured in four main parts- the
protocol discriminator (9J* octet)- a half octet used in some cases as security header type and in other cases as an
2P! bearer identity (9J* octet)- a messae type octet- and one octet included in some cases and used as a
procedure transaction identity (PT%). %f the procedure transaction identity is present- it is precedin the messae
type octet.
@ The header of a security protected &.! messae is composed of si' octets- and structured in four main parts- the
protocol discriminator (9J* octet)- a half octet used as security header type- a messae authentication code of
four octets- and a se>uence number of one octet. This header is followed by a complete plain &.! messae (i.e.
includin the header of this plain &.! messae).
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #% "elease #
11.2.3.1.1 Proto'ol %(&'r(:(nator
0its 9 to = of the first octet of a standard 53 messae contain the protocol discriminator (P;) information element. The
P; identifies the 53 protocol to which the standard layer 3 messae belons. The correspondence between 53 protocols
and P;s is one@to@one.
7or future evolution an e'tension mechanism is foreseen which allows the use of protocol discriminators with one octet
lenth- where bits = to one are coded as 9 9 9 +. Messaes of such protocols may not be standard 53 messaes. %n
particular- the rest of the header may not respect the structure described in this sub@clause.
The P; can ta"e the followin valuesB
Table ,,'%1 Protocol discriminator 3alues
bits & 3 % ,
0 0 0 0 4ro$) 'all 'ontrol
0 0 0 1 ,roa%'a&t 'all 'ontrol
0 0 1 0 PS &e&&(on :ana4e:ent :e&&a4e&
0 0 1 1 'all 'ontrolI 'all relate% SS :e&&a4e&
0 1 0 0 GP#S Tran&)arent Tran&)ort Proto'ol (GTTP)
0 1 0 1 :o,(l(ty :ana4e:ent :e&&a4e&
0 1 1 0 ra%(o re&o$r'e& :ana4e:ent :e&&a4e&
0 1 1 1 PS :o,(l(ty :ana4e:ent :e&&a4e&
1 0 0 0 GP#S :o,(l(ty :ana4e:ent :e&&a4e&
1 0 0 1 SMS :e&&a4e&
1 0 1 0 GP#S &e&&(on :ana4e:ent :e&&a4e&
1 0 1 1 non 'all relate% SS :e&&a4e&
1 1 0 0 Lo'at(on &er7('e& &)e'(5(e% (n 3GPP TS 44.071 JEaK
1 1 1 0 re&er7e% 5or e2ten&(on o5 t*e P6 to one o'tet len4t*
1 1 1 1 $&e% ,y te&t& )ro'e%$re& %e&'r(,e% (n 3GPP TS 44.014 J"aK, 3GPP TS
34.109 J17aK an% 3GPP TS 3!."09 J2!K.
%f the networ" receives- on a !.P where it e'pects standard 53 messaes- a messae with a protocol discriminator
different from those specified in table 99.*- the networ" may inore the messae or initiate the channel release
procedure defined in 3GPP T! ==.+9< F:bG.
%f the Mobile !tation receives- on a !.P where it e'pects standard 53 messaes- a standard 53 messae with a protocol
discriminator different from those specified in table 99.*- or for a protocol that it does not support- the Mobile !tation
shall inore the messae.
11.2.3.1.2 Sk() (n%('ator
0its 8 to < of octet 9 of a standard 53 messae may be used differently- dependin on the protocol and the !.P. The use
of this half@octet is consistent for a iven P; and !.P. One possibility is that this half@octet contains the s"ip indicator.
3nless otherwise specified in the protocol- the s"ip indicator %2 is a spare field.
11.2.3.1.3 Tran&a't(on (%ent(5(er
. 53 protocol may define that bits 8 to < of octet 9 of a standard 53 messae of the protocol contains the transaction
identifier (T%). The T% allows to distinuish up to 9: different bi@directional messaes flows for a iven P; and a iven
!.P. !uch a messae flow is called a transaction.
.n e'tension mechanism for T% is also defined. This mechanism allows to distinuish up to *8: different bi@directional
messaes flows for a iven P; and a iven !.P. The e'tension mechanism shall not be used unless e'plicitly stated in
the core specification(s) for the protocol. The T% %2 is coded as shown in fiure 99., and table 99.3. %t is composed of
the T% value and the T% fla.
The T% value and the T% fla occupy bits 8 @ ? and bit < of the first octet respectively.
The e'tended T% shall not be used unless T% values of ? or reater are needed.
Khere the e'tended T% is used- the T% %2 includes a second octet. The T% value in the first octet is inored- and the T%
value is encoded in bits ?@9 of the second octet.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #3 "elease #
&OT2B %n other specifications- in respect to error handlin- there are references to T% value H999H. This refers to
the binary encodin of bits 8 N? in octet 9. 7or protocols which do not use the e'tended T% this #999#
encodin is still handled as an error case.Transactions are dynamically created- and their T% value is
assined at creation time. T% values are assined by the side of the interface initiatin a transaction. .t the
beinnin of a transaction a free T% value (i.e.- a value not yet used for the iven P;- the iven !.P- and
with the iven initiator) is chosen and assined to this transaction. %t then remains fi'ed for the lifetime of
the transaction. .fter a transaction ends- the associated T% value is free and may be reassined to a later
transaction.
Two identical T% values may be used when each value pertains to a transaction initiated by the different sides of the
interface. %n this case the T% fla shall avoid ambiuity. The transaction identifier fla can ta"e the values H+H or H9H.
The T% fla is used to identify which side of the interface initiated the transaction. . messae has a T% fla set to H+H
when it belons to transaction initiated by its sender- and to H9H otherwise.
Aence the T% fla identifies who allocated the T% value for this transaction and the only purpose of the T% fla is to
resolve simultaneous attempts to allocate the same T% value.
The T% e'tension mechanism may in future evolution of the 53 protocols be further e'tended by settin the 2MT fla in
octet * to H+H (see fiure 99.,).
< ? : 8 = 3 * 9
T%
fla
T%O @ @ @ @ Octet 9
9
2MT
T%2
Octet *
E
0igure ,,'#1 Transaction identifier
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #& "elease #
Table ,,'31 Transaction identifier
T8 5la4 (o'tet 1)
;(t
E
0 T*e :e&&a4e (& &ent 5ro: t*e &(%e t*at or(4(nate& t*e T8
1 T*e :e&&a4e (& &ent to t*e &(%e t*at or(4(nate& t*e T8
T8< (o'tet 1)
;(t&
7 ! "
0 0 0 T8 7al$e 0
0 0 1 - - 1
0 1 0 - - 2
0 1 1 - - 3
1 0 0 - - 4
1 0 1 - - "
1 1 0 - - !
1 1 1 T*e T8 7al$e (& 4(7en ,y t*e T8 (n o'tet 2
T8 (o'tet 2)
;(t& 7-1
0000000
0000001
0000010
0000011
0000100
0000101
0000110
#e&er7e%.
+ll ot*er 7al$e& T*e T8 7al$e (& t*e ,(nary re)re&entat(on o5 T8
B*ere ,(t 7 (& t*e :o&t &(4n(5('ant ,(t
+n% ,(t 1 (& t*e lea&t &(4n(5('ant ,(t
11.2.3.1.4 S$,-)roto'ol %(&'r(:(nator
. 53 protocol may define that bits 8 to < of octet 9 of a standard 53 messae of the protocol contains the sub@protocol
discriminator (!P;). The !P; allows to distinuish between different protocols inside one sublayer.
Table ,,'&1 Sub+Protocol discriminator 3alues
bits / ) . -
0 0 0 0 Val$e $&e% ,y t*e Sk() 8n%('ator (&ee 11.2.3.1.2)
0 0 0 1 /TS &$,-)roto'ol
0 0 1 0 L
To M all ot*er 7al$e& are re&er7e%
1 1 1 1 3
11.2.3.1." PS ,earer (%ent(ty
. 53 protocol may define that bits 8 to < of octet 9 of a standard 53 messae of the protocol contain the 2P! bearer
identity. The 2P! bearer identity is used to identify a messae flow.
E 7 ! " 4 3 2 1
PS ,earer (%ent(ty 7al$e - - - - o'tet 1
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #- "elease #
0igure ,,'#a1 :PS bearer identit
Table ,,'-1 :PS bearer identit
PS ,earer (%ent(ty 7al$e (o'tet 1)
;(t&
/ ) . -
0 0 0 0 .o PS ,earer (%ent(ty a&&(4ne%
0 0 0 1 #e&er7e%
0 0 1 0 #e&er7e%
0 0 1 1 #e&er7e%
0 1 0 0 #e&er7e%
0 1 0 1 PS ,earer (%ent(ty 7al$e "
0 1 1 0 PS ,earer (%ent(ty 7al$e !
0 1 1 1 PS ,earer (%ent(ty 7al$e 7
1 0 0 0 PS ,earer (%ent(ty 7al$e E
1 0 0 1 PS ,earer (%ent(ty 7al$e 9
1 0 1 0 PS ,earer (%ent(ty 7al$e 10
1 0 1 1 PS ,earer (%ent(ty 7al$e 11
1 1 0 0 PS ,earer (%ent(ty 7al$e 12
1 1 0 1 PS ,earer (%ent(ty 7al$e 13
1 1 1 0 PS ,earer (%ent(ty 7al$e 14
1 1 1 1 PS ,earer (%ent(ty 7al$e 1"
11.2.3.1.! Se'$r(ty *ea%er ty)e
. 53 protocol may define that bits 8 to < of octet 9 of a standard 53 messae of the protocol contain the security header
type.
11.2.3.1a Pro'e%$re tran&a't(on (%ent(ty
. 53 protocol may define that the second octet of a standard 53 messae of the protocol contains the procedure
transaction identity (PT%). The PT% allows distinuishin up to *8= different bi@directional messaes flows for a iven
P; and a iven !.P. !uch a messae flow is called a transaction. The procedure transaction identity is released when
the procedure is completed.
Table ,,'.1 Procedure transaction identit
;(t&
/ ) . - & 3 % ,
0 0 0 0 0 0 0 0 .o )ro'e%$re tran&a't(on (%ent(ty a&&(4ne%
0 0 0 0 0 0 0 1 L
to M Pro'e%$re tran&a't(on (%ent(ty 7al$e
1 1 1 1 1 1 1 0 3
1 1 1 1 1 1 1 1 #e&er7e%
11.2.3.2 Me&&a4e ty)e o'tet
11.2.3.2.1 Me&&a4e ty)e o'tet (w*en a''e&&(n4 #elea&e 9E an% ol%er network& only)
The messae type octet is the second octet in a standard 53 messae.
Khen a standard 53 messae is e'pected- and a messae is received that is less than 9: bit lon- that messae shall be
inored.
Khen the radio connection started with a core networ" node of a /elease ,< or older networ"- the messae type %2 is
coded as shown in fiure 99.9+a and 99.9+'.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #. "elease #
0it < is encoded as H+HD value H9H is reserved for possible future use as an e'tension bit. . protocol entity e'pectin a
standard 53 messae- and receivin a messae containin bit < of octet * encoded as H9H shall dianose a H messae not
defined for the P;H error and treat the messae accordinly.
%n messaes of MM- 11- !! (via 1! domain)- G11 and 011 protocol sent usin the transmission functionality
provided by the // layer to upper layers- and sent from the mobile station or the 5M3 to the networ"- bit ? of octet * is
used for send se>uence number- see subclause 99.*.3.*.3.
%n messaes of the 51! protocol sent usin the transmission functionality provided by the // layer to upper layers- and
sent from the type . 5M3 to the networ"- bit ? of octet * is used for send se>uence number- see subclause 99.*.3.*.3.
%n all other standard layer 3 messaes- e'cept for // messaes- bit ? is set to a default value. . protocol entity
e'pectin a standard 53 messae- and not usin the transmission functionality provided by the // layer- and receivin
a messae containin bit ? of octet * encoded different to the default value shall dianose a Hmessae not defined for
the P;H error and treat the messae accordinly.
The default value for bit ? is + e'cept for the !M protocol where the default value is 9. &o default value for bit ? is
specified for // protocol. 7or // messae types see 3GPP T! ==.+9<.
E 7 ! " 4 3 2
1
0
o'tet 1
Me&&a4e ty)e
. (S6)
or 0
0igure ,,',(a1 Message tpe 8: !MM4 CC4 SS4 GCC4 6CC and 9CS$
E 7 ! " 4
3 2 1
o'tet 1
Me&&a4e ty)e
0igure ,,',(?1 Message tpe 8: !protocol other than MM4 CC4 SS4 GCC4 6CC and 9CS$
7or MM- 11- !!- G11- 011 and 51! protocols bits 9 to : of octet * of standard 53 messaes contain the messae
type. 7or all other 53 protocols bits 9 to < of octet * of standard 53 messae contain the messae type.
The messae type determines the function of a messae within a protocol in a iven direction. The meanin of the
messae type is therefore dependent on the protocol (the same value may have different meanins in different
protocols)- and the direction (the same value may have different meanins in the same protocol- when sent from the
Mobile !tation to the networ" and when sent from the networ" to the Mobile !tation).
2ach protocol defines a list of allowed messae types for each relevant !.P. . messae received analysed as a standard
53 messae- and with a messae type not in the correspondin list leads to the dianosis Hmessae not defined for the
P;H. !ome messae types may correspond to a function not implemented by the receiver. They are then said to be not
implemented by the receiver.
The reaction of a protocol entity e'pectin a standard 53 messae and receivin a messae with messae type not
defined for the P; or not implemented by the receiver and the reception conditions is defined in the relevant protocol
specification. .s a eneral rule- a protocol specification should not force the receiver to analyse the messae further.
11.2.3.2.2 Me&&a4e ty)e o'tet (w*en a''e&&(n4 #elea&e 99 an% newer network&)
The messae type octet is the second octet in a standard 53 messae.
Khen a standard 53 messae is e'pected- and a messae is received that is less than 9: bit lon- that messae shall be
inored.
Khen the radio connection started with a core networ" node of a /elease ,, or later networ"- the messae type %2 is
coded dependent on the P; as shown in fiures 99.9+b- c and d.
%n messaes of MM- 11 and !! (via 1! domain) protocol sent usin the transmission functionality provided by the //
andJor access stratum layer to upper layers- and sent from the mobile station or the 5M3 to the networ"- bits ? and < of
octet * are used for send se>uence number- see subclause 99.*.3.*.3.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #) "elease #
%n messaes of G11 and 011 protocol sent usin the transmission functionality provided by the // layer to upper
layers- and sent from the mobile station or the 5M3 to the networ"- only bit ? of octet * is used for send se>uence
number. 0it < is set to the default value.
%n messaes of the 51! protocol sent usin the transmission functionality provided by the // layer to upper layers- and
sent from the type . 5M3 to the networ"- only bit ? of octet * is used for send se>uence number. 0it < is set to the
default value.
%n all other standard layer 3 messaes- e'cept for // messaes- bits ? and < are set to the default value. . protocol
entity e'pectin a standard 53 messae- and not usin the transmission functionality provided by the // andJor access
stratum layer- and receivin a messae containin bit ? or bit < of octet * encoded different to the default value shall
dianose a Hmessae not defined for the P;H error and treat the messae accordinly.
%n messaes of the // protocol entity- bit < of octet * is set to the default value. The other value is reserved for possible
future use as an e'tension bit .%f an // protocol entity e'pectin a standard 53 messae receives messae containin bit
< of octet * encoded different from the default value it shall dianose a Hmessae not defined for the P;H error and treat
the messae accordinly.
The default value for bit < is +. The default value for bit ? is + e'cept for the !M protocol which has a default value
of 9. &o default value for bit ? is specified for // protocol. 7or // messae types see 3GPP T! ==.+9<.
7or 2P!D the default value for bit ? is 9. The value for bit < is + for the 2MM protocol and 9 for the 2!M protocol.
E 7 ! " 4
3 2 1
o'tet 1
Me&&a4e ty)e
. (S6) or 0
0igure ,,',(b1 Message tpe 8: !MM4 CC and SS$
E 7 ! " 4
3 2
1
0
o'tet 1
Me&&a4e ty)e
. (S6)
or 0
0igure ,,',(c1 Message tpe 8: !GCC4 6CC and 9CS$
E 7 ! " 4
3 2 1
o'tet 1
Me&&a4e ty)e
0igure ,,',(d1 Message tpe 8: !protocol other than MM4 CC4 SS4 GCC4 6CC and 9CS$
7or MM- 11- !!- G11- 011 and 51! protocols bits 9 to : of octet * of standard 53 messaes contain the messae
type. 7or all other 53 protocols bits 9 to < of octet * of standard 53 messae contain the messae type.
The messae type determines the function of a messae within a protocol in a iven direction. The meanin of the
messae type is therefore dependent on the protocol (the same value may have different meanins in different
protocols)- and the direction (the same value may have different meanins in the same protocol- when sent from the
Mobile !tation to the networ" and when sent from the networ" to the Mobile !tation).
2ach protocol defines a list of allowed messae types for each relevant !.P. . messae received analysed as a standard
53 messae- and with a messae type not in the correspondin list leads to the dianosis Hmessae not defined for the
P;H. !ome messae types may correspond to a function not implemented by the receiver. They are then said to be not
implemented by the receiver.
The reaction of a protocol entity e'pectin a standard 53 messae and receivin a messae with messae type not
defined for the P; or not implemented by the receiver and the reception conditions is defined in the relevant protocol
specification. .s a eneral rule- a protocol specification should not force the receiver to analyse the messae further.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ #/ "elease #
11.2.3.2.3 Se9$en'e% :e&&a4e tran&5er o)erat(on
3pper layer messaes sent usin the // sub@layer transport service from the mobile station to the networ" can be
duplicated by the data lin" layer in at least the followin casesB
@ in .JGb mode- when a channel chane of dedicated channels is re>uired (assinment or handover procedure)
and the last layer * frame has not been ac"nowleded by the peer data lin" layer before the mobile station leaves
the old channelD
@ in %u mode- when an /51 re@establishment occurs (e.. due to relocation) and the /51 layer has not
ac"nowleded the last one or more /51 P;3s before /51 re@establishmentD
@ an inter@system chane from %u mode to .JGb mode is performed and the /51 layer has not ac"nowleded the
last one or more /51 P;3sD
@ an inter@system chane from .JGb mode to %u mode is performed and the last layer * frame in .JGb mode has
not been ac"nowleded by the peer data lin" layer before the mobile station leaves the old channel.
%n these cases- the mobile station does not "now whether the networ" has received the messaes correctly. Therefore-
the mobile station has to send the messaes aain when the channel chane is completed.
The networ" must be able to detect the duplicated received messaes. Therefore- each concerned upper layer messaes
must be mar"ed with a send se>uence number.
To allow for different termination points in the infrastructure of the messaes of different P;s- the se>uence numberin
is specific to each P;. 7or historical reasons- an e'ception is that messaes sent with the 11- !! (via 1! domain) and
MM P;s share the same se>uence numberin. %n the followin- the phrase upper layer message flow refers to a flow
of messaes sharin the same se>uence numberin. The different upper layer flows are MMI11I!! (via 1! domain)-
G11- 011 and 51!. The GMM- 2MM- !M- 2!M- !M!- !! (via P! domain) and T1 (Test 1ontrol- see
3GPP T! ==.+9= F8aG- 3GPP T! 3=.9+, F9?aG and 3GPP T! 3:.8+, F*:G) protocols do not use layer 3 se>uence
numberin.
%n a shared networ" with a MO1& confiuration- &etwor" !harin non@supportin 32s can be redirected between 1&
operators (see 3GPP T! *3.*89 F**G). Khen the redirection ta"es place- the 1& node of the redirectin 1& operator
shall forward via the /.& the value of &(!;) of the last messae received on the MMI11I!! (via 1! domain)
messae flow to the 1& node of the ne't 1& operator (3GPP T! *8.=93 F*3G).
11.2.3.2.3.1 Var(a,le& an% &e9$en'e n$:,er&
11.2.3.2.3.1.1 Sen% &tate 7ar(a,le V(S6)
The mobile station shall have one associated send state variable C(!;) (H!end ;uplicatedH) for each upper layer
messae flow. The send state variable denotes the se>uence number of the ne't in se>uence numbered messae in the
flow to be transmitted. The value of the correspondin send state variable shall be incremented by one with each
numbered messae transmission.
7or the MMI11I!! (via 1! domain) upper layer messae flowB
@ when the // connection starts with a core networ" of /elease ,< or earlier- arithmetic operations on C(!;) are
performed modulo *. The mobile station shall "eep usin modulo * for the duration of the // connectionD
@ when the // connection starts with a core networ" of /elease ,, or later- arithmetic operations on C(!;) are
performed modulo =. The mobile station shall "eep usin modulo = for the duration of the // connectionD
@ after successful completion of !/C11 handover (see 3GPP T! *3.*9: F*?G)- the mobile station shall perform
modulo = arithmetic operations on C(!;). The mobile station shall "eep usin modulo = until the release of the
// connection established at !/C11 handover.
&OT2 9B %n .JGb mode- the release supported by the core networ" is indicated in the M!1/ bit and in the !G!&/
bit in the system information broadcast (see 3GPP T! ==.+9< F:bG and 3GPP T! ==.+:+ F9+aG).
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ## "elease #
&OT2 *B ;urin !/C11 handover the M!1/ bit is not provided to the mobile station- and therefore the mobile
station assumes to access to a /elease ,, or later core networ".
7or the G11- 011- and 51! upper layer messae flows- arithmetic operations on C(!;) are performed modulo *.
11.2.3.2.3.1.2 Sen% &e9$en'e n$:,er .(S6)
.t the time when such a messae to be numbered is desinated for transmission- the value of &(!;) for the messae to
be transferred is set e>ual to the value of the send state variable C(!;).
11.2.3.2.3.2 Pro'e%$re& 5or t*e (n(t(at(on, tran&5er e2e'$t(on an% ter:(nat(on o5 t*e &e9$en'e%
:e&&a4e tran&5er o)erat(on
11.2.3.2.3.2.1 8n(t(at(on
The se>uenced messae transfer operation is initiated by establishin a // connection. The send state variables C(!;)
are set to +.
.fter successful completion of !/C11 handover (see 3GPP T! *3.*9: F*?G)- the mobile station shall set the send state
variable C(!;) to +.
11.2.3.2.3.2.2 Tran&5er 2e'$t(on
The core networ" shall compare the send se>uence numbers of pairs of subse>uent messaes in the same upper layer
messaes flow.
7or the G11- 011- and 51! upper layer messae flows- in case the send se>uence numbers of two subse>uent
messaes in a flow are not identical- no duplication has occurred. %n case the send se>uence numbers are identical- the
networ" must inore the second one of the received messaes.
7or the MMI11I!! (via 1! domain) upper layer messae flowB
@ when accessed by a release ,< or earlier mobile station- in case the send se>uence numbers of two subse>uent
messaes in the flow are identical- the core networ" shall discard the second one of the received messaesD
@ when accessed by a release ,, or later mobile station- the core networ" shall discard any messae whose &(!;)
is not the increment by one (modulo =) of the &(!;) of the last accepted messae.
&OT2B The release supported by the mobile station is indicated by the revision level in the Mobile Station
Classmark 1 or Mobile Station Classmark 2 information element- or by the revision level indicator in the
MS network capability information element (see 3GPP T! *=.++<- subclause 9+.8).
%n a shared networ" with a MO1& confiuration- the core networ" node to which the mobile station was redirected
shall compare the send se>uence number of the first messae received after the redirection in the MMI11I!! (via 1!
domain) messae flow with the value of &(!;) received durin the redirection procedure (see 3GPP T! *3.*89 F**G)B
@ when accessed by a release ,< or earlier mobile station- if the two send se>uence numbers are identical- the core
networ" shall discard the received messae from the mobile stationD
@ when accessed by a release ,, or later mobile station- the core networ" shall discard any messae whose &(!;)
is not the increment by one (modulo =) of the &(!;) received durin the redirection procedure.
11.2.3.2.3.2.3 Ter:(nat(on
The se>uenced messae transfer operation is terminated by the // connection release procedure.
%nter system chane from .JGb mode to %u mode or from %u mode to .JGb mode shall not terminate the se>uenced
messae transfer. 3MT! !/&1 relocation shall not terminate the se>uenced messae transfer.
11.2.3.3 Stan%ar% (n5or:at(on ele:ent& o5 t*e (:)erat(7e )art
The messae type octet of a standard 53 messae may be followed by mandatory standard %2s havin the format C- 5C
or 5C@2 as specified in the messae description in the relevant protocol specification.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(( "elease #
.s a desin rule- octet boundaries must be respected. This implies that half@octet standard %2s (i.e.- C formatted type 9
standard %2s) must appear by pair.
%f messae is received as a standard 53 messae- and that is too short to contain the complete imperative part as
specified in the relevant protocol specification- an imperative messae part error is dianosed. (The same error may be
dianosed at detection of certain contents of the imperative part of a messaeD this is defined in the relevant protocol
specification.) The treatment of an imperative messae part error is defined in the relevant protocol specification.
11.2.4 .on-(:)erat(7e )art o5 a &tan%ar% L3 :e&&a4e
The imperative part of a standard 53 messae is followed by the (possibly empty) non@imperative part. The relevant
protocol specification defines where the imperative part of a standard 53 messae ends. The non@imperative part of a
standard 53 messae is composed of ((ero- one- or several) standard %2s havin the format T- TC- T5C or T5C@2. The
receiver of a standard 53 messae shall analyse the non imperative part as a succession of standard %2s each containin
an %2%- and shall be prepared for the non@imperative part of the messae to contain standard %2s that are not specified in
the relevant protocol specification.
.n %2% may be "nown in a messae or un"nown in a messae. 2ach protocol specification lists- for each messae
(i.e.- accordin to the messae type- the direction and the lower layer !.P)- the "nown standard %2s in the non@
imperative part.
.n %2% that is "nown in a messae desinates the %2 type of the %2 the first part of which the %2% is- as well as the use of
the information. Khich %2 type it desinates is specified in the relevant protocol specification. Kithin a messae-
different %2%s may desinate the same %2 type if that is defined in the relevant protocol specification.
Khether the second part of an %2 with %2% "nown in a messae is the lenth or not (in other words- whether the %2% is
the first part of an %2 formatted as T5C- T5C@2 or not) is specified in the relevant protocol specification.
3nless otherwise specified in the protocol specification- the receiver shall assume that %2 with un"nown %2% are TC
formatted type 9- T formatted type *- T5C formatted type = or T5C@2 formatted type : standard %2s. The %2% of
un"nown %2s toether with- when applicable- the lenth indicator- enable the receiver to determine the total lenth of
the %2- and then to s"ip un"nown %2s. The receiver shall assume the followin rule for %2s with un"nown %2%B
0it < of the %2% octet is set to H9H indicates a TC formatted type 9 standard %2 or a T formatted type * %2s. Aence-
a 9 valued bit < indicates that the whole %2 is one octet lon.
7urthermore- for the 2P! protocols 2MM and 2!MB
0it < of the %2% octet set to H+H and bits ? to = set to H9H indicates a T5C@2 formatted type : %2- i.e. the followin
two octets are lenth octets. 0it < of the %2% octet set to H+H and bit ? to = set to any other bit combination
indicates a T5C formatted type = %2- i.e. the followin octet is a lenth octet.
7or all other protocolsB
0it < of the %2% octet set to H+H indicates a T5C formatted type = %2. Aence- the followin octet is a lenth octet.
.s a desin rule- it is recommended that %2%s of any TC formatted type 9- T formatted type *- T5C formatted type = or
T5C@2 formatted type : %2 follow the rule- even if assumed to be "nown by all potential receivers.
. messae may contain two or more %2s with e>ual %2%. Two %2s with the same %2% in a same messae must have the
same format- and- when of type 3- the same lenth. More enerally- care should be ta"en not to introduce ambiuities
by usin an %2% for two purposes. .mbiuities appear in particular when two %2s potentially immediately successive
have the same %2% but different meanins and when both are non@mandatory. .s a recommended desin rule- messaes
should contain a sinle %2 of a iven %2%.
2ach protocol specification may put specific rules for the order of %2s in the non@imperative part. .n %2 "nown in the
messae- but at a position non compliant with these rules is said to be out of se>uence. .n out of se>uence %2 is
decoded accordin to the format- and- when of type 3 the lenth- as defined in the messae for its %2%.
11.2." Pre&en'e re9$(re:ent& o5 (n5or:at(on ele:ent&
The relevant protocol specification may define three different presence re>uirements (M- 1- or O) for a standard %2
within a iven standard 53 messaeB
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(, "elease #
@ M (HMandatoryH) means that the %2 shall be included by the sendin side- and that the receiver dianoses a
Hmissin mandatory %2H error when detectin that the %2 is not present. .n %2 belonin to the imperative part of
a messae has presence re>uirement M. .n %2 belonin to the non@imperative part of a messae may have
presence re>uirement MD
@ 1 (H1onditionalH) meansB
E that inclusion of the %2 by the sender depends on conditions specified in the relevant protocol specificationD
E that there are conditions for the receiver to e'pect that the %2 is present andJor conditions for the receiver to
e'pect that the %2 is not present in a received messae of a iven P;- !.P and messae typeD these
conditions depend only on the content of the messae itself- and not for instance on the state in which the
messae was received- or on the receiver characteristicsD they are "nown as static conditionsD
E that the receiver detectin that the %2 is not present when sufficient static conditions are fulfilled for its
presence- shall dianose a Hmissin conditional %2H errorD
E that the receiver detectin that the %2 is present when sufficient static conditions are fulfilled for its non@
presence- shall dianose an Hune'pected conditional %2H error.
@ Only %2s belonin to the non@imperative part of a messae may have presence re>uirement 1D
@ O (HOptionalH) means that the receiver shall never dianose a Hmissin mandatory %2H error- a Hmissin
conditional %2H error- or an Hune'pected conditional %2H error because it detects that the %2 is present or that the
%2 is not present. (There may however be conditions dependin on the states- resources- etc. of the receiver to
dianose other errors.) Only %2s belonin to the non@imperative part of a messae may have presence
re>uirement O.
3nless otherwise specified the presence of a %2 of un"nown %2% or of an out of se>uence %2 shall not lead by itself to an
error. .n alternative specification is the #comprehension re>uired# scheme. . type = %2 is encoded as #comprehension
re>uired# if bits 8- :- ? and < of its %2% are set to (ero. . type : %2 is encoded as #comprehension re>uired# if bit < is set to
(ero and bits 3- =- 8- :- and ? of its %2% are set to one. The #comprehension re>uired# scheme is to be applied if e'plicitly
indicated in the protocol specification. The reaction on the reception of an un"nown or out of se>uence %2 coded as
#comprehension re>uired# is specified in the relevant protocol specification.
11.2.! 6e&'r()t(on o5 &tan%ar% L3 :e&&a4e&
This subclause describes a eneric description method for standard 53 messaes- the tabular description. Protocol
specification may follow other methods.
. standard 53 messae is described by a table listin the header elements and the standard %2s in the messae. 7or each
element is ivenB
@ if applicable the %2%- in he'adecimal representation (one diit followed by and hyphen for TC formatted type 9-
and two diits for the other cases)D
@ the name of the %2 (this is used in particular for the description of conditional presence rules)D
@ the type of the information element- with a reference of where the internal structure of the value part is specifiedD
@ the format of the standard %2 (T- C- TC- 5C- T5C- 5C@2 or T5C@2)D and
@ the lenth- or the rane of lenths- of the whole standard %2- includin when applicable the T and 5 parts.
The list of elements is iven in the table in the order they appear in the resultin bit strin- with the e'ception of
half@octet elements in the imperative partB half octets in a pair are inverted. This applies in particular for the two first
header elementsB the protocol discriminator appears first in a table describin a standard 53 messae.
11.3 .on &tan%ar% L3 :e&&a4e&
%n some protocols- the structure of part or all of the messaes miht not always follow the standard 53 messae
structure. .s a desin rule- this should be consistent for a iven protocol- direction and lower layer !.P.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(% "elease #
. possibility is to describe the messae with the compact notation described in .nne' 0.
. few consistent structures are found in the present protocol specifications- and are described hereafter.
Other structures can be described directly in the protocol specifications.
11.3.1 /a&e +0 ;//= an% +G/=3P/= :e&&a4e&
%n these cases- the !.P capability is for fi'ed lenth messaes. The messaes are structured as standard 53 messaes
plus one octet in front- the 5* pseudo lenth octet- and a rest octet part at the end.
11.3.1.1 L2 P&e$%o Len4t* o'tet
This octet- the 5* pseudo lenth indicator octet- indicates the lenth in octets of the subse>uent octet strin that can be
analysed as a standard 53 messae.
The octet is structured as followsB
0its 3 to < encodes in binary the 5* pseudo lenth- i.e.- the lenth of the part to be analysed as a standard 53
messaeD
0it * is set to H+HD
0it 9 is set to H9H.
. receiver e'pectin a messae so structured and receivin a messae with bit 9 of octet 9 (i.e.- the <
th
bit of the
messae) set to H9H and bit * of octet 9 (i.e.- the ?
th
bit of the messae) different from H+H- shall abandon the analysis of
the messae.
. receiver e'pectin a messae so structured and receivin a messae on .G1AJP1AB
@ with an 5* pseudo lenth indicator encodin + or 9 shall s"ip the indicated number of octets and not try to analyse
the standard 53 messae partD
@ with a 5* pseudo lenth indicator bier than what is compatible with the !.P capability shall abandon the analysis
of the messae.
11.3.1.2 #e&t <'tet&
The part after the part structured as a standard 53 messae- and up to the end of the messae as constrained by lower
layers- is presented as a non standard %2 of variable lenth (sometime indicated as of type 8)- the Hrest octetsH %2.
The rest octets element may be described by table description- or- preferably- usin the compact notation described in
.nne' 0 of the present document.
11.3.1.3 6e&'r()t(on o5 a :o%(5(e% &tan%ar% L3 :e&&a4e
The description can be provided in the same way as a standard 53 messae- with in the case of a tabular description one
non standard %2 at the beinnin (of type 5* pseudo lenth)- and one non standard %2 at the end.
11.3.2 /a&e ;0 S+//= 3 S6//= 3 -+//= :e&&a4e& &ent (n
$na'knowle%4e% :o%e
The messaes are structured either as standard 53 messaes- or in the so@called short header format. The value of the <
th
bit (bit 9 of octet 9) of the lin" layer P;3 distinuishes the two cases. %n the case of the short header- the 53 messae is
the same bit strin as the lin" layer P;3- and has a fi'ed lenth. The followin description includes the *@bit lin" layer
header.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(3 "elease #
11.3.2.1 T*e 5(r&t o'tet
0its 9 and * are the lin" layer header. 0it * of octet 9 is set to H+H- and bit 9 is reserved for the lin" layer.
. protocol discriminator is the first part of the messae (startin bit < of octet 9). The protocol discriminator field may
have different lenths. The followin protocol discriminator is definedB
@ + //.
.ll additional P; defined for this structure shall start by 9. The reception of a messae with bit < of octet 9 set to 9
when e'pectin a messae structured as defined by this clause shall be dianosed as an un"nown P;- and the messae
inored.
.s a desin rule- a messae type field should follow the P;- and of a lenth such that the P; and the messae type fit in
the : first bits of the messae.
11.3.2.2 T*e re&t o5 t*e :e&&a4e
The rest of the structure is not more constrained.
The preferred description method is the one described in .nne' 0.
11.3.3 6e&(4n 4$(%el(ne& 5or non &tan%ar% )art&
The uidelines in this subclause apply to non standard parts- such as rest octets- short header broadcast messae or fully
non standard 53 messaes.
11.3.3.1 General
The structure should be as far as possible be such that the analysis can be conducted from beinnin to end. %n other
terms- the conditions determinin the syntactic analysis of a part (e..- tas- lenths) should appear before that part.
The part should be structured as a succession of information elements- each carryin an elementary semantic
information. .n information element should be composed of (possibly) a ta- than (possibly) a lenth indicator- then a
value part.
Tas can be of fi'ed or variable lenth- their e'tent bein analysable from beinnin to end. . typical tain is the one
bit tain- which should preferably used as followsB value H+H indicates that the %2 is no more than the ta bit- and H9H
indicates that the %2 continues at least with the ne't bit.
Cariable lenth tain should be used to distinuish between several possible formats of the element. Ta lenths are
then chosen accordin to pac"in efficiency criteria.
The T field of standard %2s can be presented as a variable tain with only two lenthsB = and < bits.
The lenth indicator can be of fi'ed or variable lenth- their e'tent bein analysable from beinnin to end. %t should
preferably be presented as encodin the lenth in bits of the value part.
The 5 field of standard %2s can be presented as a fi'ed lenth (one octet) lenth indicator which can encode only
lenths multiple of < bits.
The value part can be described as further structured- in a similar way. This can be used to help the readin- and to
cover some presence dependence.
11.4 =an%l(n4 o5 &$)er5l$o$& (n5or:at(on
.ll e>uipment should be able to inore any e'tra information present in an 53 messae- which is not re>uired for the
proper operation of that e>uipment. 7or e'ample- a mobile station may inore the callin party 01; number if that
number is of no interest to the Mobile !tation when a !2T3P messae is received.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(& "elease #
11.4.1 8n5or:at(on ele:ent& t*at are $nne'e&&ary (n a :e&&a4e
The relevant protocol specification may define certain %2s to be under some conditions unnecessary in a 53 messae. .
protocol entity detectin an unnecessary %2 in a received 53 messae shall inore the contents of that %2 for treatin the
messaeD it is not oblied to chec" whether the contents of the %2 are syntactically correct.
11.4.2 <t*er &ynta't(' error&
This clause applies to the analysis of the value part of an information element. %t defines the followin terminoloyB
- .n %2 is defined to be syntactically incorrect in a messae if it contains at least one value defined as HreservedH-
or if its value part violates syntactic rules iven in the specification of the value part.
- %t is not a syntactical error that a type = and type : standard %2 specifies in its lenth indicator a reater lenth
than possible accordin to the value part specificationB e'tra bits shall be inored.
- %t should not be considered a syntactical error if a type = and type : %2 is received with a shorter lenth than
defined in this version of the specification if the %2 is correctly encoded accordin to an earlier version of the
specification.
@ . messae is defined to have semantically incorrect contents if it contains information which- possibly
dependant on the state of the receiver- is in contradiction to the resources of the receiver andJor to the procedural
part.
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(- "elease #
+nne2 + ((n5or:at(7e)0
M.-Ser7('e& arrow %(a4ra:
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(. "elease #
CC MM RR L2 L2 RR MM CC
M obi le Stati on Netw ork
MNC C- SETU P- REQ D L-RAND OM-ACC -REQ/ IN D (CHAN N REQ)
DL- UN IT-D ATA- IN D/ REQ(IMM ASS)
DL-ASS- REQ DL-EST- IN D
DL-EST- CNF UA (CM SERV REQ)
AUTH REQ
AUTH RES
C IPH MODE CMD
C IPH MODE COM
SETU P
C ALL PROC
ASSIGN CMD
ASSIGN COM
ALER T
CONNECT
CONN AC K
MN CC-C ALL-
PR OC-IND
MN CC-ALERT-IND
MNCC -SETUP-CNF
MMC C-EST-C NF
MMCC-SYNC-IND
(res ass)
R R- EST-CNF
RR-SYNK- IN D
(r es ass)
R R- EST-IND
(C M SERV REQ)
R R- SYNC- REQ
(ci ph)
RR -SYNC-CNF
(ci p h)
R R-SYN C-REQ
( res ass)
R R-SYN C-CN F
( res ass)
MMCC -EST-IN D
( SETUP)
MMC C- SYNC- REQ
(r es ass)
MMCC-SYNC-C NF
(r es ass)
MNCC- SETUP- IN D
MNC C-CALL-
PR OC -REQ
MNCC-ALERT-REQ
MNC C- SETU P- RSP
MNC C-SETU P-
COMPL-IN D
DATA FLOW
MMC C- EST-REQ RR -EST- REQ
(CM SERV REQ)
RR-SYNC-IND
( ciph)
SABM (CM SERV REQ)
0igure 2',1 Mobile originated Call Setup' Successful case
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,() "elease #
Mobile Station Network
DATA FLOW
DL-RANDOM-ACC-REQ/IND (CHANN REQ)
DL-UNIT-DATA-IND/REQ (IMMASS)
DL-EST-REQ DL-EST-IND
DL-EST-CONF
UA (PAG RES)
AUTH REQ
AUTH RES
CIPH MODE CMD
CIPH MODE COM
SETUP
CALL CONF
ASSIGN CMD
ASSIGN COM
ALERT
CONNECT
CONN ACK
RR-EST-IND
RR-SYNC-IND
(ciph)
RR-SYNC-IND
(res ass)
MMCC-EST-IND
(SETUP)
MMCC-SYNC-IND
(res ass)
MNCC-SETUP-
IND
MNCC-CALL-
CONF-REQ
MNCC-ALERT-
REQ
MNCC-SETUP-
RES
MNCC-SETUP-
COMPL-IND
RR-EST-REQ
(mob id)
RR-EST-CNF
RR-SYNC-REQ
(res ass)
RR-SYNC-CNF
(res ass)
RR-SYNC-REQ
(res ass)
RR-SYNC-CNF
(res ass)
MMCC-EST-REQ
(mob id)
MMCC-SETUP-REQ
MMCC-EST-CNF
MNCC-CALL-
CONF-IND
MMCC-SYNC-REQ
(res ass)
MMCC-SYNC-CNF
(res ass)
MNCC-ALERT-IND
MNCC-SETUP-CNF
MNCC-SETUP-
COMPL-REQ
SABM(PAG RES)
DL-UNIT-DATA-IND/REQ (PAG REQ)
MM
CC
RR L2 L2 RR MM
CC
0igure 2'%1 Mobile terminated Call Setup' Successful case
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(/ "elease #
Mobile Station Network
DATA FLOW
MNCC-DISC-REQ
MNCC-REL-IND
MMCC-REL-REQ
RR-REL-IND
DISCONNECT
RELEASE
RELEASE COM
CHANN REL
DL-REL-REQ
DL-REL-CNF
DISC
UA
DL-REL-IND
RR-REL-REQ MMCC-REL-REQ
MNCC-DISC-IND
MNCC-REL-REQ
MNCC-REL-CNF
CC
RR L2
CC
MM
MM
RR L2
0igure 2'31 Mobile originated4 Call "elease and Channel "elease' Successful case
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,(# "elease #
Mobile Station
Network
RR-EST-REQ
(LOC UPD)
DL-RANDOM-ACC-REQ/IND (CHANN REQ)
DL-UNIT-DATA-IND/REQ (IMMASS)
DL-EST-REQ SAHM(LOC UPD) DL-EST-IND
DL-EST-CNF UA (LOC UPD)
AUTH REQ
AUTH RES
CIPH MODE CMD
CIPH MODE COM
LOC UPD ACC
REAL COM
CHANN REL
DISC
UA
DL-REL-REQ
DL-REL-CNF
DL-REL-IND
RR-EST-IND
(LOC UP)
RR-SYNC-REQ
(ciph)
RR-SYNC-CNF
(ciph)
RR-REL-REQ
CC MM
RR L2
CC MM
RR L2
0igure 2'&1 9ocation updating' Successful case
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,,( "elease #
Mobile Station Network
DATA FLOW
DATA FLOW
HANDO CMD
DL-SUS-REQ (local)
DL-REL-CNF (local)
PHYS INFO
DL-RES-REQ
DL-EST-CNF
SAHM
UA
HANDO COM
DL-EST-IND
BS1
BS2
CC
MM RR
L2
CC
MM RR
L2
0igure 2'-1 Cando3er' Successful case
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,,, "elease #
Mobile Station Network
MNX-SPECIFIC-REQ
(1MSG (X))
MMX-EST-REQ RR-EST-REQ
(CMSERV REQ)
RR-EST-CNF
MMX-EST-CNF RR-SYNC-IND
(ciph)
MMX-DATA-REQ
(1MSG (X))
MMX-DATA-DND
(2MSG (X))
RR-DATA-RE1
(1 MSG (X))
RR-DATA-DND
(2MSG (X))
MMX-SYNC-IND
(res ass)
MMX-DATA-REQ
(MSG (X))
MMY-EST-REQ
MMY-EST-CNF
MMY-DATA-REQ
(1 MSG (Y))
RR-SYNC-IND
(res ass)
RR-DATA-REQ
(MSG (X))
RR-DATA-REQ
(1MSG (Y))
CHANN REQ
IMMASS
DL-EST-CNF
UA (CMSERV REQ)
AUTH REQ
AUTH RES
CIPH MODE CMD
CIPH MODE COM
1 MESSAGE (X)
2 MESSAGE (X)
ASSIGN CMD
ASSIGN COM
MESSAGE (X)
MESSAGE OF TRANSACTION X
OM SERV REQ
(serv 1)
OM SERV ACC
(serv 2)
1 MESSAGE (Y)
MESSAGE OF TRANSACTION X & Y
RR-EST-IND
(CMSERV REQ)
NR-SYNC-REQ
(ciph)
RR-SYNC-CNF
(ciph)
RR-DATA-IND
(1 MSG (X))
RR-DATA-REQ
2 MSG (X))
RR-SYNC-REQ
(res ass)
RR-SYNC-CNF
(res ass)
RR-DATA-IND
(MSG (X))
MMX-DATA-REQ
2 MSG (X))
MMX-SYNC-REQ
(res ass)
MMX-SYNC-CNF
(res ass)
MMX-DATA-IND
(MSG (X))
MMXX-EST IND
(1 MSG (X))
RR-DATA-IND
(1MSG (Y))
MMY-EST-IND
(1MSG(Y))
T
r
a
n
s
a
c
t
i
o
n

Y

s
t
a
r
t
e
d
T
r
a
n
s
a
c
t
i
o
n

X

s
t
a
r
t
e
d
IM-EST-REQ
(CM SERV REQ)
IM-EST-IND
(CMSERV REQ)
SABM(CMSERV REL)
MMY-SPECIFIC-REQ
(1MSG (Y))
CM MM RR L2 CM
MM
RR
L2
0igure 2'.1 :stablishment of parallel transactions !General 3iew$
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,,% "elease #
Mobile Station Network
MMG-#L-#A
MM>-#L-#A
##-#L-8.6
La&t :e&&a4e o5 &)e'(5(' Proto'ol (2)
MSS+G <- T#+.S+/T8<.S G N >
MSS+G <- T#+.S+/T8<.S >
La&t :e&&a4e o5 &)e'(5(' Proto'ol (y)
/=+.. #L
6L-#L-#A
6L-#L-/.-
68S/
U+
6L-#L-8.6
MMG-#L-#A
MM>-#L-#A
Tran&a't(on
relea&e%
Tran&a't(on
relea&e%
/*annel
relea&e%
/M MM ##
L2 /M MM
## L2
0igure 2')1 "elease of parallel transactions !General 3iew$
3GPP
3GPP TS %&'(() *#'('( !%((#+,%$ ,,3 "elease #
+nne2 ; ((n5or:at(7e)0
6e&'r()t(on o5 /S..1
The oal of the notation described hereafter is to describe the structure of the syntactically correct messaes for a iven
sinallin protocol- or of part of such messaes. The notation addresses the cases where the concrete messaes are
binary strins. The notation allows to describe sets of strinsB the structure of a messae defined a protocol defines a set
of allowable bit strins. %t also allows to put labels on parts of strins that follow a iven structure.
One aspect of the specification of messae set is to define the set of strins that are acceptable as when received. .ll the
strins that cannot be reconi(ed as syntactically correct messaes are to be rejected for syntactical reasons. %n many
cases- only a subset of this set are allowed to be sent. The notation allows also to distinuish the set of the strins that
can be sent and the set of strins that are reconi(ed as syntactically correct.
.nother aspect of the specification of messaes is the splittin of an acceptable strin in a number of sub@strins that
will be use to derive the e'act sinificance of the messae. The notation provides this function by labellin sub@strins.
These labels can then in turn be used in te'tual or formal semantic descriptions which are not covered in the present
document.
The notation described here could be enhanced in the future- with the addition of new rules.
;.1 T*e ;a&(' #$le&
The followin rules (09 to 0:) form the core part of the notation- more or less directly inherited from 0&7. /ules 0? to
0< add what is needed in addition to encode the rest octet parts of fi'ed lenth messaes as defined in
3GPP T! *=.++< F:G.
/ule .9 is not needed to describe sets of strins at this stae. %t is the one allowin to label parts of messaes.
;.1.1 /ore #$le&
;.1.1.1 #$le ;10 ;(t&
. Hbit strinH is an ordered se>uence of symbols- each belonin to a two@value set.
The character H+H and H9H are used to indicate one bit- respectively of one or the other value.
7ormally- the notations V + W and V 9 W denote each a set composed of a sinle bit strin of a sinle bit- of different
values.
%n addition the word HbitH denotes the set of the two 9@bit lon strins- namely + and 9.
;.1.1.2 #$le ;20 .$ll Str(n4
Khere needed- the word HnullH call be used to indicate the null strin- i.e.- the strin of no symbols.
7ormally- the notation V null W denote the set composed of a sinle bit strin- the empty strin.
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,,& "elease #
;.1.1.3 #$le ;30 /on'atenat(on
. succession of two strin descriptions describe the concatenation of the strins.
More formallyB a succession of two strin descriptions describes the strins obtained by concatenation of one strin
ta"en in the subset described by the first strin description and then one strin ta"en in the subset described by the
second strin description. The rule e'tends to any number of strin descriptions.
7or instanceB
++
This denotes the set composed of the sinle bit strin of lenth * composed of two (eros.
;.1.1.4 #$le ;40 /*o('e
. list of choices is noted usin as separator the character HXH. .n alternative notation uses instead the word HorH (this is
not used in the present document).
&OT2B .n idea is to allow not to used strane characters- by ivin in each case a verbose e>uivalent. This is not
done systematically yet in the present document.
7ormallyB the notation . X 0- where . and 0 are strin set descriptions- describes the set of the strins which are in the
set described by . or in the set described by 0- that is the union of sets described by . and 0.
The concatenation has a hiher precedence than the choice.
2'amplesB
++ X +9
This indicates that bit strins ++ and +9 are part of the set (9+ and 99 are not).
+ X 9
;enotes the same set as HbitH.
The characters HTH and HUH are used for delimitin a strin set description from what follows andJor precedes.
+ T+X9U
This indicates the same set of bit strins as in the previous case.
Precedence e'ampleB
9+ X 99
9 +X9
0ecause of the priority rule- the two descriptions are not e>uivalent- the second notin the set (9+- 9).
%t is allowed that the different sets in a choice have non null intersections. To allow messae decodin- a rule must then
be iven to choose the branch. The rule is that any matchin set can be chosen (the concatenation is a true set union).
%n practice- it is preferable to have non intersectin choice sets. Moreover- the ability to select the branch to ta"e rapidly
is important for obtainin simple messae decoders. 2'cept for stron reasons- a desin should only include choice
construction that can be rewritten usin only constructions matchin the pattern Ta9 s9 Xa* s*U where a9 and a* are
non@intersectin sets of strins of the same non@null lenth. . tolerable deroation is to use intersectin an.
2'amplesB
T9++ '' X ++9 ((U is acceptable.
T++ '' X +9+ yy X +99 ((U is acceptable- since it can be rewritten T++ '' X +9 T+ yy X 9 ((UUU.
TT++X+9X9+U '' X T++X99U yyU is not recommended (the start ++ is ambiuous).
%n practice this covers fi'ed lenth tain (li"e tain by an %2%- or 9@bit tain in rest octets)- and also non@
intersectin variable lenth tain as used for instance in the fre>uency list %2 (ta list such as +- 9++- 9+9- 99+- 999++-
999+9- 9999+- 99999- where no ta is the start of another one).
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,,- "elease #
;.1.1." #$le ;"0 .a:(n4
The characters HYH and HZH are used to delimit a reference to the description of a strin set. This can be used inside a
strin set description- to refer to a strin set described elsewhere.
7or compilability- the name must be used somewhere else to define the correspondin strin set. 7or a simple
description- the description of the reference could be done by normal te't.
The name- that is the part se>uence of characters between HYH and HZH must not be empty- and is constituted freely of
characters- with the e'ception of HYH and HZH. 1ase is not sinificant- nor are headin or tailin spaces. .ny succession
of space characters is treated as a sinle character. To avoid difficulties with more advanced rules- the use of the
characters HBH- HSH- H(H and H)H should be avoided. More enerally- it is not recommended to use many other characters-
such as HYH for instance. The space character can (and should[) be used- to allow a ood leibility for human beins.
2'ampleB
Ybit pairZ
;.1.1.! #$le ;!0 6e5(n(t(on
. reference followed by the character se>uence HBBSH followed by a strin set description is used to associate the
description with the reference- terminated when needed to separate it from a followin definition and when
compilability is loo"ed for- by a semi@colon # D.
/ecursive definition is allowed- e..- the reference can appears on the riht hand side of the HBBSH. To avoid too much
difficulties for would@be@compilers- only tail recursivity should be used- i.e.- a recursive term should appear only as the
last term of a definition.
2'amplesB
Ybit pairZ BBS ++ X +9 X 9+ X 99 D
This could have been noted as wellB
Ybit pairZ BBS T++ X +9 X 9+ X 99U D
or
Ybit pairZ BBS T+X9U T+X9U D
/ecursive e'ampleB
Yall bit strinsZ BBS null X T T+ X 9U Yall bit strinsZU D
.nother recursive- but not tail@recursive (and then not recommended) e'ampleB
Yall bit strinsZ BBS null X TYall bit strinsZ T+ X 9UU D
;.1.2 S)are )art&
7or the purpose of messae description it is in many cases needed to specify differently the set of bit strins that are
acceptable when received and the correspondin set of bit strins which may be sent. The second set is included in the
first. . first e'ample are the spare parts.
&otations related to spare parts are different in nature from the bit strin set description seen so far. They define two
sets as the same time- the sent set and the received set. . construction rule of eneral application will be defined in
advanced rules. 7or the moment- only two ad@hoc constructions are described.
;.1.2.1 #$le ;70 S)are ,(t&
The followin constructionB
Yspare bitZ
describes a + when emitted and a bit (+ or 9) in reception.
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,,. "elease #
;.1.2.2 #$le ;E0 Pa%%(n4 ,(t&
.n issue specific to the G!M radio interface protocols is that in some cases the messaes cannot ta"e arbitrary lenths.
Paddin is then necessary to fill up the messae up to the desired lenth. Moreover- the paddin uses a particular
se>uence of bits- of fi'ed position- i.e.- the value of a paddin bit depends on its position relative to the start of the
messae. The paddin se>uence is protocol@specific. %n most cases it is constituted of all + values- in which case the
followin notation is of no use. %n the case of G!M +=.+<- the paddin se>uence is the repetition of octet ++9+9+99-
startin on an octet boundary.
The special notations H5H and HAH are used to denote the respectively the bit value correspondin to the paddin spare
bit for that position- and the other value.
The notations H+H- H9H- HnullH- H5H and HAH are the only terminals in 1!&.9.
Paddin spare bits are bits which are set to the indicated value in emission whereas in reception any bit strin is
acceptable. The followin notationB
Yspare 5Z
describes a bit which has a loical value 5 in emission- and is a bit (+ or 9) in reception.
The term Yspare paddinZ denotes the re>uired paddin spare bits needed to fill up the messae. The construction can
be developed only partially from the rules described so far- because the lenth limitation does not appear in the
followin descriptionB
Y spare paddinZ BBS Yspare 5Z Tnull X Y spare paddinZUD
;.1.3 Pre%e5(ne% &et&
The notation allows a modular description of the messaes. This means in particular the possibility to build a library of
bit strin set definitions to be used wherever needed. The followin is an e'ample of an elementary library- which could
be specified once and can be used in other specifications without bein redefined.
YbitZ BBS +X9 D
Ybit (9)Z BBS YbitZD
Ybit (*)Z BBS YbitZ YbitZD
Ybit (3)Z BBS Ybit (*)Z YbitZD
Ybit (=)Z BBS Ybit (3)Z YbitZD
Ybit (8)Z BBS Ybit (=)Z YbitZD
Ybit (:)Z BBS Ybit (8)Z YbitZD
Ybit (?)Z BBS Ybit (:)Z YbitZD
YoctetZ BBS Ybit (?)Z YbitZD
Yhalf octetZ BBS Ybit (=)ZD
Yspare half octetZ BBS Yspare bitZYspare bitZYspare bitZYspare bitZD
Yspare paddinZ BBS Yspare 5Z Tnull X Yspare paddinZUD
Yoctet strin(i)Z BBS YoctetZ
(i)
D @@ for any positive or null inteer i
Ybit(i)Z BBS YbitZ(i)D @@ for any positive or null inteer %
Ybit strinZ BBS bitEED
Yoctet strinZ BBS YoctetZEED
.<T 10 T*e %e5(n(t(on o5 4ener(' 'on&tr$'t(on& &$'* a& O,(t &tr(n4(()P (& &o:ew*at '$:,er&o:e w(t* only t*e ,a&('
r$le&. More a%7an'e% r$le& wo$l% allow a :$'* :ore 'o:)a't notat(on.
.<T 20 T*e $&e o5 t*e '*ara'ter& Q(Q an% Q)Q w(t*(n a re5eren'e (& %one 'on&(&tently w(t* )otent(al a%7an'e% r$le&.
.<T 30 T*(& ,a&(' l(,rary (& not e2*a$&t(7e an% 'an ,e e2ten%e% w*en t*e nee%& ar(&e.
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,,) "elease #
;.1.4 La,ell(n4 Part&
;.1.4.1 #$le +10 La,el&
;elimited names as defined by /ule 0: identify sets of sub strins. %n many cases this can be used within the conte't of
a messae to refer to the specific part of the messae. Aowever- this is not of eneral application- since it may happen
that two parts of a messae follow the same structure- and economy of notation re>uires that the structure is described
but once.
The eneral synta' that follows allows to refer to a part inside a descriptionB
Yname1 B string description>
7or the definition of strin sets- this is e>uivalent to the strin description bein used alone.
The name used as a label can be built accordin to the rules applicable to parenthesed references.
2'amplesB
YTa B +++ Z
Y7ield B Y7ield typeZZ
Y7ield B octetZ
The third e'ample shows the use of a non parentheses reference to obtain a more eleant e'pression than- for instance-
the second e'ample. .t this stae- labels has no use for describin messae synta'- but can be used to refer to the
correspondin part of the strin- e..- in the description of the messae specifyin the relationship between the
syntactical content and the semantical contents of the messae- or to associate properties with effective sub@strins in
effective messaes (rather than with sets of sub strins). !yntactical use of the semantical identifier are presented in
more advanced rules.
The same name may appear in several places. ;esiners have to be careful to use non ambiuous names if
non@ambiuous reference is desired.
;.1." Goo%(e&
;.1.".1 #$le G10 /o::ent&
1omments can be added- startin with the term H@@H and ended by the end of line. 1omments can be used in particular to
indicate the section where a particular description can be found.
;.2 +%7an'e% r$le&
;.2.1 #$le +20 2)onent notat(on
.n arithmetic e'pression used as e'ponent after a delimited strin description is used to indicate repetitions.
. numerical e'pression between parentheses indicates a fi'ed number of repetitions.
YoctetZ BBS T+ X 9U
(<
) D
is e>uivalent to
YoctetZ BBS T+ X 9U T+ X 9U T+ X 9U T+ X 9U T+ X 9U T+ X 9U T+ X 9U T+ X 9U D
This could also be writtenB
YoctetZ BBS bit(<) D
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,,/ "elease #
Khen the e'ponent is neative or e>ual to +- the e'ponentiated construction is e>uivalent to the null strin.
.n e'ample of a common construction is the followinB
Yname B bit(8)Z
!imple arithmetic- usin numbers- terms HIH- H@H- HEH and HJH- and parentheses are allowed in e'pressions.
2'ampleB
Yoctet strin(=+)Z BBS YoctetZ
(<E(=I9))
D
. star used alone between parentheses- or a double star- indicates a finite- possibly null- but indeterminate- number of
repetitions. (The star used as an e'ponent can be understood also as meanin the union of all the sets obtained by
replacin the star by (ero or some positive inteer).
Yall bit strinsZ BBS T+ X9U(E) D
Yall bit strinsZ BBS T+ X9UEE D
This allows a shorter notation of recursive constructions such asB
Yall bit strinsZ BBS T+X9U Yall bit strinsZ X nullD
. shorter notation is allowed when the e'pression has a sinle term- consistin of a star followed by the termB
YoctetZ BBS T+ X 9UE< D
Yoctet strin(=+)Z BBS YoctetZE(<E(=I9)) D
Yall bit strinsZ BBS bitEED
.pplication noteB
The indefinite e'ponent is usually combined with some mean to indicate to the decoder the end of the repetition.
;ifferent techni>ues e'ist- such as indicatin in a previous field the number of repetitions. .nother techni>ue is one@bit
tain- an e'ample of which followsB T9 YitemZUEE +.
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,,# "elease #
+nne2 / ((n5or:at(7e)0
GP#S-Ser7('e& &e9$en'e %(a4ra:
%nstead of providin a complete set of all scenarios- the intention of this clause is to provide some typical e'amples. %t
shall be noted- that within the fiures only those parameters of the P;3s and the service primitives are shown- which
are needed for a eneral understandin of the e'amples. 7urthermore durin the e'amples below (e'cept 1.9?) no cell
re@selection ta"es place.
3GPP
3GPP TS %&'(() *#'('( !%((#+(#$ ,%( "elease #
C.1 ATTACH, GPRS only, MS unknown in te network
GMM/2G@.TT.1A@ /2O
F.ttach type-
/2.;L@timer-
!T.&;0L@timer G
!T./T Tattach
55@3&%T;.T.@/2O
FP;3S.ttach /e> (
%M!% or T55%plus/.%)-
oldT55%-1ipherSoff G
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- T55%-
/.%-1%G
55@3&%T;.T.@%&;
FP;3S.ttach /e> (
%M!% or T55%plus/.%)-
oldT55%- 1%G
55GMM@.!!%G&@/2O
F$c- .lorithmG
!T./T Tauth
55@3&%T;.T.@/2O
G//@;.T.@@/2O
!TOP Tauth
F P;3S.uth@1ipher@
/e> (.l- /.&;-..)-
oldT55%- 1ipherSoff G
F551@3%-
;/M- 15M-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
55@3&%T;.T.@%&;
FP;3S.uth@1ipher@
/e> (.l.- /.&;-\)
G
55@3&%T;.T.@/2O
FP;3S.uth@1ipher@
/esp (!/2!)-
oldT55%-1ipherSoff G
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- oldT55%G
55@3&%T;.T.@%&;
FP;3S.uth@1ipher@
/esp (!/2!)-
oldT55% G
F$c- .lorithmG
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
55GMM@.!!%G&@/2O
!T./T Tident
55@3&%T;.T.@/2O
F P;3S
%dentification /e>-
oldT55%- 1ipherSoff G
G//@;.T.@@/2O
F551@3%-
;/M- 15M-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
55@3&%T;.T.@%&;
FP;3S
%dentification /e>G
!TOP Tident
55@3&%T;.T.@/2O
FP;3S%dentification@
/esp (%M!%)-
oldT55%-1ipherSoff G
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- T55%G
55@3&%T;.T.@%&;
FP;3S%dentification@
/esp (%M!%)-
oldT55% G
The oldT55% may be a
5ocal T55%- or a
7orein T55%- or a
/andom T55%
%M!% fetched if
@ &o GP/! MM 1onte't e'ists- and
@ .ttach /e>uest without %M!%
The networ" starts the
authentication toether with settin
the cipherin mode.
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%, "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.1 #$ont%&'( ATTACH, GPRS only, MS unknown in te network
!T./T T.ttach !TOP Tattach
GMM/2G@.TT.1A@ 1&7
F P5M&Ps MT caps- .ttach@ typeG
!TOP Tattach
55@3&%T;.T.@/2O
FP;3S.ttach .ccept(
newT55%)-
oldT55%-1ipherSon G
G//@;.T.@@/2O
F551@3%- oldT55%-
!.P%Ssinallin G
G//@;.T.@%&;
F551@3% G
55@3&%T;.T.@%&;
FP;3S.ttach .ccept(
newT55%) G
55GMM@.!!%G&@/2O
F/'B oldT55% or
newT55%
TMB new T55% G
55GMM@.!!%G&@/2O
F/'B oldT55% or
newT55%
TMB newT55% G
55@3&%T;.T.@/2O
FP;3S.ttach complete-
newT55%-1ipherSon G
G//@;.T.@/2O
F551@3%-
!.P%Ssinallin G
G//@;.T.@%&;
F551@3%- newT55% G
55@3&%T;.T.@%&;
FP;3S.ttach 1omplete-
newT55%G
F unassin oldT55% G
55GMM@.!!%G&@/2O
GMM//@.!!%G&@/2O
F/'B oldT55% or
newT55%
TMB new T55% GG
/2!T./T
/2.;L@timer
/2!T./T
/2.;L@timer
55GMM@.!!%G&@/2O
F unassin oldT55% G
GMM//@.!!%G&@/2O
F unassin oldT55% G
. new T55%
is assined
%mplementation optionB
3nassinment of old T55% e..
@ with reception of first 551 frame
usin the new T55%
@ e'piry of appropriate timer
G//@%&%T;.T.@@/2O
F551@M%; G
G//@3&%T;.T.@%&;
F 551@M%;- T55%- 1% G
G//@3&%T;.T.@%&;
F 551@M%; G
G//@3&%T;.T.@/2O
F 551@M%; G
2'chane of new %&P3T
O7!2T value
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%% "elease /
C.) ATTACH, GPRS only, MS known in te network
GMM/2G@.TT.1A@/2O
F.ttach typeG
!T./T Tattach
55@3&%T;.T.@/2O G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- oldT55%
1%G
55@3&%T;.T.@%&;
FP;3S.ttach /e> (
1$!&)-
oldT55%- 1%G
. new T55%
is assined
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
FP;3S.ttach /e> (
T55%plus/.%)-
oldT55%-1ipherSoff G
!T./T Tauth
55@3&%T;.T.@/2O
G//@;.T.@@/2O
!TOP Tauth
F P;3S.uth@1ipher@
/e>( .loritm)-
oldT55%- 1ipherSoff G
F551@3%-
;/M- 15M-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
55@3&%T;.T.@%&;
FP;3S.uth@1ipher@
/e> (.lorithm) G
55@3&%T;.T.@/2O
FP;3S.uth@1ipher@
/esp ( )-
oldT55%-1ipherSoff G
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- oldT55%G
55@3&%T;.T.@%&;
FP;3S
.uth@1ipher/esp-
oldT55% G
55GMM@.!!%G&@/2O
F $c- .lorithm G
to enable 551 to decipher
subse>uent ciphered
sinallin messaes
received 1$!& matches-
start of cipherin without
authentication
F $c- .lorithm G
55GMM@.!!%G&@/2O
G//@%&%T;.T.@@/2O
F551@M%; G
G//@3&%T;.T.@%&;
F 551@M%;- T55%- 1% G
G//@3&%T;.T.@%&;
F 551@M%; G
G//@3&%T;.T.@/2O
F 551@M%; G
2'chane of new %&P3T
O7!2T value
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%3 "elease /
C.) #$ont%&' ATTACH, GPRS only, MS known in te network
!T./T Tattach !TOP Tattach GMM/2G@.TT.1A@
1&7
F P5M&Ps MT caps- .ttach@ typeG
55@3&%T;.T.@/2O
FP;3S.ttach .ccept(
newT55%)-
oldT55%- 1ipherSon G
G//@;.T.@/2O
F551@3%-
!.P%Ssinallin G
G//@;.T.@%&;
F551@3% G
55@3&%T;.T.@%&;
FP;3S .ttach .ccept(
new T55%) G
55GMM@.!!%G&@/2O
55GMM@.!!%G&@/2O
F/'B oldT55% or newT55%
TMB new T55% - $c-
.lorithm G
!TOP Tattach
F /'B old or newT55%
TMB new T55% G G
55@3&%T;.T.@/2O
FP;3S.ttach complete-
newT55%- 1ipherSon G
G//@;.T.@/2O
F551@3%-
!.P%Ssinallin G
G//@;.T.@%&;
F551@3%- newT55% G
55@3&%T;.T.@%&;
FP;3S.ttach 1omplete-
newT55%G
F unassin oldT5% G
55GMM@.!!%G&@/2O
GMM//@.!!%G&@ /2O
/2!T./T
/2.;L@timer
/2!T./T
/2.;L@timer
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
55GMM@.!!%G&@/2O
F unassin oldT55% G
GMM//@.!!%G&@/2O
F unassin oldT55% G
F$c- .lorithm G
F /'B old or newT55%
TMB new T55% G G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%& "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.* MS initiate& +"TACH, GPRS only
GMM/2G@;2T.1A@ /2O
F;etach@type-
normal@detach G !T./T Tdetach
55@3&%T;.T.@/2O
FP;3S;etach /e>-
T55%- 1ipherSon G
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- T55%
1%G
55@3&%T;.T.@%&;
FP;3S;etach /e>-
T55%- 1%G
!TOP Tdetach
GMM/2G@;2T.1A@ 1&7
F ;etach@ typeG
55@3&%T;.T.@/2O
FP;3S;etach .ccept
T55%- 1ipherSon G
G//@;.T.@@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
55@3&%T;.T.@%&;
FP;3S;etach .cceptG
55@3&%T;.T.@/2O
F P;3S;etach /e>-
T55%- 1ipherSon G
G//@;.T.@/2O
F 551@3%-
!.P%Ssinallin G
G//@;.T.@%&;
F 551@3%- T55%
1% G
55@3&%T;.T.@%&;
FP;3S;etach /e>-
T55%- 1%G
C., P-."R/-00 +"TACH, GPRS only
55GMM@.!!%G&@/2O
F unassin T55%G
.ll 551 lin"s are aborted
!&!M@;2.1T%C.T2
@%&;
F G
GMM!M@
/252.!2 @%&;
F G
55GMM@.!!%G&@/2O
F unassin T55%G
!&!M@;2.1T%C.T2
@%&;
F T55% G
GMM!M@
/252.!2@%&;
F T55% G
GMM/2G@;2T.1A@ /2O
F;etach@type-
power off G
55GMM@.!!%G&@/2O
F unassin T55%G
!&!M@;2.1T%C.T2
@%&;
F T55% G
GMM!M@
/252.!2@%&;
F T55% G
55GMM@.!!%G&@/2O
F unassin T55%G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%- "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.1 !etwork initiate& +"TACH, GPRS only
GMM/2G@;2T.1A@
/2O
F;etach@type-
normal@detach G
55@3&%T;.T.@/2O
FP;3S;etach .ccept-
T55%- 1ipherSon G
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- T55%
1%G
55@3&%T;.T.@%&;
FP;3S;etach .ccept-
T55%- 1%G
!TOP Tdetach
GMM/2G@;2T.1A@
1&7
F ;etach@ typeG
55@3&%T;.T.@/2O
FP;3S;etach /e>-
T55% - 1ipherSonG
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
55@3&%T;.T.@%&;
FP;3S;etach /e>G
55GMM@.!!%G&@/2O
F unassin T55%G
.ll 551 lin"s are aborted
!&!M@;2.1T%C.T2
@%&;
F G
GMM!M@
/252.!2 @%&;
F G
55GMM@.!!%G&@/2O
F unassin T55%G
!&!M@;2.1T%C.T2
@%&;
F T55% G
GMM!M@
/252.!2@%&;
F T55% G
!T./T Tdetach
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%. "elease /
C.2 P+P Conte3t A$ti4ation, MS 5nitiate&, MS alrea&y atta$e&
G//@;.T.@/2O 55@3&%T;.T.@/2O
FP;3S.ctivate
P;P 1onte't /e> G
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%- T55%
1%G
55@3&%T;.T.@%&;
F!M@P;3- \..G
G//@;.T.@@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
55@3&%T;.T.@%&;
FP;3S .ctivate
P;P 1onte't
.ccept G
!TOP TP;P .ct
F &!.P%- Oo! G
F T55%- &!.P%- Oo! G
!&!M@.1T%C.T2
@%&;
!&!M@.1T%C.T2@
%&;
!T./T TP;P& act
&o 551
lin"
e'ists
yet-
establish
a lin"
and
e'chane
M%;
551 lin"
e'ists
already-
only M%;
e'chane
!M/2G@ P;P@.1T%C.T2@1&7
F P;P@type- P;P@address-
Oo!- &!.P%G
!&!M@.1T%C.T2@
/!P
!&!M@
.1T%C.T2@1&7
F G
F T55% G
!TOP TP;P& act
55@M%;@/2O
F T55%- !&;1P M%; G
55@M%;@1&7
F T55%-!&;1P@M%; neotiated- &*+9 G
55@M%;@%&;
F T55%- !&1P@M%;- &*+9 G
55@M%;@/!P
F T55%- !&1P@M%; neotiatedG
G//@;.T.@/2O
F 551@M%;-
!.P%Sdata G
G//@;.T.@%&;
F551 M%;G
G//@;.T.@%&;
F 551 M%;- \..G
F551 M%;- prioritySdataG
55@ 2!T.05%!A@/2O
F T55%- !&;1P M%; re>uested G
55@2!T.05%!A@ 1&7
F T55%- !&;1P@M%; neotiated- &*+9 G
55@2!T.05%!A@ %&;
F T55%- !&1P@M%; re>uested &*+9G
55@ 2!T.05%!A@/!P
F T55%- !&1P@M%; neotiated G
G//@;.T.@/2O
F 551@!.0M-
!.P%Sdata G
G//@;.T.@%&;
F551 3.G
G//@;.T.@%&;
F 551 !.0M- .....G
F551 3.-
!.P%SdataG
551 lin" e'ists
already- no
M%; e'chane
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
!M/2G@P;P@ .1T%C.T2@/2O
F P;P@type- P;P address- Oo!-
&!.P%- GG!& name-
.1$J3&.1$ G
!T./T TP;Pact
GMM!M@
2!T.05%!A@/2O
GMM!M@
2!T.05%!A@1&7
GMM!M@3&%T
;.T.@%&;
FP;3S .ctivate
P;P 1onte't /e> G
GMM!M@3&%T
;.T.@/2O
F!M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
F!M@P;3- \.. G
55@3&%T;.T.@/2O
F P;3S .ctivate
P;P 1onte't
.ccept G
F!M@P;3- \..G
GMM!M@3&%T
;.T.@/2O
the GP/! .ttach procedure shall be
performed in case the M! is not already
GP/! attached
M%; re@neotiates re>uires lin" reset
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%) "elease /
C.6 P+P Conte3t A$ti4ation, !etwork 5nitiate&
//@;.T.@/2O
F 551@3%-
!.P%Ssinallin G
G//@;.T.@%&;
F 551@3%- \.. G
F P;P@ type- P;P address-
Oo!- &!.P%- GG!& name-
.1$J3&.1$ G
G//@;.T.@@/2O
F 551@3%-
!.P%Ssinallin G
G//@;.T.@%&;
F 551@3% G
!T./T TP;P& act
!M/2G@P;P@.1T%C.T2@%&;
!TOP TP;P& act
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
1ontinued as normal M! initiated P;P conte't activation
55@3&%T;.T.@/2O
F P;3S /e>uest@
P;P 1onte't@
.ctivationG
F!M@P;3- \..G
GMM!M@3&%T
;.T.@/2O
!M/2G@P;P@.1T%C.T2@/2O
F P;P@type- P;P@address
Oo!- &!.P%-
GG!& name-
.1$J&.1$ G
55@3&%T;.T.@%&;
F!M@P;3- \..G
GMM!M@3&%T
;.T.@%&;
FP;3S .ctivate
P;P 1onte't /e> G
55@3&%T;.T.@/2O
FP;3S.ctivate
P;P 1onte't /e> G
!M/2G@P;P@ .1T%C.T2@/2O
F P;P@type- P;P address- Oo!-
&!.P%- GG!& name-
.1$J3&.1$ G
!T./T TP;Pact
GMM!M@3&%T
;.T.@/2O
F!M@P;3- \.. G
55@3&%T;.T.@%&;
FP;3S /e>uest@
P;P 1onte't@
.ctivationG
GMM!M@3&%T
;.T.@%&;
F!M@P;3- \.. G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%/ "elease /
C.7 Anonymous P+P Conte3t A$ti4ation
#8oi&'
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,%# "elease /
C.9 P+P Conte3t +ea$ti4ation, MS initiate&
!M/2G@P;P@;2.1T%C.T2@/2O
F &!.P%(s) G
!T./T TP;P deact
G//@;.T.@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F 551@3%- T55%- 1% G
!TOP TP;P deact
!M/2G@P;P@;2.1T%C.T2@1&7
F &!.P%(s) G
F P;3S;eactivate
P;P 1onte't
.ccept G
G//@;.T.@@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F551@3%G
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
55@3&%T;.T.@/2O
F P;3S;eactivate
P;P 1onte't /e> G
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@/2O
55@3&%T;.T.@%&;
F P;3S;eactivate
P;P 1onte't
.ccept G
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
55@3&%T;.T.@%&;
F P;3S
;eactivate P;P
1onte't /e> G
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
55@3&%T;.T.@/2O
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@/2O
F &!.P%(s) G
!&!M@;2.1T%C.T2
@%&;
!&!M@;2.1T%C.T2
@/2!
F T55% G
F T55% G
55@/252.!2@1&7
55@/252.!2@/2O
F local T55% G
55@/252.!2@17&
F T55% G
F G
!&!M@;2.1T%C.T2
@/!P
F &!.P%(s) G
!&!M@;2.1T%C.T2
@%&;
55@/252.!2@/2O
F local T55% G
&oteB
The release is only re>uested- if the 551 lin" is not used
by any other P;P conte't usin ac" mode
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3( "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.1: P+P Conte3t +ea$ti4ation, network initiate&
!T./T TP;P& deact
!TOP TP;P& deact
!M/2G@P;P@;2.1T%C.T2@%&;
F &!.P%(s)G
G//@;.T.@@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@%&;
F 551@3%- T55%- 1% G
G//@;.T.@%&;
F 551@3% G
G//@;.T.@/2O
F 551@3.-
!.P%Ssinallin G
55@3&%T;.T.@%&;
F P;3S;eactivate
P;P 1onte't
/e>uestG
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
55@3&%T;.T.@/2O
F P;3S;eactivate
P;P 1onte't
.112PT G
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@/2O
55@3&%T;.T.@/2O
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@/2O
F P;3S;eactivate
P;P 1onte't
/2O32!T G
55@3&%T;.T.@%&;
F P;3S
;eactivate P;P
1onte't .ccept G
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
!M/2G@P;P@;2 .1T%C.T2@1&7
F&!.P%G
!M/2G@P;P@;2 .1T%C.T2@/2O
F&!.P%G
F &!.P%(s) G
!&!M@;2.1T%C.T2
@%&;
!&!M@;2.1T%C.T2
@/!P
F T55%- G
F T55% G
55@/252.!2@1&7
55@/252.!2@/2O
F local T55% G
55@/252.!2@17&
F T55% G
F G
!&!M@;2.1T%C.T2
@/!P
F &!.P%(s) G
!&!M@;2.1T%C.T2
@%&;
55@/252.!2@/2O
F local T55% G
&oteB
The release is only re>uested- if the 551 lin" is not
used by any other P;P conte't usin ac"Ped mode
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3, "elease /
C.11 P+P Conte3t Mo&ifi$ation
!T./T TP;P& mod
F T55%- &!.P%(s) I
newOo!(s) G
!&!M@MO;%7L@%&;
!&!M@MO;%7L@/2!
F T55% G
!TOP TP;P& mod
!M/2G@P;P@MO;%7L@%&;
F &!.P%(s)JOo!(s) G
55@ 2!T.05%!A@%&;
F T55%- !&;1P M%; re>uested- &*+9 G
55@2!T.05%!A@/!P
F T55O- !&;1P@M%; neotiated G
55@ 2!T.05%!A@1&7
F T55%- !&1P@M%; neotiated- &*+9G
F &!.P%(s) I
newOo!(s) G
!&!M@MO;%7L@%&;
!&!M@MO;%7L@/!P
F G
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
G//@;.T.@%&;
F 551@3%- T55%- 1% G
G//@;.T.@%&;
F 551@3.- T55%- 1% G
G//@;.T.@%&;
F 551@3%- T55%- 1% G
G//@;.T.@@/2O
F551@3%-
!.P%SsinallinG
G//@;.T.@@/2O
F551@;%!1-
!.P%SdataG
G//@;.T.@@/2O
F551@!.0M-
!.P%SdataG
G//@;.T.@%&;
F 551@3% G
G//@;.T.@%&;
F 551@;%!1 G
G//@;.T.@%&;
F 551@!.0MG
G//@;.T.@/2O
F 551@3.-
!.P%Sdata G
G//@;.T.@/2O
F 551@3.-
!.P%Sdata G
G//@;.T.@/2O
F 551@3%-
!.P%Ssinallin G
55@3&%T;.T.@/2O
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@/2O
F P;3SModify
P;P 1onte't
/2O32!T G
55@3&%T;.T.@%&;
F P;3S
Modify P;P
1onte't .ccept G
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
F T55% G
55@/252.!2@ /2O
55@ /252.!2@1&7
F T55% G
F T55%- !&;1P@M%; re>uested G
55@2!T.05%!A@/2O
55@/252.!2@@%&;
F T55% G
55@3&%T;.T.@/2O
F P;3SModify
P;P 1onte't
.cceptG
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@/2O
55@3&%T;.T.@%&;
F P;3SModify
P;P 1onte't
/e>uestG
F !M@P;3- \.. G
GMM!M@3&%T
;.T.@%&;
!M/2G@P;P@ MO;%7L@1&7
F&!.P%G
!M/2G@P;P@ MO;%7L@/2O
F&!.P%G
&oteBThe release is only re>uested- if the lin" is not
used by any other P;P conte't usin ac"Ped mode
&OT2B The standalone P;P conte't modification procedure should use raceful disconnection of the 551 lin".
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3% "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.1) M- +ata an& M-/SMS transfer
55@;.T.@/2O
FT55%- &@P;3- local ref. G
55GMM@T/%GG2/@%&;
F T55%- 1% G
/2!T./T
/2.;L@timer
55@;.T.@%&;
F &@P;3- T55%-
local ref. G
55@;.T.@1&7
FT55%- local ref.G
55GMM@T/%GG2/
@%&;
F G
/2!T./T
/2.;L@timer
SMS SMS
55@ 3&%T;.T.@/2O
FT55%- !M!@1P@P;3 G
/2!T./T
/2.;L@timer
55@3&%T;.T.@%&;
F !M!@1P@P;3- T55% G
/2!T./T
/2.;L@timer
G//@;.T.@@/2O
F551@//-
prioritySdataG
G//@;.T.@%&;
F 551@%- T55%- 1% G
G//@;.T.@%&;
F 551@3%- T55%- 1% G
G//@;.T.@%&;
F 551@//G
G//@;.T.@/2O
F 551@3%-
!.P%S!M! G
G//@;.T.@/2O
F 551@%-
!.P%Sdata G
55GMM@T/%GG2/
@%&;
F G
55GMM@T/%GG2/@%&;
F T55%- 1% G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,33 "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.1* Paging an& MT +ata transfer
55GMM@T/%GG2/
@/2O
F G
G//@;.T.@%&;
F551 P;3- T55%-
1%G
GMM//@P.G2@/2O
GMM//@P.G2@%&;
55@;.T.@/2O
F &@P;3- T55%-
local ref. G
FT55%- %M!%- 1%
or 1%@list or /.%-
!.P%Ssinallin G
55GMM@P.G2@%&;
F T55% G
F G
/2!T./T
/2.;L@timer
/2.;L@timer
e'pires
55@;.T.@%&;
F T55%- &@P;3- local ref. G
/2!T./T
/2.;L@timer 55GMM@T/%GG2/@%&;
F T55%- 1%G
/2!T./T
/2.;L@timer
55@;.T.@1&7
F T55%- local ref. G
&ormal 551 traffic continues
!T./T P.G%&G
timer
!TOP P.G%&G
timer
55GMM@!3!P2&;@/2O
F T55%- cause G
. 551 frame is
sent- see ]1ell
updateP- 19?
/2!T./T
/2.;L@timer 55GMM@T/%GG2/@
/2!P@%&;
F T55%- 1% G
G//@;.T.@@/2O
F551@%-
!.P%SdataG
G//@;.T.@%&;
F 551@//- T55%- 1% G
551 is resumed-
MMin /2.;L
55GMM@/2!3M2@/2O
F T55% G G//@;.T.@%&;
F 551@%G
G//@;.T.@/2O
F 551@P;3-
!.P%Sdata G
G//@;.T.@/2O
F 551@//-
!.P%Sdata G
55GMM@T/%GG2/
@%&;
F G
551 is suspended-
MM in !T.&;0L-
cause indicates that pain is
re>uired if data has to be sent
55@;.T.!2&T
@%&;
F FT55%- local ref.-
C(!)G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3& "elease /
C.1, Paging for SMS an& SMS/MT transfer
MS !"T
GMM !M! 551 // !M !M! 551 // 0!!GP !M GMM
55@;.T.@/2O
F!M!@1P@P;3- T55% G
55GMM@P.G2@%&;
/2.;L@timer
e'pires
551 is suspended-
MMin !T.&;0L-
cause indicates that pain is
re>uired if data has to be sent
55GMM@!3!P2&;@/2O
F T55%- cause G
F T55% G
55GMM@T/%GG2/@/2O
F G
G//@;.T.@%&;
F551 P;3- T55%-
1%G
GMM//@P.G2@/2O
GMM//@P.G2@%&;
FT55%- %M!%- 1%
or 1%@list or /.%-
!.P%Ssinallin G
F G
/2!T./T
/2.;L@timer
55@;.T.@%&;
F T55%- !M!@1P@@P;3G
&ormal 551 traffic continues
!T./T P.G%&G
timer
!TOP P.G%&G
timer
.n 551 frame
is sent- see ]1ell
updatinP 19?
/2!T./T
/2.;L@timer
55GMM@T/%GG2/@%&;
F T55%- 1% G
G//@;.T.@@/2O
F551@3%-
!.P%S!M!G
551 is resumed-
MMin /2.;L
55GMM@/2!3M2@/2O
F T55% G G//@;.T.@%&;
F 551@3%G
G//@;.T.@/2O
F 551@P;3-
!.P%SdataJunitdata G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3- "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.11 Generi$ Routing Area ;p&ate, 5ntra SGS!
!T./T
Trams
55@3&%T;.T.
@%&;
FP;3S /. 3pdate /e> (
T55% plus /.%)-
oldT55%- 1% G
!ecurity function may be invo"ed
55@3&%T;.T.@
/2O
F P;3S
/. 3pdate /e> (
T55% plus old /.%)-
1ipherSoff G
!TOP
Trams
55@3&%T;.T.@/2O
FP;3S/. 3pdate@
.ccept (newT55%) G
55@3&%T;.T.@%&;
FP;3S/. 3pdate@
.ccept (newT55%) G
55GMM@.!!%G&@/2O
F newT55% G
FP;3@/. 3pdate 1ompl-
newT55%- 1% G
55Q3&%T;.T.Q%&;
!top Tran
55GMM@.!!%G&@/2O
F /'B newT55% or
oldT55%
T'B newT55% G
GMM//@.!!%G&@/2O
F new T55% G
!tart Tran
55GMM@.!!%G&
@/2O
F unassin oldT55% G
55GMM@!3!P2&;
@/2O
F G
!MM@/2!3M2@
/2O
F G
G//@;.T.@/2O
F 551@3%-
!.P%Ssinallin G
G//@;.T.@/2O
F 551@P;3-
!.P%Ssinallin G
G//@;.T.@%&;
F 551@3%G
G//@;.T.@%&;
F551 3%-
old T55%- 1%G
G//@;.T.@%&;
F551 P;3
new T55%- 1%G
55@3&%T;.T.@
/2O
F P;3S/. 3pdate@
1ompl-
1ipherSon G
G//@;.T.@@/2O
F551@3%-
!.P%Ssinallin G
The oldT55% may be a 5ocal
T55%- or a 7orein T55%- or a
/andom T55%
55GMM@.!!%G&@/2O
F unassin oldT55% G
GMM//@.!!%G&@/2O
F unassin oldT55% G
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3. "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
C.12 Routing Area ;p&ate, 5nter SGS!
G//@;.T.@%&;
F551@P;3-
oldT55%- 1%
55@3&%T;.T.@%&;
FP;3@/outin .rea
3pdate/e>uest-
oldT55%- 1% GG
!ecurity function may be invo"ed
F P;3S
$c- .lorith G
G//@;.T.@/2O
F 551@3%-
!.P%Ssinallin G
!T./T
Trams
55@3&%T;.T.@
/2O
F P;3@/outin
.rea 3pdate /e>uest-
1ipherSoff G
55GMM@!3!P2&;
@/2O
F T55%G
!ee ]/outin area update- inter !G!&- old
!G!&P in the GTP protocol. The new !G!&
receivesB
/eceive &@P;3number if ac"Ped mode
is used
@ MMand P;P conte'ts- with !end and
F$c- .lorithmG
55GMM@.!!%G&@/2O
/2!2T and %OC@3% sent- possibly toether
with !&;1PJ551 M%; e'chane
//@3&%T;.T.@/2O
//@3&%T;.T.@%&;
F 551@!.0M- !.P%SdataG
F 551@3.- T55%- 1% G
55@2!T.05%!A@%&;
55@2!T.05%!A@/!P
F!&;1P M%; re>uestedG
F!&;1P M%; neotiatedG
G//@3&%T;.T.@%&;
G//@3&%T;.T.@/2O
F 551@!.0MG
F 551@3.- !.P%Sdata G
55@2!T.05%!A@/2O
55@2!T.05%!A@1&7
!&!M@MO;%7L@/!P
F!&;1P M%; re>uesetedG
F!&;1P M%; neotiatedG
!&!M@MO;%7L@%&;
FT55%- &!.P%- Oo!G
FT55%G
2stablishment andJor M%;
&eotiation- as re>uired
/eceive &@P;3s tunnelled from the old
!G!&. 7or ac"Ped mode &@P;3s- &@P;3
number is also received if assined.
G//@3&%T;.T.@/2O
F/eset- %OC@3%- 551@M%;G
G//@3&%T;.T.@%&;
F 551@M%;- T55%- 1% G
55GMM@/2!2T@/2O
F T55%G
F T55%G
55@/2!2T@%&;
F T55%G
55GMM@/2!2T@1&7
F T55% G
G//@3&%T;.T.@%&;
F /eset- %OC@3%- 551@M%; G
G//@3&%T;.T.@/2O
F 551@M%; G
55@/2!2T@%&;
!&;1P suspends transmission
for &!.P%s usin ac" mode
!&;1P suspends transmission
for &!.P%s usin ac" mode
!ent for every P;P conte't to be
created in the new !G!&
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3) "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
P;P 1O&T2MT Modification may be re>uested (optional) N see fiure 1.99
F oldT55% G
F
55GMM@.!!%G&@/2O
unassin
GMM//@.!!%G&@/2O
unassin oldT55% G
3nassinment of old T55% may be
delayed so that !.0MJM%; sent on
the old T55% may be received
C.12#$ont%&' Routing Area ;p&ate, 5nter SGS!
//@;.T.@%&;
F551@P;3-
newT55%- 1% G
F
55GMM@.!!%G&@/2O
unassin oldT55%-G
G//@;.T.@/2O
F 551@3%-
!.P%Ssinallin G
F
F P;3S
/.3pdate 1ompl
/' &@P;3number- 1ipherG
55@3&%T;.T.
@/2O
F T55% G
55GMM@/2!3M2@
@/2O
FP;3S/. 3pdate1ompl F
/' &@P;3number- newT55%- 1% G
55@3&%T;.T.
@%&;
!top Tran
!&!M@!2O32&12@%&;
FT55%- &!.P%-
F /' &@P;3numberG
!ent for each &!.P% usin ac" mode.
!&;1P deletes buffered &@P;3s
received by M!- and bein re@
transmittin all buffered &@P;3s.
G//@;.T.@/2O
F 551@P;3-
!.P%Ssinallin G
55GMM@.!!%G&@/2O
F /'B newT55% or
oldT55%
T'B newT55% G
GMM//@.!!%G&@/2O
F new T55% G
55GMM@.!!%G&@/2O
F new T55%- $c- .lorithm
G//@;.T.@%&;
F 551@P;3G
55@3&%T;.T.@/2O
P;3S /. 3pdate @.ccept F
/' &@P;3 numbers- 1ipherSon G
!T./T
Tran
2stablishment andJor M%;
neotiation on non@sinallin !.P%s
may still be outstandin when /.
update accept is sent
!TOP
Trams
!&!M@!2O32&12@%&;
FT55%- &!.P%-
/' &@P;3 numberG
!ent for each &!.P% usin ac" mode.
!&;1P deletes buffered &@P;3s
received by !G!&- and bein re@
transmittin all buffered &@P;3s.
55@3&%T;.T.@%&;
P;3S /. 3pdate .ccept F
/' &@P;3 numbers- 1ipherG
!&!M@!2O32&12@/2!
FT55%- &!.P%-
/' &@P;3 numberG
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3/ "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
55GMM@T/%GG2/
@/2O
F G
G//Q;.T.Q/2O
F 551@//-
!.P%Sdata G
G//Q;.T.Q%&;
F 551@!.1$-
T55%- 1% G
55GMM@T/%GG2/
@%&;
F T55%- 1% G
C.16 C"<< ;P+AT"
G//Q;.T.Q/2O
F 551@%-
prioritySunitdata G
G//Q;.T.Q%&;
F 551@%- T55%-
1% G
F &@P;3- T55%-
local ref.G
55Q;.T.Q%&;
%f no 551 frames
pendin and 551 in
.0M- send a
supervisory frame-
e.. //
%f 551 frames
pendin and 551
in .0M send e.. an
% P;3
/2!T./T
/2.;L
@timer
/2!T./T
/2.;L
@timer
or
55GMM@T/%GG2/
@%&;
F T55%- 1% G
/2!T./T
/2.;L
@timer
G//Q;.T.Q/2O
F 551@3%-
prioritySunitdata G
G//Q;.T.Q%&;
F 551@;M- T55%-
1% G
%f 551 in .;M-
then a 3% is sent.
or
55GMM@T/%GG2/
@%&;
F T55%- 1% G
/2!T./T
/2.;L
@timer
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,3# "elease /
MS !"T
GMM !&;1P 551 // !M !&;1P 551 // 0!!GP !M GMM
55GMM@T/%GG2/
@/2O
G//Q;.T.Q/2O
F 551@//-
!.P%Sdata G
G//Q;.T.Q%&;
F 551@!.1$-
T55%- 1% G
55GMM@T/%GG2/
@%&;
F T55%- 1% -&355G
C.17 C"<< !otifi$ation
G//Q;.T.Q/2O
F 551@%-
prioritySunitdata G
G//Q;.T.Q%&;
F 551@%- T55%-
1% G
F &@P;3- T55%-
local ref.G
55Q;.T.Q%&;
%f no 551 frames
pendin and 551 in
.0M- send a
!;<< frame
%f 551 frames
pendin and 551
in .0M send e.. an
% P;3
or
55GMM@T/%GG2/
@%&;
F T55%- 1% G
/2!T./T
/2.;L
@timer
G//Q;.T.Q/2O
F 551@3%-
prioritySunitdata G
G//Q;.T.Q%&;
F 551@;M- T55%-
1% G
%f 551 in .;M-
then a 3% is sent.
or
55GMM@T/%GG2/
@%&;
F T55%- 1% G
/2!T./T
/2.;L
@timer
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,&( "elease /
+nne2 6 ((n5or:at(7e)0
/*an4e *(&tory
TSG S2D Spec *ersi
on
C" "e3 "el New
*ersi
on
Subject Comment
D$n 1999 GSM 04.07 7.1.0 Tran&5erre% to 3GPP
/.
/.R04 24.007 3.0.0
/.R" 24.007 3.0.0 002 1 #99 3.1.0 +%%(t(on o5 LL-ST+TUSC8.6
/.R! 24.007 3.0.1 004 1 #99 3.2.0 U)l(nk L3 Me&&a4e Se9$en'(n4
/.R! 24.007 3.0.1 00" #99 3.2.0 M(rror #99 L/S /# to 04.07
/.R! 24.007 3.0.1 003 " #99 3.2.0 U&(n4 MM &$,layer 5or PS-SMS
:e&&a4e tran&5er
/.R! 24.007 3.0.1 001 " #99 3.2.0 Tran&a't(on 8%ent(5(er 2ten&(on
/.R7 24.007 3.2.0 00! 1 #99 3.3.0 U)%at(n4 Se&&(on Mana4e:ent
(SM) 5or #99
/.R7 24.007 3.2.0 007 #99 3.3.0 #e:o7al o5 +nony:o$& +''e&&
/.R7 24.007 3.2.0 00E #99 3.3.0 PMMSMS-#L-#e9 %elet(on (n MS
&(%e
/.R7 24.007 3.2.0 010 1 #99 3.3.0 8nte4r(ty '*e'k(n4 o5 &(4nall(n4
:e&&a4e& 5or UMTS
- 24.007 3.3.0 - - #99 3.3.1 %(tor(al '*an4e&
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,&, "elease /
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,&% "elease /
TSGN TSGN-
number
WG
Number
Spec CR Rev Rel C
at
Old
vers
New
ver
Title WI Notes/Date
CN#8 NP-000270 N1-000620 24.007 006 2 R99 F 3.3.1 3.4.0 Updating SM for R99 SM!UM"S
#nt$r%or&ing
CN#8 NP-000270 N1-000619 24.007 012 R99 F 3.3.1 3.4.0 R$'o($ RR pri'iti($ d$)*ription) and
'a&$ r$f$r$n*$ to ot+$r do*,'$nt
SM!UM"S
#nt$r%or&ing
CN#8 NP-000269 N1-000763 24.007 014 2 R99 F 3.3.1 3.4.0 C+ang$ of t+$ MM R$ad- "i'$r
.$+a(io,r
PRS
CN#08 NP-000269 N1-000668 24.007 01/ R99 C 3.3.1 3.4.0 N$% P0 for 11C for ,)$ .- 0"M 20,a3
"ran)f$r Mod$4 'o.i3$)
PRS
CN#8 NP-000270 N1-000669 24.007 016 R99 C 3.3.1 3.4.0 S$r(i*$) pro(id$d .- t+$ Radio R$)o,r*$
Manag$'$nt $ntit-
SM!UM"S
#nt$r%or&ing
CN#9 NP-000443 N1-001032 24.007 013 3 R99 F 3.4.0 3./.0 S5P) and S$r(i*$ pri'iti($) for UM"S6 PS
'od$.
SM!UM"S
#nt$r%or&ing
adapt$d to
ad7,)t t+$
o3d$r ,)$d
r$3$a)$ of t+$
)p$*
CN#9 NP-000443 N1-000880 24.007 018 R99 F 3.4.0 3./.0 Proto*o3 di)*ri'inator (a3,$ for U8 )p$*ia3
*onfor'an*$ t$)ting f,n*tion)
SM!UM"S
#nt$r%or&ing
CN#9 NP-000443 N1-00101/ 24.007 019 1 R99 F 3.4.0 3./.0 Corr$*tion of )$nd )$9,$n*$ n,'.$r
'$t+od app3i$d proto*o3)
SM!UM"S
#nt$r%or&ing
CN#9 NP-000443 N1-000930 24.007 020 R99 F 3.4.0 3./.0 8ditoria3 *orr$*tion):: SM!UM"S
#nt$r%or&ing
CN#9 NP-000441 N1-000969 24.007 021 R99 F 3.4.0 3./.0 Proto*o3 0i)*ri'inator for 0"M 2)i'p3$
*3a)) 54
PRS
NP-10 NP-000673 N1-001188 24.007 024 R99 F 3./.0 3.6.0 R$'o(a3 of F3o% #d fro' RR-S5P "8#
NP-10 NP-000670 N1-001367 24.007 02/ 1 R99 F 3./.0 3.6.0 R5;M5S-S5P and R5;MSM-S5P
adaptation for <and3ing of ,n)-n*+roni=$d
P0P *ont$>t)
PRS
NP-10 NP-000671 N1-001246 24.007 027 R99 F 3./.0 3.6.0 Updating CS!PS proto*o3 ar*+it$*t,r$
fig,r$ %it+ R5;M
SM!UM"S
#nt$r%or&ing
NP-10 NP-000671 N1-0012/6 24.007 028 R99 F 3./.0 3.6.0 53ign'$nt of 24.007 to ot+$r )p$*) SM!UM"S
#nt$r%or&ing
NP-11 NP-010123 N1-010101 24.007 02/ 2 R99 F 3.6.0 3.7.0 5ddition of Str$a' #d$ntifi$r and N5S
S-n*+roni=ation #ndi*ator to t+$ pri'iti($)
SM!UM"S
int$r%or&ing
03-2001
NP-11 NP-010123 N1-010083 24.007 032 R99 F 3.6.0 3.7.0 C+ang$ MM5S-S5P to RR-S5P in fig. /.6 SM!UM"S
int$r%or&ing
03-2001
NP-11 NP-010207 N1-010486 24.007 034 R99 F 3.6.0 3.7.0 "ran)f$r of t+$ N2S04 d,p3i*ation
a(oidan*$ proto*o3 fro' SM 04.18
SM!UM"S
int$r%or&ing
03-2001
NP-11 NP-01020/ N1-010447 24.007 03/ R99 F 3.6.0 3.7.0 0$3$tion of *a,)$ ?,n)-n*+rono,)P0P? in
R5;M5S-S5P
"8# 03-2001
NP-11 NP-010206 N1-010444 24.007 031 3 R$3-4 ; 3.7.0 4.0.0 5daptation of SS proto*o3 to PS do'ain "8# 03-2001
NP-14 NP-010682 N1-011811 24.007 043 1 R$3-4 5 4.0.0 4.1.0 C3arifi*ation of t+$ )$nd )$9,$n*$ n,'.$r
'$*+ani)'
SM!UM"S
int$r%or&ing
12-2001
NP-16 NP-020218 N1-021341 24.007 047 2 R$3-4 5 4.1.0 4.2.0 RR proto*o3 '$))ag$ t-p$ o*t$t SM!UM"S
int$r%or&ing
06-2002
NP-16 NP-020222 N1-020893 24.007 049 1 R$3-4 5 4.1.0 4.2.0 C3arifi*ation of t+$ $>t$n)ion '$*+ani)'
for t-p$ 4 #8)
"8# 06-2002
NP-16 NP-020224 N1-021367 24.007 0/3 1 R$3-4 F 4.1.0 4.2.0 @ario,) *3$an-,p of %rong r$f$r$n*$)6 $g
to%ard) 44.018 and 23.271
"8#4 06-2002
NP-16 24.007 R$3-/ 4.2.0 /.0.0 P3$nar- d$*i)ion to 'a&$ t+i) "S a3)o for
R$3-/.
06-2002
NP-17 NP-020383 N1-021836 24.007 0/7 1 R$3-/ F /.0.0 /.1.0 C3arifi*ation of t+$ CN r$3$a)$ indi*ator) "8#/ 09-2002
NP-22 NP-03048/ N1-0316/3 24.007 0/9 1 R$3-6 F /.1.0 6.0.0 0on?t ,)$ S5P# to diff$r$ntiat$ .$t%$$n
'$))ag$) of t+$ )a'$ '$))ag$ t-p$.
"8#6 12-2003
NP-24 NP-04018/ N1-040967 24.007 063 1 R$3-6 5 6.0.0 6.1.0 Corr$*tion) *on*$rning t+$ ,)$ of t+$ 1CS
proto*o3
1CS 06-2004
NP-2/ NP-040377 N1-04162/ 24.007 064 1 R$3-6 ; 6.1.0 6.2.0 Updat$ of t+$ S$))ion Manag$'$nt
)$r(i*$) - M;MS
M;MS 09-2004
NP-2/ NP-04037/ N1-04164/ 24.007 067 4 R$3-6 ; 6.1.0 6.2.0 S$9,$n*$ n,'.$r +and3ing d,ring
r$dir$*tion in MACN )+aring )*$nario
N"S+ar 09-2004
NP-26 NP-040/01 N1-04844 24.007 070 5 6.2.0 6.3.0 S$9,$n*$ n,'.$ring for SS (ia PS "8#4 12-2004
NP-27 NP-0/0068 N1-0/004/ 24.007 072 R$3-6 5 6.3.0 6.4.0 5ddition of 'a>i',' data rat$ to
RRBSCNCB#N0 and MMCCBSCNCB#N0
SCU0#F 03-200/
CP-29 CP-0/0361 C1-0/0966 24.007 074 R$3-6 F 6.4.0 6./.0 U)$ of )+ort +$ad$r for'at on S0CC< !
F5CC<
"8#6 09-200/
CP-29 CP-0/0366 C1-0/1030 24.007 07/ 1 R$3-7 F 6./.0 7.0.0 <and3ing of t+$ 12 P)$,do 1$ngt+ "8#7 09-200/
CP-42 CP-080866 C1-08/163 24.007 0078 2 R$3-8 ; 7.0.0 8.0.0 S,pport of 8PS N5S proto*o3) S58S 12-2008
CP-43 CP-09012/ C1-091296 24.007 0082 2 R$3-8 F 8.0.0 8.1.0 U8 )id$ ar*+it$*t,r$ fig,r$ %it+o,t CSF; S58S 03-2009
CP-43 CP-0901/3 C1-091320 24.007 0083 2 R$3-8 F 8.0.0 8.1.0 5r*+it$*t,r$ fig,r$ for 8PS U8 D CSF; S58S-CSF; 03-2009
CP-43 CP-090130 C1-091182 24.007 008/ 1 R$3-8 F 8.0.0 8.1.0 M$))ag$ d,p3i*ation in S1 'od$ S58S 03-2009
CP-43 CP-09012/ C1-091106 24.007 0086 1 R$3-8 F 8.0.0 8.1.0 5dd r$f$r$n*$ of 1"8 t$)t *ontro3
)p$*ifi*ation
S58S 03-2009
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,&3 "elease /
TSGN TSGN-
number
WG
Number
Spec CR Rev Rel C
at
Old
vers
New
ver
Title WI Notes/Date
CP-43 CP-090126 C1-0913/0 24.007 0087 2 R$3-8 F 8.0.0 8.1.0 C3arifi*ation of for'at of 1@-8!"1@-8
1$ngt+ #ndi*ator for'at
S58S 03-2009
CP-43 24.007 R$3-8 8.0.0 8.1.0 8ditoria3 *3$an,p .- MCC 03-2009
CP-44 CP-090422 C1-092120 24.007 0090 1 R$3-8 F 8.1.0 8.2.0 <and3ing of )$9,$n*$ n,'.$r) S58S-SR@CC 06-2009
CP-46 R$3-9 8.2.0 9.0.0 Upgrad$ to R$3-9 .- MCC 12-2009
3GPP
3GPP TS %&'(() */'%'( !%((#+(.$ ,&& "elease /