3GPP TS 22.101 V12.4.

0 (2013-03)
Technical Specification
3
rd
Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Service aspects;
Service principles
(Release 12
The present document has been developed within the 3
rd
Generation Partnership Project (3GPP
TM
) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP

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

only. The Oranisational Partners accept no liability for any use of this
!pecification.
!pecifications and reports for implementation of the 3GPP
TM
system should be obtained via the 3GPP Oranisational Partners# Publications Offices.
3GPP
$eywords
UMTS, LTE, service
3GPP
Postal address
3GPP support office address
650 Roue !es Lucio"es - So#$i% &'i#o"is
V%"(o''e - )R&*+E
Te"., -33 4 .2 .4 42 00 )%/, -33 4 .3 65 40 16
%nternet
$#,11222.33##.or3
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.
) *+,3- 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!% 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 22!1"1 #12!$!" (2"13%"3 2 Release 12
+o'e's
1ontents.................................................................................................................................................... 3
7oreword................................................................................................................................................... 8
, !cope...................................................................................................................................................... 9
* /eferences.............................................................................................................................................. 9
*., &ormative references.............................................................................................................................................:
*.* %nformative references.........................................................................................................................................,+
3 ;efinitions- symbols and abbreviations.................................................................................................,+
3., ;efinitions...........................................................................................................................................................,+
3.* .bbreviations.......................................................................................................................................................,,
< General................................................................................................................................................. ,,
<., .ims of 3GPP specifications...............................................................................................................................,,
<.* !tandardisation of !ervice 1apabilities...............................................................................................................,*
<.*., Provision of service capabilities in shared networ"s.......................................................................................,*
<.3 2fficient 3se of &etwor" /esources....................................................................................................................,*
<.3., &etwor" Traffic Patterns..................................................................................................................................,*
<.3.* Mass !imultaneous /eistration......................................................................................................................,*
<.3.3 /adio %nterface..................................................................................................................................................,*
<.3.< /eal=time /esource 3sae................................................................................................................................,3
<.3.> !elected %P Traffic Offload (!%PTO) for P! ;omain only...............................................................................,3
<.3.>., 1ommon /e?uirements for !%PTO in the Mobile Operator &etwor" and !%PTO at the 5ocal &etwor"....,3
<.3.>.* /e?uirements for !%PTO in the Mobile Operator &etwor"..........................................................................,<
<.< 1ompatibility with Global !tandards..................................................................................................................,<
<.> @oid ,<
<.A 7unctionality of !ervin &etwor" and Bome 2nvironment...............................................................................,<
<.8 P5M& .rchitecture.............................................................................................................................................,>
<.9 %nterwor"in 0etween P5M& and Cireless 5.&s.............................................................................................,>
<.: &etwor" !harin..................................................................................................................................................,>
<.,+ The 2volved Pac"et !ystem...............................................................................................................................,>
<.,, 3ser ;ata 1onverence.....................................................................................................................................,>
<.,,., %ntroduction....................................................................................................................................................,>
<.,,.* Manaement of user data...............................................................................................................................,A
<.,,.3 3ser ;ata Modellin......................................................................................................................................,A
> 2volution.............................................................................................................................................. ,8
>., !upport of *G services.........................................................................................................................................,8
>.* Provision and evolution of services.....................................................................................................................,8
A 1lassification of services......................................................................................................................,8
8 Principles for new service capabilities..................................................................................................,9
8., General.................................................................................................................................................................,9
8.* Multimedia...........................................................................................................................................................,9
8.*., 1ircuit !witched (1!) multimedia calls...........................................................................................................,:
8.*.* %P multimedia (%M) sessions.............................................................................................................................,:
8.*.3 Multimedia Messain !ervice (MM!)..........................................................................................................*+
8.*.< Te't 1onversation.............................................................................................................................................*+
8.*.> Pac"et !witched !treamin !ervice.................................................................................................................*+
8.3 !ervice Manaement /e?uirements....................................................................................................................*+
8.< .utomatic ;evice ;etection................................................................................................................................*,
9 !ervice architecture.............................................................................................................................. *,
: Duality of !ervice (Do!)......................................................................................................................**
,+ 2merency 1alls.................................................................................................................................**
,+., General re?uirements.......................................................................................................................................**
,+.,., %dentification of emerency numbers............................................................................................................*3
,+.,.* ;omains priority and selection for 32 attempts to emerency call..............................................................*<
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3 Release 12
,+.,.*., @oice and GTT only....................................................................................................................................*<
,+.,.*.* Other media.................................................................................................................................................*<
,+.,.3 1all=0ac" /e?uirements.................................................................................................................................*<
,+.* 2merency calls in the 1! 1& ;omain............................................................................................................*<
,+.3 2merency 1alls in the P! 1& ;omain...........................................................................................................*<
,+.< 2merency calls in the %M 1& subsystem........................................................................................................*>
,+.<., General............................................................................................................................................................*>
,+.<.* %M! Multimedia 2merency !essions...........................................................................................................*>
,+.<.*., General *>
,+.<.*.* 32 /e?uirements.........................................................................................................................................*A
,+.<.*.3 Oriinatin &etwor" /e?uirements............................................................................................................*8
,+.> @oid *9
,+.A 5ocation .vailability for 2merency 1alls.......................................................................................................*9
,+.8 Transfer of data durin emerency calls...........................................................................................................*9
,+.9 !upplementary service interaction durin emerency calls..............................................................................*:
,, &umberin principles.........................................................................................................................*:
,,., &umber portability.............................................................................................................................................*:
,,.,., /e?uirements for 1! 1& domain...................................................................................................................*:
,,.,.* /e?uirements for P! 1& domain...................................................................................................................*:
,,.,.3 /e?uirements for %M 1& subsystem..............................................................................................................*:
,,.* 2volution path....................................................................................................................................................*:
,,.3 @oid 3+
,,.< @oid 3+
,,.> @oid 3+
,,.A Private numberin.............................................................................................................................................3+
,,.8 &umberin schemes...........................................................................................................................................3+
,,.8., Multiple numberin scheme...........................................................................................................................3+
,,.8.* !inle numberin scheme..............................................................................................................................3+
,,.8.3 .dditional numbers........................................................................................................................................3+
,,.9 Optimal routin.................................................................................................................................................3+
,,a %dentification /e?uirements..............................................................................................................3+
,,a., !ubscriber %dentification..................................................................................................................................3+
,,a.* Terminal %dentification....................................................................................................................................3,
,,a.3 Bome 2nvironment E !ervin &etwor" %dentification....................................................................................3,
,,a.< !ervin 2nvironment E Mobile @irtual &etwor" %dentification......................................................................3,
,* Buman 7actors and user procedures...................................................................................................3,
,3 3%11- 3!%M and Terminal................................................................................................................3*
,3., The 3!%ME%!%M and 3ser Profiles....................................................................................................................3*
,3.,., The 3!%M.......................................................................................................................................................3*
,3.,.* 3ser Profiles....................................................................................................................................................3*
,3.,.3 3%11 usae in G2/.& only Terminals........................................................................................................33
,3.,.< Multiple 3!%Ms per 3%11.............................................................................................................................33
,3.,.> The %!%M........................................................................................................................................................33
,3.* The 3%11...........................................................................................................................................................33
,3.*., The 3%11 and .pplications other than the 3!%M or %!%M..........................................................................33
,3.*.,a 3%11 applications and %M!.......................................................................................................................3<
,3.*.* 7ast .ccess and /etrieval of ;ata from 3%11..............................................................................................3<
,3.3 Terminals and Multiple 3%11s.........................................................................................................................3<
,< Types of features of 32s.................................................................................................................... 3<
,> /elationship between subscription and service delivery......................................................................3A
,>., !ubscription.......................................................................................................................................................3A
,>.* Other concepts associated with services............................................................................................................38
,>.3 /e?uirements concernin service delivery........................................................................................................38
,>.3., Mobile Oriinated @oice calls........................................................................................................................39
,>.3.* Mobile Terminated @oice calls......................................................................................................................39
,A 1harin principles............................................................................................................................. 39
,8 /oamin............................................................................................................................................. 39
,8., .ssumptions.......................................................................................................................................................39
,8.* Principle............................................................................................................................................................3:
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $ Release 12
,8.3 /e?uirements.....................................................................................................................................................3:
,9 Bandover /e?uirements...................................................................................................................... <+
,: &etwor" !election.............................................................................................................................. <+
*+ !ecurity.............................................................................................................................................. <+
*, @oice 1all 1ontinuity......................................................................................................................... <+
*,., General...............................................................................................................................................................<+
*,.* !upport of !upplementary !ervices...................................................................................................................<+
*,.*., 5ine %dentification !ervices............................................................................................................................<,
*,.*.* .ll 1all 7orwardins......................................................................................................................................<,
*,.*.3 1all Caitin...................................................................................................................................................<,
*,.*.< 1all Bold.........................................................................................................................................................<,
*,.*.> Multiparty.......................................................................................................................................................<,
*,.*.A .ll 1all 0arrins............................................................................................................................................<,
*,.*.8 @oid <,
*,.*.9 @oid <,
*,.*.: .ll other !upplementary !ervices..................................................................................................................<,
*,.3 Duality of !ervice..............................................................................................................................................<*
*,.< !ecurity..............................................................................................................................................................<*
*,.> 2merency calls.................................................................................................................................................<*
*,.A 1harin............................................................................................................................................................<*
*,.8 @11 .ctivation.................................................................................................................................................<*
** %M! 1entrali(ed !ervices................................................................................................................... <*
**., General...............................................................................................................................................................<*
**.* !ervice 1onsistency...........................................................................................................................................<*
**.3 !ervice 1ontinuity.............................................................................................................................................<3
**.< %M! !ervices......................................................................................................................................................<3
**.> /oamin !upport...............................................................................................................................................<3
*3 1! %P interconnection re?uirements....................................................................................................<3
*3., %ntroduction........................................................................................................................................................<3
*3.* %P interconnect...................................................................................................................................................<3
*3.3 M!1 server interconnect...................................................................................................................................<<
*< !ervice .linment F Miration..........................................................................................................<<
*<., %ntroduction........................................................................................................................................................<<
*<.* .linment of supplementary services settins..................................................................................................<<
*> !ystem optimisation for communication with specific characteristics.................................................<A
*>., @oid <A
*>.* &umberin /esource 2fficiency........................................................................................................................<A
*>.3 &etwor" provided destination for uplin" data..................................................................................................<A
*>.< P! only subscriptions.........................................................................................................................................<A
*A !inle !in=On (!!O) !ervice............................................................................................................<A
*A., /e?uirements.....................................................................................................................................................<A
*A.,., /e?uirements for the 32................................................................................................................................<A
*A.,.* /e?uirements for a 3GPP !!O !ervice..........................................................................................................<8
*8 3ser plane conestion manaement.....................................................................................................<8
*8., %ntroduction........................................................................................................................................................<8
*8.* General...............................................................................................................................................................<8
*8.3 Prioriti(in traffic..............................................................................................................................................<8
*8.< /educin traffic.................................................................................................................................................<9
*8.> 5imitin traffic..................................................................................................................................................<9
Annex A (normative):
Description of optional user equipment features..................................49
.., ;isplay of called number....................................................................................................................................<:
..* %ndication of call proress sinals......................................................................................................................<:
..3 1ountryEP5M& indication..................................................................................................................................<:
..< !ervice Provider &ame indication......................................................................................................................<:
..<a 1ore &etwor" Operator &ame indication.........................................................................................................>+
..> $eypad................................................................................................................................................................>+
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 & Release 12
..A !hort messae indication and ac"nowledement...............................................................................................>+
..8 !hort messae overflow indication.....................................................................................................................>+
..9 %nternational access function..............................................................................................................................>+
..: !ervice %ndicator (!%)..........................................................................................................................................>,
..,+ ;ual Tone Multi 7re?uency (;TM7)...............................................................................................................>,
..,, OnEOff switch....................................................................................................................................................>,
..,* !ub=.ddress......................................................................................................................................................>,
..,3 !hort Messae !ervice 1ell 0roadcast.............................................................................................................>,
..,< !hort Messae !ervice 1ell 0roadcast ;/G....................................................................................................>,
..,> !upport of the e'tended !hort messae cell broadcast channel.......................................................................>,
..,A &etwor" %dentity and Time(one.......................................................................................................................>,
..,8 &etwor"#s indication of alertin in the 32.......................................................................................................>*
..,9 &etwor" initiated Mobile Oriinated (MO) connection..................................................................................>3
..,: .bbreviated diallin.........................................................................................................................................>3
..*+ 0arrin of ;ialled &umbers.............................................................................................................................>3
..*, ;TM7 control diits separator.........................................................................................................................><
..** !election of directory number in messaes......................................................................................................><
..*3 5ast &umbers ;ialled (5&;)...........................................................................................................................>>
..*< !ervice ;iallin &umbers.................................................................................................................................>>
..*> 7i'ed number diallin.......................................................................................................................................>>
..*A Messae Caitin %ndication.............................................................................................................................>A
..*8 /e?uirements for the transfer of e1all Minimum !et of ;ata (M!;)...........................................................>A
..*9 /e?uirements for H%n 1ase of 2merencyH (%12) information.......................................................................>8
Annex B (informative):
Additional number use case...................................................................58
Annex (informative):
!an"e !istor#.......................................................................................$%
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 ' Release 12
)ore2or!
This Technical !pecification has been produced by the 3GPP.
The contents of the present document are subject to continuin wor" within the T!G and may chane followin
formal T!G approval. !hould the T!G modify the contents of the present document- it will be re=released by the T!G
with an identifyin chane of release date and an increase in version number as followsI
@ersion '.y.(
whereI
' the first diitI
, presented to T!G for informationJ
* presented to T!G for approvalJ
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 22!1"1 #12!$!" (2"13%"3 ( Release 12
1 Sco#e
This Technical !pecification (T!) describes the !ervice Principles for P5M&s specified by 3GPP. Principles and
re?uirements for interwor"in with C5.& are covered in T!**.*3< K3>L.
3GPP specifications provide interated personal communications services. The system will support different
applications ranin from narrow=band to wide=band communications capability with interated personal and
terminal mobility to meet the user and service re?uirements of the *,
st
century.
3GPP specifications allow the realisation of a new eneration of mobile communications technoloy for a world in
which personal communications services should allow person=to=person callin- independent of location- the terminal
used- the means of transmission (wired or wireless) and the choice of technoloy. Personal communication services
should be based on a combination of fi'ed and wirelessEmobile services to form a seamless end=to=end service for the
user.
3GPP specifications should be in compliance with the followin objectivesI
a) to provide a sinle interated system in which the user can access services in an easy to use and uniform way in
all environmentsJ
b) to allow differentiation between service offerins of various servin networ"s and home environmentsJ
c) to provide a wide rane of telecommunications services includin those provided by fi'ed networ"s and
re?uirin user bit rates of up to ,++ MbitsEs as well as services special to mobile communications. These
services should be supported in residential- public and office environments and in areas of diverse population
densities. These services are provided with a ?uality comparable with that provided by fi'ed networ"s such as
%!;& and fi'ed broadband %nternet accessJ
d) to provide services via hand held- portable- vehicular mounted- movable and fi'ed terminals (includin those
which normally operate connected to fi'ed networ"s)- in all environments (in different service environments =
residential- private domestic and different radio environments) provided that the terminal has the necessary
capabilitiesJ
e) to provide support of roamin users by enablin users to access services provided by their home environment in
the same way even when roamin.
f) to provide audio- data- video and particularly multimedia servicesJ
) to provide for the fle'ible introduction of telecommunication servicesJ
h) to provide within the residential environment the capability to enable a pedestrian user to access all services
normally provided by fi'ed networ"sJ
i) to provide within the office environment the capability to enable a pedestrian user to access all services
normally provided by P0Gs and 5.&sJ
j) to provide a substitute for fi'ed networ"s in areas of diverse population densities- under conditions approved by
the appropriate national or reional reulatory authority.
") to provide support for interfaces which allow the use of terminals normally connected to fi'ed networ"s.
2 Re4ere'ces
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
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 ) Release 12
the same Release as the present document.
2.1 *or5%ive re4ere'ces
K,L 3GPP T! **.,+> H!ervices and !ervice 1apabilitiesH
K*L @oid
K3L 3GPP T! **.+39I H!%M application tool"it- stae ,H
K<L 3GPP T! **.++,I H Principles of 1ircuit telecommunication services supported by a Public 5and
Mobile &etwor" (P5M&)H.
K>L 3GPP T! **.++<I General on supplementary servicesH
KAL 3GPP T! **.+3+I HMan=Machine %nterface (MM%) of the 3ser 2?uipment (32)H
K8L 3GPP T! **.+AAI H!upport of Mobile &umber Portability (M&P)J !ervice descriptionJ !tae ,H
K9L 3GPP T! **.+8:I H !upport of Optimal /outinJ !tae ,H
K:L 3GPP T! **.,*:I HBandover /e?uirements between 3T/.& and G2/.& or other /adio
!ystemsH
K,+L 3GPP T! 33.,+*I H!ecurity .rchitectureH
K,,L 3GPP T! **.+,,I H!ervice .ccessibilityH
K,*L 3GPP T! **.+,AI H%nternational mobile !tation 2?uipment %dentities (%M2%)H
K,3L 3GPP T! *<.++9I H Mobile /adio %nterface 5ayer 3 !pecificationH
K,<L 3GPP T! **.++3I H1ircuit Teleservices supported by a Public 5and Mobile &etwor" (P5M&)H
K,>L 3GPP T! *,.,33I H!ecurity Threats and /e?uirementsH
K,AL 3GPP T! 33.,*+I H!ecurity PrinciplesH
K,8L 3GPP T! **.+<*I H&etwor" %dentity and Time Mone- !ervice ;escription- !tae ,H
K,9L 3GPP T! <*.++:I H!ecurity .spectsH
K,:L 3GPP T! 3,.,+*I H3!%M .pplication 1haracteristicsH
K*+L 3GPP T! *3.**, H.rchitectural /e?uirementsH
K*,L 3GPP T! **.++*I H1ircuit 0earer !ervices (0!) supported by a Public 5and Mobile &etwor"
(P5M&)H
K**L 3GPP T! **.+A+I HGeneral Pac"et /adio !ervice (GP/!)H
K*3L 3GPP T! *:.++*I HMobile .pplication Part (M.P) specification H
K*<L 3GPP T/ *3.:8*I H1ircuit !witched Multimedia TelephonyH.
K*>L 3GPP T! **.,<+I HMultimedia messain serviceJ !tae ,H.
K*AL 3GPP T! **.**AI HGlobal Te't Telephony- !tae ,.H
K*8L 3GPP T! **.**9I H%P multimedia (%M) 1& subsystem- stae ,H
K*9L /71 3*A,I H!%PI !ession %nitiation ProtocolH
K*:L 3GPP T/ *,.:+>I H @ocabulary for 3GPP !pecificationsH
K3+L 3GPP T! *A.*33I HPac"et !witched !treamin !ervice (P!!) J General ;escriptionH
K3,L 3GPP T! *A.*3<I HPac"et !witched !treamin !ervice (P!!) J Protocols and 1odecsH
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 * Release 12
K3*L 3GPP T/ **.:3<I H7easibility study on 3GPP system to Cireless 5.& interwor"inH
K33L /71 *<9AI HThe &etwor" .ccess %dentifierH
K3<L T! >,.+,,I H!pecification of the !ubscriber %dentity Module = Mobile 2?uipment (!%M=M2)
interfaceH- /elease <
K3>L T!**.*3<I H/e?uirements on 3GPP system to wireless local area networ" (C5.&) interwor"inH
K3AL 3GPP T! 3,.,+,I H3%11=terminal interfaceJ Physical and loical characteristicsH
K38L OM. ;evice Manaement @,.* specifications
K39L OM. 1lient Provisionin @,., specifications
K3:L void
K<+L 3GPP T! **.,83I H %M! Multimedia Telephony !ervice and supplementary services = !tae ,H
K<,L 3GPP T! **.+9*I H 1all 7orwardin (17) supplementary services = !tae ,H
K<*L 3GPP T! **.*89I H!ervice /e?uirements for the 2volved Pac"et !ystem (2P!)H
K<<L 3GPP T! **.+8,I H5ocation !ervices (51!)J !ervice descriptionJ !tae ,H
K<>L 3GPP T/ **.:9>I H!ervice re?uirement for the 3GPP 3ser ;ata 1onverence (/elease :)H
K<AL ;; 12&ET! ,>8**I*++: N/oad Transport and Traffic Telematics- e!afety- e1all Minimum !et
of ;ata (M!;)O
K<8L 3GPP T! *3.**AI HGlobal te't telephony (GTT)J !tae *H
K<9L 3GPP T! **.**+I H !ervice re?uirements for Bome &ode0s and Bome e&ode0sH
K<:L 2T!% T! ,9, +,: @*.+.+ (*++8=,,)I HTelecommunications and %nternet convered !ervices and
Protocols for .dvanced &etwor"in (T%!P.&)J 0usiness 1ommunication /e?uirementsH
K>+L 3GPP T! *3.33>I H3ser ;ata 1onverence (3;1)J Technical reali(ation and information flowsHJ
stae *.
K>,L Open%; 7oundationI HOpen%; .uthentication *.+H- httpIEEopenid.netEspecsEopenid=
authentication=*P+.html.
2.2 6'4or5%ive re4ere'ces
K<3L G!M. P/; %/.3<I H%nter=!ervice Provider %P 0ac"bone GuidelinesH
3 7e4i'iio's, s85(o"s %'! %((revi%io's
3.1 7e4i'iio's
&'(( ))* Aut!entication: .uthentication performed between an !!O=capable 32 and 3GPP !!O %dentity Provider
usin Operator=controlled credentials and without re?uirin user involvement.
&'(( ))* +dentit# (rovider: .n entity that maintains Operator=controlled identity and credential information for a
user- performs 3GPP !!O .uthentication- and asserts the userQs identity to a ;ata .pplication Provider.
&rd (art# ))* +dentit# (rovider: .n entity that maintains identity and credential information (that is not Operator=
controlled) for a user- performs authentication- and asserts the userQs identity to a ;ata .pplication Provider.
Attended Data ,raffic: ;ata traffic of which the user is aware heEshe initiated- e.. based on the screenE"eypad loc"
bein deactivated- lenth of time since the 32 last received any input from the user- "nown type of application (e.. an
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1" Release 12
application monitorin a user#s health R HmBealthH R which may need its data always treated as .ttended ;ata
Traffic.)
eallI . manually or automatically initiated emerency call-(T!,*) from a vehicle- supplemented with a minimum set
of emerency related data (M!;)- as defined under the 23 1ommissionQs e!afety initiative.
Data Application (rovider: .n entity that offers data application services to users (e..- over the public %nternet).
The data applications can be browser or non=browser based services.
+-) entrali.ed )ervices: The provision of communication services wherein services and service control are based
on %M! mechanisms and enablers- and support is provided for a diversity of access networ"s (includin 1! domain
and %P based- wireless and wireline)- and for service continuity between access networ"s.
-)DI The Minimum !et of ;ata K<AL formin the data component of an e1all sent from a vehicle to a Public !afety
.nswerin Point or other desinated emerency call centre. The M!; has a ma'imum si(e of ,<+ bytes and includes-
for e'ample- vehicle identity- location information and time=stamp.
/A0 user plane con"estion: The situation where the demand for /.& resources to transfer user data e'ceeds the
available /.& capacity to deliver the user data for a sinificant period of time in the order of few seconds or loner.
))* (rovider: .n entity that provides !!O !ervice. The !!O Provider enables a user to authenticate to an %dP and
thereby to have their identity asserted to a ;.P. 2ach data application- whether provided by different ;.Ps or the
same ;.P- may have its own policy reardin authentication. %n the 3GPP !!O !ervice- the !!O Provider is the
3GPP Operator.
))* )ervice: . service in which the user of a data application is authenticated once- and as a result of that
authentication is provided with seamless and transparent access to multiple data applications offered by one or more
;ata .pplication Providers.
))* 1ocal 2ser Aut!entication: .uthentication performed by the 32 that establishes the presence of the reistered
user of the data application by re?uirin input which only the reistered user would be able to provide.
2nattended Data ,raffic: ;ata traffic of which the user is unaware heEshe initiated- e.. based on the screenE"eypad
loc" bein activated- lenth of time since the 32 last received any input from the user- "nown type of app (e.. an
application monitorin a user#s health R HmBealthH R may need its data never treated as 3nattended ;ata Traffic.)
7urther definitions are iven in 3GPP T/ *,.:+> K*:L.
3.2 &((revi%io's
7or the purposes of this T!- the followin abbreviations applyI
;.P ;ata .pplication Provider
%dP %dentity Provider
%@! %n @ehicle !ystem (e1all terminal and associated sub=systems in vehicle)
M2 Mobile 2?uipment
OTT Over The Top
P1 Personal 1omputer
!!O !inle !in=On
7urther abbreviations are iven in 3GPP T/ *,.:+> K*:L.
4 Ge'er%"
4.1 &i5s o4 3GPP s#eci4ic%io's
%t shall be capable of deliverin audio- te't- video and raphics direct to people and provide them with access to the
ne't eneration of information based services. %t moves mobile and personal communications forward from e'istin
systems- deliverin mass mar"et low=cost diital telecommunication and %P=based multimedia services.
The aims areI
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 11 Release 12
= to enable users to access a wide rane of telecommunications services- includin many that are today undefined
as well as multi=media and hih data rates.
= to facilitate the provision of a hih ?uality of service (particularly speech ?uality) similar to that provided by
fi'ed networ"sJ
= to facilitate the provision of small- easy to use- low cost terminals with lon tal" time and lon standby
operationJ
= to provide an efficient means of usin networ" resources (particularly radio spectrum).
4.2 S%'!%r!is%io' o4 Service +%#%(i"iies
2'istin systems have traditionally standardised the complete sets of teleservices- applications and supplementary
services which they provide. .s a conse?uence- substantial efforts are often re?uired to introduce new services or
simply to modify the e'istin one (customisation). This ma"es it more difficult for operators to differentiate their
services. .t the same time however- this may reduce the comple'ity of providin a service across different operatorsQ
networ"s.
3GPP shall therefore preferentially standardise service capabilities. %n circumstances where the service is meant to be
used across different operatorsQ networ"s- hence a common specification set is of paramount importance- the service
should be standardised to a level of detail sufficient to ensure interoperability and interwor"in across different
operatorsQ networ"s. !ervice capabilities consist of bearers defined by Do! parameters and the mechanisms needed to
realise services. These mechanisms include the functionality provided by various networ" elements- the
communication between them and the storae of associated data. This T! provides a conceptual description of a
service architecture and architecture re?uirements which aim to provide service capabilities. %t is intended that these
standardised capabilities should provide a defined platform which will enable the support of speech- video- multi=
media- messain- data- teleservices- user applications and supplementary services and enable the mar"et for services
to be determined by users and home environments.
4.2.1 Provisio' o4 service c%#%(i"iies i' s$%re! 'e2or9s
The provision of services and service capabilities that is possible to offer in a networ" shall not be restricted by the
e'istence of the networ" sharin %t shall be possible for a core networ" operator to differentiate its service offerin
from other core networ" operators within the shared networ".
%t shall be possible to control the access to service capabilities offered by a shared networ" accordin to the core
networ" operator the user is subscribed to.
4.3 E44icie' Use o4 *e2or9 Resources
4.3.1 *e2or9 Tr%44ic P%er's
!ervice capabilities shall ta"e account of the discontinuous and asymmetric nature of most teleservices- multimedia
services and user applications and consider the overheads and sinallin sure caused by fre?uent transmissions of
small amount of data by mobile data application- in order to ma"e efficient use of networ" resources (particularly radio
resources).
4.3.2 M%ss Si5u"%'eous Re3isr%io'
Chen a lare number of subscribers enter in a reistration area in which they have not reistered- the core and radio
access networ" shall be able to provide a capability to optimi(e the mass simultaneous reistration traffic at a iven
instance of time. The core and radio access networ" shall be able to "eep providin the service (e.. mobile oriinated
and mobile terminated services) without interruption for those subscribers who are oriinally in the cell which receive
the mass simultaneous reistration traffic.
4.3.3 R%!io 6'er4%ce
!ervice capabilities shall be provided in a wide rane of radio operatin environments (where a radio environment is
characterised in terms of propaation environment- mobile e?uipment relative speeds and traffic characteristics).
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 12 Release 12
.lthouh 3GPP aims to minimise the number of radio interfaces and to ma'imise commonality between them- it may
utilise several radio interfaces- each optimised for different environments. 2ach radio interface may provide differin
service capabilities. 3GPP specifications include 3T/.(&) radio interface supportin two modes (T;; and 7;;)- an
2volved 3T/.(&) radio interface and G2/.& radio interface. .dditionally- it may be possible to connect to the
3GPP system usin radio interfaces and fi'ed access technoloies specified outside of 3GPP.
3GPP specifications shall provide a mechanism which will enable a piece of user e?uipment (32) to adapt to different
radio interfaces as necessary and to determine the service capabilities available. The specifications shall also provide a
mechanism which will enable a 32 to select radio interfaces capable of providin appropriate service capabilities and
support mobility between multiple radio interfaces.
4.3.4 Re%"-i5e Resource Us%3e
To enable networ" operators to render services efficiently- dimension their networ"s and set tariffs that more
accurately reflect radio resource usae- real time information on resource usae is needed. Chen re?uested- it shall be
possible for the servin cell type (e.. /.T)- cell %; E 3T/.& !ervice .rea %dentity and cell E !ervice .rea capability
usae (e.. B!;P.- 2=;1B) information to be made available to the core networ". 1ell E !ervice .rea capability
usae information may include- for e'ample- user(s) identity- start and finish time of data transfer- up=lin" and down=
lin" data rates- volumes of data and other statistical information.
4.3.5 Se"ece! 6P Tr%44ic :44"o%! (S6PT:) 4or PS 7o5%i' o'"8
4.3.5.1 +o55o' Re;uire5e's 4or S6PT: i' $e Mo(i"e :#er%or *e2or9 %'!
S6PT: % $e Loc%" *e2or9
%t shall be possible to offload selected traffic (e.. internet) towards a defined %P networ" close to the 32#s point of
attachment to the access networ".
The followin re?uirements apply to !elected %P Traffic OffloadI
= The mobile operator may enableEdisable !elected %P Traffic Offload on a per 32 per defined %P networ" basis
(e.. based on tariff- subscription type etc.).
= %t shall be possible for %P traffic of a 32 associated with a particular defined %P networ" to be offloaded while
%P traffic of that same 32 associated with other defined %P networ"(s) is not offloaded.
= %t shall be possible to perform !elected %P Traffic Offload for pre=/elease ,+ 32s.
= Offloadin selected %P traffic for a 32 shall not affect services runnin in parallel for the same 32.
= The mobile operator shall be able to collect sinallin performance measurements (e.. session
connectionEdisconnection- etc) related to !elected %P Traffic Offload for each user.
= !elected %P Traffic Offload shall not compromise the security of the mobile operator#s networ".
= !ervice 1ontinuity of %P data session(s) for !elected %P Traffic Offload may be supported durin the followin
mobility eventsI
= mobility between the macro networ" and B(e)&0sJ and
= mobility between B(e)&0s.
;urin both these mobility events- based on home mobile operator policies- the impact of mobility events as
perceived by the user shall be reduced by minimisin any interruption to the data flow.
= %t shall be possible for the BP5M& to provide the @P5M& with the followin information for a particular userI
= .n indication of whether the userQs %P traffic is permitted to be subjected to !elected %P Traffic Offload
in the visited networ"J
= The defined %P networ"(s) for which !elected %P Traffic Offload is permitted.
/e?uirements specific to !%PTO at the local residentialEenterprise %P networ" can be found in section >.: in K<9L.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 13 Release 12
4.3.5.2 Re;uire5e's 4or S6PT: i' $e Mo(i"e :#er%or *e2or9
The followin re?uirements apply to !elected %P Traffic Offload in the mobile operator networ"I
= The mobile operator shall be able to enableEdisable !elected %P Traffic Offload for certain parts of the networ".
= !elected %P Traffic Offload shall not compromise interity and confidentiality of offloaded traffic.
= The mobile operator shall be able to collect statistics for the offloaded traffic for each user.
= The networ" shall be able to perform !elected %P Traffic Offload without any user interaction based on mobile
operator policies.
= !ervice 1ontinuity of %P data session(s) within the mobile operator networ" shall be supported for !elected %P
Traffic Offload. 0ased on home mobile operator policies- the impact of mobility events within the macro
networ" as perceived by the user shall be reduced by eitherI
= minimisin any interruption to the data flowJ or
= preventin interruption to the data flow e.. for voice services.
= !ervice 1ontinuity of %P data session(s) for !elected %P Traffic Offload may be supported durin the followin
mobility eventsI
= mobility between the macro networ" and B(e)&0sJ and
= mobility between B(e)&0s.
;urin both these mobility events- based on home mobile operator policies- the impact of mobility events as
perceived by the user shall be reduced by preventin interruption to the data flow e.. for voice services.
4.4 +o5#%i(i"i8 2i$ G"o(%" S%'!%r!s
3GPP specifications aim to be compatible with %MT=*+++ and to provide lobal terminal mobility (roamin)- enablin
the user to ta"e hisEher terminal to different reions of the world and to be provided with services. %t is probable that
different reions of the world will adopt different radio interface technoloies. %MT=*+++- as a lobal standard- should
therefore enable a %MT=*+++ terminal to determine the radio interface technoloy and the radio interface standard
used in a reion. Global terminal roamin also re?uires the lobal standardisation of service capabilities. .s far as
possible the method of indication of the radio interface standard and available service capabilities shall be alined with
%MT=*+++.
3GPP specifications shall enable users to access the services provided by their home environment in the same way via
any servin networ" provided the necessary service capabilities are available in the servin networ".
The 3GPP specifications will be available for the partner oranisations to adopt as their reional standards. 7or
e'ample in 2urope- 2T!% may adopt them as standards for both G!M and 3MT!.
4.5 Voi!
4.6 )u'cio'%"i8 o4 Servi'3 *e2or9 %'! <o5e E'viro'5e'
The followin functionality shall be the responsibility of the home environmentI
= 3ser .uthentication.
= !%ME3!%M %ssue.
= 0illin.
= 3ser ProfileE@B2 Manaement.
The followin functionality shall be the responsibility of the servin networ"I
= /adio or other means of access.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1$ Release 12
= Transport and sinallin.
The followin functionality may be the responsibility of either the servin networ"- the home environment or an
appropriate combination of both
= !ervice 1ontrol.
= Do! neotiation.
= Mobility manaement- includin roamin.
= .utomatic establishment of roamin areements.
4.0 PLM* &rc$iecure
The networ" is loically divided into a radio access networ" and a core networ"- connected via an open interface.
7rom a functional point of view the core networ" is divided into a Pac"et !witched 1& ;omain- %P Multimedia (%M)
1& subsystem K*8L and a 1ircuit !witched 1& ;omain. %M 1& subsystem utilises P! 1& domain bearer services.
1! 1& domain supports bearer independent transport. There is no difference in service offerin or 32 functionality
due to different transport.
. P! only 3GPP core networ" is possible as defined within the specification for the 2volved Pac"et !ystem (2P!)
K<*L.
7or further information see 3GPP T! *3.**, K*+L.
4.= 6'er2or9i'3 >e2ee' PLM* %'! ?ire"ess L&*s
.spects related to interwor"in between P5M& and C5.& are captured in T! **.*3< K3>L.
4.. *e2or9 S$%ri'3
&etwor" sharin shall be transparent to the user.
The specifications shall support both the sharin ofI
(i) radio access networ" onlyJ
(ii) radio access networ" and core networ" entities connected to radio access networ"
&oteI %n a normal deployment scenario only one or the other option will be implemented.
%t shall be possible to support different mobility manaement rules- service capabilities and access rihts as a function
of the home P5M& of the subscribers.
4.10 T$e Evo"ve! P%c9e S8se5
2volved Pac"et !ystem is an evolution of the 3G 3MT! characteri(ed by hiher=data=rate- lower=latency- pac"et=
optimi(ed system that supports multiple /.Ts. The 2volved Pac"et !ystem comprises the 2volved Pac"et 1ore
toether with the evolved radio access networ" (2=3T/. and 2=3T/.&).The service re?uirements for the 2volved
Pac"et !ystem are specified in T!**.*89 K<*L.
4.11 User 7%% +o'ver3e'ce
4.11.1 6'ro!ucio'
The 3;1 concept K<>L supports a layered architecture- separatin the data from the application loic in the 3GPP
system- so that user data is stored in a loically uni?ue repository allowin access from core and service layer entities-
named application front=ends. .nd such uni?ue repository shall be possible to be shared amon different P5M&s that
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1& Release 12
have trusted relationships.
&etwor" elements and functionalities should be desined to access profile data remotely and without storin them
permanently locally- i.e. the front=ends shall wor" in a subscriber dataless confiuration.
%n some cases- services may depend on user data scattered over 3;1 and other networ" elements. 3;1 may support
the ability to access necessary networ" elements to fetch user data on behalf of these services- while minimi(in
impacts on e'istin &etwor" 2lements in which the data is located.
.pplications can subscribe to specific events which will li"ely occur on specific user data- and those should be notified
when those events do appear. The events can be chanes on e'istin user data- addition of user data- and so on.
Third party applications and non trusted networ" elements should only be able to access the user data after proper
authentication and authori(ation ta"in into account security and privacy re?uirements- i.e. it should be possible to
present different views on the data to the parties which re?uire access- dependent on the authori(ation. 3;1 concept is
bac"wards compatible with 3GPP systems- i.e. it does not have an impact on traffic mechanisms- reference points and
protocols of e'istin networ" elements.
The 3;1 concept preserves user authentication and authori(ation of services across domains- ensurin secured usersQ
access to networ".
4.11.2 M%'%3e5e' o4 user !%%
;ue to the loical centrali(ation of user data- it is necessary for 3;1 to support the provisionin of the user data- that
is- user data manipulation li"e creation- deletion- readin- modification and other operations. Provisionin shall be
possible via an e'ternal system- self care or dynamically via applications offerin e.. user service confiuration
facilities.
Operations carried out in the framewor" of 3;1 shall support the .1%; (.tomicity- 1onsistency- %solation- and
;urability) characteristics.
4.11.3 User 7%% Mo!e""i'3
3ser ;ata Modellin refers to the different models that apply to user data converenceI %nformation Models and ;ata
Models.
.n %nformation Model denotes an abstract- formal representation of entity types- includin their properties and
relationships- the operations (e.. read- writeS) that can be performed on them- and related rules and constraints. %n
the information model- entities miht have networ" topoloy relationship with each other.
%n order to accommodate multiple applications and services- e'istin and new ones- a common baseline information
model shall be developed and shall- at minimum- clearly distinuish a number of concepts as entity typesI
= !ubscriber with relation to several users (e.. a company and its employees)-
= . user attached to different subscriptions (e.. for a private and a professional service usae)
= . user usin multiple devices (e.. mobiles or fi'ed)
= Groupin of users to certain cateories
= . particular user as member of a certain roup
= !ervice providersQ services provided by networ" operators
= 2nterprise services provided by networ" operators
The baseline information model shall be future proof. %t shall not be tied to any specific implementation of the data
base or its interfaces. %t shall provide fle'ibility (in its data structure and content)- e'tensibility and multi=application
approach.
0y e'tensible- it shall be understood that new applications andEor new service profiles can be added by the operator- if
necessary. The fle'ibility shall permit new data for e'istin applications to be introduced- or modified.
;ata Models are practical implementations of the information model- e.. Tree=li"e modellin. The common
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1' Release 12
information model shall allow derivin one or more data models. . reference data model shall be standardi(ed for the
messae e'chane over 3d interface K>+L- in order to enable multivendor interoperability.
2ach application shall only interface the 3;1 for the data it is dealin with- and not be impacted by other data that
3;1 stores for other applications. %t corresponds to the concept of a data view specific to a iven application.
.n application can allow access by other applications to data for which it is responsible. This can be done under
certain constraint customi(ed by operators.
.ccess to the 3;1 data shall be independent of the structure of the data models- i.e. the chanes in the data models
shall not affect the interface.
5 Evo"uio'
5.1 Su##or o4 2G services
The 3GPP specifications shall be capable of supportin e'istin *G services in a manner which is transparent to the
users of these services.
5.2 Provisio' %'! evo"uio' o4 services
!ince a phased approach has been adopted- the same eneral service principles shall apply to each phase. !upport of
services from an end user perspective is understood to be an important driver for established mobile users to stay with
their e'istin operator while ta"in the new services into use. %t is therefore important to enable operators to offer
continued support of leacy services in future releases. Previous release services shall as a principle also be supported
in the followin releases.
&etwor"s shall be capable of providin a specified core set of capabilities.
The core set of capabilities should permit home environment to offer a rane of distinctive services includin those
which cannot be implemented on systems based on previous release specifications.
%t shall be possible for the home environment to develop services with full roamin capability.
The radio interface should not unnecessarily restrict the development of new services (within physical limitations).
The standard shall provide a mechanism which allows a terminal to be easily upraded so that it can access new
services which are within the physical limitations of the terminal.
6 +"%ssi4ic%io' o4 services
%n the 1! 1& domain- the basic services are divided into circuit teleservices (3GPP T! **.++3 K,<L) and bearer
services (3GPP T! **.++* K*,L) and they can utilise standardised supplementary services (3GPP T! **.++< K>L).
The P! 1& ;omain provides %P bearer services. !M!- 3!!; and 33! can also be considered as bearer services for
some applications.
%P multimedia services are the %P based session related services- includin voice communications. %P multimedia
sessions use %P bearer services provided by the P! 1& ;omain.
@alue added non=call related services include a lare variety of different operator specific servicesEapplications. They
are usually not specified by 3GPP. The services can be based on fully proprietary protocols or standardised protocols
outside 3GPP.
%n order to create or modify the above services (both call and non=call related services) operators may utilise tool"its
standardised by 3GPP (such as 1.M25 or 51!) or e'ternal solutions (e.. %nternet mechanisms). Pre=paid is an
e'ample of an application created with tool"its that may apply to all of the above services cateories.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1( Release 12

Too"9is,
+&MEL
ME/E
(U)S&T
:6SP
L+S
@6'er'e oo"s@
ec...
+ircui
e"eservices
(22.003)
Te"e#$o'8
)&A
SMS
V%"ue
%!!e!
'o'-c%""
re"%e!
services
(e.3. eM%i",MMS,
???, *e2s,
ecB)
6P
5u"i5e!i%
services
(S6P)
(e.3. e"e#$o'8,
c$%,
2$ie(o%r!s)
:$er
>e%rer
services
SMS,UUS,
USS7
6P (e%rer services
+ircui
>e%rer
services
(22.002)
Su##"e5e'%r8
services
(22.004)
+i,ure 1- Service classification
0 Pri'ci#"es 4or 'e2 service c%#%(i"iies
0.1 Ge'er%"
3GPP specifications shall enable the user of a sinle terminal to establish and maintain several connections
simultaneously. %t shall efficiently cater for applications which have variable re?uirements relatin to specific Do!
parameters (e.. throuhput) whilst meetin other Do! tarets. %t shall also cater for applications which are able to
ta"e adapt to a rane of variations in Do!.
0.2 Mu"i5e!i%
3GPP specifications shall support development of multimedia services and provide the necessary capabilities.
Multimedia services combine two or more media components (e.. voice- audio- data- video- pictures) within one call.
. multimedia service may involve several parties and connections (different parties may provide different media
components) and therefore fle'ibility is re?uired in order to add and delete both resources and parties.
Multimedia services are typically classified as interactive or distribution services.
%nteractive services are typically subdivided into conversational- messain and retrieval servicesI
1onversational services are real time (no store and forward)- usually bi=directional where low end to end delays (T ,++
ms) and a hih deree of synchronisation between media components (implyin low delay variation) are re?uired.
@ideo telephony and video conferencin are typical conversational services.H
Messain services offer user to user communication via store and forward units (mailbo' or messae handlin
devices). Messain services miht typically provide combined voice and te't- audio and hih=resolution imaes.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1) Release 12
/etrieval services enable a user to retrieve information stored in one or many information centres. The start at which
an information se?uence is sent by an information centre to the user is under control of the user. 2ach information
centre accessed may provide a different media component- e.. hih resolution imaes- audio and eneral archival
information.
;istribution services are typically subdivided into those providin user presentation control and those without user
presentation control.
;istribution services without user control are broadcast services where information is supplied by a central source and
where the user can access the flow of information without any ability to control the start or order of presentation e..
television or audio broadcast services.
;istribution services with user control are broadcast services where information is broadcast as a repetitive se?uence
and the ability to access se?uence numberin allocated to frames of information enables the user (or the userQs
terminal) to control the start and order of presentation of information.
0.2.1 +ircui S2ic$e! (+S) 5u"i5e!i% c%""s
1! multimedia call is a 0earer !ervice which utilises !ynchronous Transparent ;ata service. The followin basic
re?uirements shall be supported for 1! multimedia calls K*<LI
= 1! multimedia call shall be based on a 3GPP specific subset of B.3*<M.
= .ll call scenarios shall be supported- i.e. Mobile Oriinatin and Mobile Terminatin call aainst Mobile-
%!;& and P!T& call party.
= !inle and multiple numberin schemes shall be supported.
= 7allbac" to speech (T! ,, K,<L) shall be supported from 3.,"B( 2't. P5M& multimedia bearer- i.e. if setup of
the multimedia call fails the call will be set up as a speech call.
= !ervice chane and fallbac" shall be supported for 3;%E/;% multimedia bearer and speech- to allow fallbac" to
a less preferred service if the preferred service is unsupported- and to chane the service between speech and
multimedia durin the call.
= %n the case where a 1! multimedia call includes speech (e.. video call) then the followin re?uirements applyI
= . user shall be able to chane between a speech and 1! multimedia call- when desired.
= Chen the 1! multimedia call is no loner supported- for e'ample due to deraded coverae conditions
(includin 3T/.& to G2/.& only transitions)- service chane shall occur automatically from a 1!
multimedia call to speech.
= Chen a 1! multimedia call can be supported- for e'ample due to improved coverae conditions (includin
G2/.& only to 3T/.& or 3T/.&EG2/.& transitions)- service chane bac" to the 1! multimedia call
may be initiated by the networ".
= Other services than 1! multimedia call may e'ist which utilise the !ynchronous Transparent ;ata service.
!ervice transition toEfrom speech described for 1! multimedia call in this clause shall only apply to 1!
multimedia call and not !ynchronous Transparent ;ata services in eneral.
= ;ifferent bitrates as specified at 3GPP T! **.++* K*,L shall be supported.
= !upplementary services apply to multimedia calls as for !ynchronous Transparent ;ata service accordin to
3GPP T! **.++<K>L.
= Chen acceptin a multimedia call- the user shall be able to re?uest a service chane to speech before the call is
answered- such that the multimedia path is never actually connected throuh to the userQs phone.
= The user shall be able to deny a service chane to multimedia durin the call.
0.2.2 6P 5u"i5e!i% (6M) sessio's
%P multimedia services are not the evolution of the circuit switched services but represent a new cateory of services-
mobile terminals- services capabilities- and user e'pectations. .ny new multimedia service- which may have a similar
name or functionality to a comparable standardised service- does not necessarily have to have the same loo" and feel
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 1* Release 12
from the user#s perspective of the standardised service. @oice communications (%P telephony) is one e'ample of real=
time service that would be provided as an %P multimedia application.
The followin basic re?uirements are be supported for %P multimedia K*8LI
= %P multimedia session control shall be based on !%P K*9L.
= .ll session scenarios shall be supportedJ i.e. Mobile Oriinatin and Mobile Terminatin sessions aainst
%nternetE%ntranet- 1! or %M Mobile- %!;&- P!T& call party.
= M!%!;& and !%P 3/5 numberin and addressin schemes shall be supported.
= %P multimedia applications shall as a principle- not be standardised- allowin service provider specific
variations.
0.2.3 Mu"i5e!i% Mess%3i'3 Service (MMS)
The followin basic re?uirements are be supported for MM!I
= !tore=and=forward multimedia messain service with mobile and non=mobile users K*>L.
= MM! shall be capable of supportin interation of different types of messain (e.. fa'- !M!- Multimedia-
voicemail- e=mail etc.) in a consistent manner.
= !treamed and batch delivery for both messae download from the networ" to the terminal- and messaes
upload from the terminal to the networ".
0.2.4 Te/ +o'vers%io'
Global Te't Telephony ( GTT ) is a feature that enables real=time te't conversation K*AL.
= GTT enables real time- character by character- te't conversation to be included in any conversational service-
1ircuit !witched as well as %P based.
= %t is possible to use the te't component in a session toether with other media components- especially video and
voice.
= %nterwor"in with e'istin te't telephony in P!T& as well as emerin forms of standardised te't conversation
in all networ"s is within the scope of this feature.
= The te't media component can be included initially in the session- or added at any stae durin the session.
= The te't component is intended for human input and readin- and therefore supports human capabilities in te't
input speed. The character set support is suitable for the lanuaes the users communicate in.
= GTT specifies limited interoperation with Multimedia Messain !ervices includin a possibility to divert to
messain in case of call failure and sharin user interface e?uipment and e'ternal 32 interfaces.
0.2.5 P%c9e S2ic$e! Sre%5i'3 Service
The followin basic re?uirements are to be supported for streamin I
= The streamin service uses a client E server model which is transparent to the P5M&. The client controls the
initiation and e'ecution of the service.
= The streamin service K3+L shall use e'istin standards (codecs and protocols K3,L) where these are available.
= The streamin service utilises the P! ;omain with the Do! re?uirements as specified in 3GPP T! **.,+> K,L.
0.3 Service M%'%3e5e' Re;uire5e's
3GPP specifications shall include standardised protocols enablin service manaement. %t shall enable control-
creation and subscription of service capabilities and services- and the manaement of user profiles.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2" Release 12
0.4 &uo5%ic 7evice 7eecio'
The home environment should be automatically notified when a user- identified by a !%ME3!%M- has chaned M2 and
should be informed of the identity of the new M2. This should be applicable to any M2. %t should also be possible to
achieve .utomatic ;evice ;etection for users usin any !%ME3!%M.
&oteI The purpose of this is to enable an automatic confiuration of terminals by the operator for specific
applicationsEservices if so needed. The procedure for such an automatic confiuration need not to be
standardi(ed by 3GPP.
The notification that a user has chaned M2 shall be iven as early as possible.
= Service %rc$iecure
%n order to provide standardisation of service capabilities a service architecture shown by 7iure * is envisaed

Mo(i"i8
M%'.
+%""
+o'ro"
>e%rer
+o'ro"
Service P"%4or5
?ire! Su('e2or9
?ire"ess Su('e2or9
U6M
Te"eservice1
&##"ic%io'
MM6
Su##". Service
)i3ure 2, Service &rc$iecure
Mu"i5e!i% service1
+i,ure 2- Service Architecture
. number of bearers shall be provided that can differ in fle'ibility and offer different capabilities. 0earers may be
characterised by parameters such as HthrouhputH- Hdelay toleranceH- Hma'imum bit error rateH- HsymmetryH etc. These
bearers enable information to be transferred appropriate to the provision of teleservices- multimedia services and end
user applications enerally- via subnetwor"s which typically provide different specified ?ualities of service.
The assinment and release of bearers is provided by the bearer control function. Provision should be made for several
bearers to be associated with a call and for bearers to be added to a call andEor to be released from a call followin call
establishment. The bearers should be independent of radio environments- radio interface technoloy and fi'ed wire
transmission systems.
.daptationE%nterwor"in functions are re?uired in order to ta"e account of the differences between the bearers used for
the provision of a teleserviceEmultimedia serviceEapplication in the fi'ed networ" and the bearers.
.daptationE%nterwor"in functions are re?uired which ta"e account of the discontinuous andEor asymmetrical nature
of most teleservicesEmultimedia servicesEapplications.
The service platform shall provide interfaces (to servin networ"s and home environments) appropriate to the support-
creation and control of supplementary services- teleservices- multimedia services and user applications. The service
platform will also provide interfaces enablin subscribers to control supplementary services- teleservices- multimedia
services and user applications.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 21 Release 12
!upplementary service provision and control will be independent of radio operatin environment- radio interface
technoloy and fi'ed wire transmission systems.
.s far as possible- the service platform is re?uired to enable new supplementary services- teleservices- multimedia
services andEor end user applications to be supported at minimum cost- with minimum disruption of service and within
the shortest possible time.
. Cu%"i8 o4 Service (CoS)
The Duality of !ervice (Do!) parameters should be identified toether with appropriate parameter values which set
tarets to be reached when desinin 3GPP specifications- and which also will serve as uidelines for networ" desin
and service provision.
The Do! for call set=up time- as an e'ample- can be defined in terms of a mean value and as a percentae of cases
which should not e'ceed a certain time limit. 7urther information can be found in 3GPP T! **.,+>K,L.
The performance re?uirements for the .ll=%P &etwor" can be found in 3GPP T! **.*89K<*L.
7or 32 initiated Do! control OM. device manaement shall be the primary method for provisionin Do! parameters.
10 E5er3e'c8 +%""s
10.1 Ge'er%" re;uire5e's
%t shall be possible to establish an emerency speech call or GTT K*AL call (subject to national re?uirements). The term
U2merency callQ henceforth refers to speech calls- and GTT 2merency calls if applicable. The term Nother mediaO
henceforth refers to media other than speech and GTT. !upport of other media types durin an emerency call when
the %M 1& subsystem is used is referred to as #%M! Multimedia 2merency !ession# (M2!) and is specified in
subclause ,+.<.*. 2merency calls will be routed to the emerency services in accordance with national reulations for
where the subscriber is located. This may be based upon one or more default emerency call numbers stored in the
M2. %t shall be allowed to establish an emerency call without the need to dial a dedicated number to avoid the mis=
connection in roamin case- such as menu- by use of a #red button#- or a lin"ae to a car air ba control. 2merency
calls shall be supported by the 32 without a !%ME3!%ME%!%M bein present. &o other type than emerency calls shall
be accepted without a !%ME3!%ME%!%M.
2merency calls shall be supported by 32s that are subject to service restrictions- e.. for 32s campin on a cell in a
forbidden P5M& or in a forbidden 5. (see 3GPP T! **.+,, K,,L)- or on a 1!G cell without the subscriber bein a
member of that 1!G (see 3GPP T! **.**+ K<9L). !uch emerency calls shall be accepted by the networ" if re?uired by
local reulation.
The 2merency service is re?uired only if the 32 supports voice.
&ote ,I %t will be left to the national authorities to decide whether the networ" accepts emerency calls without
the !%ME3!%ME%!%M.
%t shall be possible to initiate emerency calls to different emerency call centres- dependin on the type of emerency.
The followin types of emerency calls shall be possibleI
= Police
= .mbulance
= 7ire 0riade
= Marine Guard
= Mountain /escue
= Manually %nitiated e1all (M%e1)
= .utomatically %nitiated e1all (.%e1)
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 22 Release 12
= !pare
Chen a !%ME3!%M is present- subscriber specific emerency call set=up MM% shall be provided. The Bome
2nvironment operator shall specify preferred emerency call numbers (e.. ::: for 3$ citi(ens or ,,+- ,,9 and ,,:
for Vapanese citi(ens). These emerency call numbers shall be stored in the !%ME3!%M and the M2 shall read this and
use any entry of these diits to set up an emerency call. %t shall be possible to store more than one instance of this
field.
&ote *I /elease #:9 and earlier !%M cards have the capability to store additional emerency call numbers.
Bowever in many cases this has not been used.
%t shall be possible to tie any emerency call number to any sinle emerency call type or to any combination of
emerency call types. The association between emerency call numbers and emerency call type shall be able to be
prorammed by the Bome 2nvironment operator into the !%ME3!%M.
2'ampleI
,: Police (.lbania)
,++ Police and 7ire 0riade (Gree" cities)
,++ .mbulance and 7ire 0riade (0elium)
,,* Police and .mbulance (%taly)
,,* General emerency call- all cateories (!weden)
,,> 7ire 0riade (%taly)
,<< .mbulance (.ustria)
%f the 32 does not reconise the emerency call numbers but the servin networ" reconises the dialled number as an
emerency call number used in the country- a normal call set up shall ta"e place over the radio interface and after the
servin networ" has reconised the emerency number the call shall be routed as an emerency call.
The user friendly MM% that specifies the type of emerency call directly (e.. menu) should be supported for use in any
(i.e. home or visited) P5M& to avoid the mis=connection in roamin case. This shall be allowed both with and without
!%ME3!%M bein present.
Chen emerency call establishment is initiated- the emerency call type shall be sent by the 32 if it is available.
The servin networ" may download emerency call numbers to the 32 in order to ensure that local emerency call
numbers are "nown to the 32. The 32 shall reard these emerency numbers as valid in that country only (as
identified by the M11) and shall discard them when a new country is entered.
&ote 3I The 32 can inform the user if the emerency call type for an emerency number received from the
servin networ" differs from that confiured on the 3!%ME!%M for the same number. Bow this is
implemented is outside the scope of 3GPP and ta"es into consideration operator policy and reulatory
re?uirements.
%f permitted by local reulation- it shall be possible for the user to prevent the sendin of his public user identifiers and
the location information to the P!.P (i.e. emerency response centre).
&ote <I Operator policies (e.. re?uirements for support of emerency communications) may over=ride the user
re?uest for suppression.
10.1.1 6!e'i4ic%io' o4 e5er3e'c8 'u5(ers
The M2 shall identify an emerency number dialled by the end user as a valid emerency number and initiate
emerency call establishment if it occurs under one or more of the followin conditions. %f it occurs outside of the
followin conditions- the M2 should not initiate emerency call establishment but normal call establishment.
2merency number identification ta"es place before and ta"es precedence over any other (e.. supplementary service
related) number analysis.
a) ,,* and :,, shall always be available. These numbers shall be stored on the M2.
b) .ny emerency call number stored on a !%ME3!%M when the !%ME3!%M is present.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 23 Release 12
c) +++- +9- ,,+- :::- ,,9 and ,,: when a !%ME3!%M is not present. These numbers shall be stored on the M2.
d) .dditional emerency call numbers that may have been downloaded by the servin networ" when the !%ME3!%M
is present.
10.1.2 7o5%i's #riori8 %'! se"ecio' 4or UE %e5#s o e5er3e'c8 c%""
10.1.2.1 Voice %'! GTT o'"8
. 32 that is connected to a domain in which it is possible for the 32 to ma"e non emerency calls usin the
particular media re?uested by the user- shall use that domain to attempt an emerency call unless servin networ"
policy (based on reulatory re?uirements and operator needs) re?uires the 32- includin an unauthenticated 32- to
attempt the emerency call on a specific domain first.
%f the 32 is connected to more than one domain in which it is possible for the 32 to ma"e non emerency calls usin
the particular media re?uested by the user- the 32 shall attempt an emerency call on the same domain it would use to
oriinate a non=emerency call usin the same media unless servin networ" policy (based on reulatory re?uirements
and operator needs) re?uires the 32- includin an unauthenticated 32- to attempt the emerency call on a specific
domain first.
%n the case where an emerency call attempt by a 32 fails- the 32 should automatically ma"e a second attempt on the
other domain if the 32 supports it.
%f the user aborts the emerency call setup durin the subse?uent automatic attempt and immediately tries to set up an
emerency call aain- then the 32 shall immediately attempt in the domain in which the user aborted the emerency
call.
10.1.2.2 :$er 5e!i%
The followin applies in addition to ,+.,.*.,.
%f an emerency call attempt that includes a re?uest for both (i) voice andEor GTT and (ii) other media cannot be
supported or fails in all connected access types in the P! 1& domain- the 32 shall attempt the emerency call in the
1! domain if available and shall only include the re?uest for voice andEor GTT.
10.1.3 +%""->%c9 Re;uire5e's
!ubject to localEreional reulations the networ" shall support a call=bac" from a P!.P.
%t shall be possible to supply the userQs ;irectory &umberEM!%!;&E!%P 3/% as the 15% to the P!.P to facilitate call=
bac". The 15% used on call=bac" shall allow the P!.P to contact the same terminal that oriinated the emerency call.
%f the incomin call can be identified by the core networ" as a call=bac" to an emerency call (i.e. comin from a
P!.P) then supplementary services at the terminatin party shall be handled as described in T! **.,83 K<+L for
Multimedia Telephony (e.. 1ommunication ;iversion- 1ommunication Bold- 1ommunication 0arrin).
&oteI There is no specific callbac" re?uirement for 1! supplementary services.
. call=bac" may be attempted for a period of time defined by local reulations after the emerency call release. %n case
of a 32 in limited service state- call=bac" is not re?uired.
10.2 E5er3e'c8 c%""s i' $e +S +* 7o5%i'
. 1! 1& ;omain shall support the emerency call teleservice as defined in 3GPP T! **.++3 K,<L (T!,*).
%f a 32 supports T!,,(Telephony)K,<L- then it shall also support T!,*(2merency 1alls)K,<L. %t shall be possible to
set up emerency calls initiated by an emerency call number.
10.3 E5er3e'c8 +%""s i' $e PS +* 7o5%i'
Cithout the %M 1& subsystem- emerency calls are not supported in the P! 1& domain.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2$ Release 12
10.4 E5er3e'c8 c%""s i' $e 6M +* su(s8se5
10.4.1 Ge'er%"
The %M 1& subsystem shall support %M! emerency calls. %t shall be possible to set up emerency calls initiated by an
emerency call number.
%f a 32 supports %M! Multimedia Telephony service with speech media as specified in T! **.,83 K<+L via an access
networ"- then it shall also support %M! emerency calls via that access networ".
!ubject to the reulatory re?uirement- the %M 1& subsystem shall be able to unambiuously identify each emerency
service defined in the national numberin plan for the country in which the 32 is located.
%n accordance with national reulations for where the subscriber is located- if the 32 does not reconise a dialled
number as an emerency call number but the %M 1& where the subscriber is located does reconise the dialled number
as an emerency call number (e.. a number used in the local emerency numberin plan) then the call shall be routed
as an emerency call indicatin the type of emerency service to the correct P!.P. !ubject to operator settin the call
may be prioriti(ed.
&ote ,I The above does not preclude the networ" rejectin the call and re?uestin the 32 to setup a new
emerency call to the same emerency service.
2merency calls may be initiated usin a private numberin plan K<:L.
&ote *I There can be an overlap between the private numberin plan of a hosted enterprise and the public
numberin plan- which ma"es translation of emerency numbers necessary.
2merency calls may be initiated by a service when re?uested by the user.
&ote 3I %t is not intended to enable automatic setup of emerency calls.
&ote <I Only speech and GTT=%P K<8L media are supported- when re?uired per subclause ,+.,- for emerency
services towards a 1! P!.P.
.n emerency call shall ta"e precedence over any other services a 32 may be enaed in- if re?uired by local
reulation.
2merency calls from an unauthenticated 32 (as far as the %M 1& is concerned) shall be supported by the %M 1&
subsystem- if re?uired by local reulation.
!ubject to reulatory re?uirements- when 32s must be authenticated- both the networ" and the 32 shall support the
same authentication and security methods that are used for non=emerency sessions.
10.4.2 6MS Mu"i5e!i% E5er3e'c8 Sessio's
10.4.2.1 Ge'er%"
7or %M! emerency calls towards %P P!.Ps- other media types may be supported by the 32 and the %M!- subject to
reulatory re?uirements.
The media types that may be supported durin an %M! M2! includeI
= /eal time video (simple'- full duple')- synchroni(ed with speech if presentJ
= !ession mode te't=based instant messainJ
= 7ile transferJ
= @ideo clip sharin- picture sharin- audio clip sharinJ
= @oiceJ and
= GTT.
&ote ,I .n %M! M2! need not contain voice or GTT.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2& Release 12
To avoid interwor"in issues- a 32 and %M! that supports te't based instant messain shall support a common
session mode te't=based instant messain protocol.
%M! M2! does not include support for leacy store and forward messain such as the !hort Messain !ervice
(!M!).
1alls from non=human associated devices (e.. fire alarms) are outside the scope of this specification.
.ddin- removin and modifyin individual media toEfrom an %M! M2! shall be supported.
.n %M! M2! is not a subscription service. . 32 capable of %M! emerency calls and capable of supportin the other
media types should also be able to support initiation of an %M!M2!.
.n %M! M2! from an unauthenticated 32 (as far as the %M 1& is concerned) shall be supported by the %M 1&
subsystem- if re?uired by local reulation.
%M! M2! shall be supported by 32s that are subject to service restrictions- e.. for 32s campin on a cell in a
forbidden P5M& or in a forbidden 5. (see 3GPP T! **.+,, K,,L)- or on a 1!G cell without the subscriber bein a
member of that 1!G (see 3GPP T! **.**+ K<9L). !uch %M! M2! shall be accepted by the networ" if re?uired by local
reulation.
.n %M! M2! shall support providin the location of the 32- in a manner similar to %M! emerency voice calls.
.n %M! 32 that supports %M! M2! shall identify an emerency number dialled by the end user as a valid emerency
number utili(in the same mechanisms as used for %M! emerency voice calls as defined in subclause ,+.,.,.
&ote *I This capability supports the eneral public- includin facilitatin emerency communications by
individuals with disabilities (e.. persons who are deaf- deaf=blind- hard of hearin- or have a speech
disability).
.n oriinatin networ" and 32 may support some or all of these other media types- and support of any specific media
by an oriinatin networ" or 32 may be subject to reulatory re?uirements.
@oice call continuity per clause *, shall be supported when a 32 with an active %M! M2! with voice and other media
moves out of %M! voice coverae and voice call continuity is supported by the 32 and networ". The remainin media
(i.e. voice call) then becomes a 1! emerency call e.. T!,* call for 3GPP systems as defined in 3GPP T! **.++3
K,<L.
Other media shall be dropped when a 32 with an active %M! M2! moves out of %M! voice coverae- irrespective of
whether or not there is an active voice session.
10.4.2.2 UE Re;uire5e's
Chen %M! M2! are supported by the 32- the followin applyI
= .n %M! 32 that supports %M! M2! shall also support %M! emerency voice calls.
= Once a 32 is aware that an %M! M2! has been initiated- the 32 shall be able to (subject to user confiuration)
avoid drawin unnecessary attention to the user (e..- playin audible tones or flashin brihtly) and should
confirm this to the user in as private a manner as is reasonable e.. usin te't on the screen or audio if
headphones are already connected. 32 behaviour in an %M! M2! may need to be different relative to the
normal confiuration.
= The 32 should clearly differentiate %M! emerency session=mode te't based instant messain from %M! non=
emerency session=mode te't based instant messain on the user display.
= The %M! 32 supportin video transfer durin an %M! M2! should be able to deliver recorded media in a form
that allows proressive playbac". (%t is desirable that all pre=recorded media sent durin an emerency session
be proressively viewable.)
= Chen an %P P!.P attempts to add additional media to an e'istin %M! M2!- the user shall be made aware of
this. Chen additional media is re?uested by the P!.P- the user shall be able to permit or deny it.
= The 32 shall provide an indication to the user for each re?uested media- whether it was successfully or
unsuccessfully established.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2' Release 12
= 7urther notifications of added and removed media shall be indicated to the user while the %M! M2! is active.
= %f none of the media re?uested by the 32 is successfully established- the %M! M2! will fail and an %M! M2!
failure indication shall be provided to the user.
= %n handover of an %M! M2! where other media is dropped when %M! M2! is not supported- the 32 shall
indicate to the end user that the other media is not supported in this area.
The followin re?uirements for %M! emerency voice calls also apply when an %M! M2! is supported by the 32I
= .n %M! 32 that supports %M! M2! shall indicate to the networ" that the call is an %M! emerency call as is
done for an %M! emerency voice call.
= .n %M! 32 that supports %M! M2! shall be able to receive an %M! call=bac" from a P!.P per clause ,+.,.3
with voice- GTT or other media per clause ,+.<.*.,.
= .n %M! 32 that supports M2! shall utili(e the same trust and security mechanisms for the other media as
utili(ed for an %M! emerency voice call.
= Chen roamin- a 32 shall oriinate an %M! M2! in the servin networ" in the same manner as for %M!
emerency voice calls.
10.4.2.3 :ri3i'%i'3 *e2or9 Re;uire5e's
Chen an %M! M2! is enabled by the oriinatin networ"- the followin applyI
= Other media shall only be supported in pac"et=based networ"s that support %M! emerency voice calls.
= The oriinatin networ" shall deliver all media to the same %P P!.P throuhout the duration of the %M! M2!.
= The networ" shall indicate to the 32- for each re?uested media- whether it was successfully or unsuccessfully
established.
= 7urther notification of added and removed media shall be provided to the 32 while the %M! M2! is active.
= %f none of the media re?uested by the 32 is successfully established- the %M! M2! will fail and an %M! M2!
failure indication will be provided to the 32.
The followin re?uirements for %M! emerency voice calls also apply when %M! M2! is supported by the networ"I
= !ubject to reional reulatory re?uirements- the networ" shall be able to authenticate the 32 usin the same
procedures as for %M! emerency voice calls.
= The oriinatin networ" shall provide the capability to enable an %M! 32 supportin %M! M2! to obtain local
emerency numbers or other emerency address(es) (e.. destination address) utili(in the same mechanism as
used for %M! emerency voice calls.
= .n %M! M2! shall be provided in the local servin networ".
= 7or an %M! M2!- any "ind of emerency addressin (e.. !%P 3/%s- Tel 3/%s) and special indications for
emerency sessions shall be treated in the same manner as %M! emerency voice calls.
= The oriinatin networ" should detect all %M! M2!s reardless of the 32 emerency call indication.
.ccordin to operator policy- the oriinatin networ" may either inform the 32 to enable re=oriination as an
%M! M2! or support oriination of the initial call.
= The oriinatin networ" shall be responsible for routin the %M! M2! towards the appropriate P!.P (e..-
based on emerency service type- location- or policy).
= The networ" shall be able to provide interity protection- andEor privacy for other media similar to that
provided for %M! emerency voice calls.
= .n %M! M2! shall utili(e the same priority mechanisms as %M! emerency voice calls.
= ;etailed lo records of the %M! M2! shall be enerated by the oriinatin networ" in a similar manner to %M!
emerency voice calls and subject to reulatory re?uirements.
= .ll media content within the %M! M2! shall be carried with an indication of the source- in a similar manner as
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2( Release 12
for %M! emerency voice calls.
10.5 Voi!
10.6 Loc%io' &v%i"%(i"i8 4or E5er3e'c8 +%""s
&ational reulations may re?uire wireless networ"s to provide the emerency callerQs location. This re?uirement
typically overrides the callerQs riht to privacy with respect to their location bein revealed- but remains in effect only
as lon as the authorities need to determine the callerQs location. The interpretation of the duration of this privacy
override may also be different- subject to national reulation. 7or e'ample- some countries re?uire location to be
available from the wireless networ" only while the call is up- while others may allow P!.PQs to unilaterally decide
how lon the location must be made available.
Therefore- the re?uirement for providin location availability is to allow the networ" to support providin a mobile
callerQs location to the authorities for as lon as re?uired by the national reulation in force for that networ".
&oteI !ee T! **.+8, K<<L for location service re?uirements on emerency calls.
10.0 Tr%'s4er o4 !%% !uri'3 e5er3e'c8 c%""s
2merency calls may be supplemented with emerency related data K,L. Typically this data enables the accurate
eoraphic location of a manually or automatically activated emerency callin device e.. an in vehicle system (%@!)-
to be provided to the Public !afety .nswerin Point (P!.P).
The followin re?uirements apply to 32s desined to be able to perform transfer of data durin an emerency call and
to networ"s supportin transfer of data durin an emerency callI
= The data may be sent prior to- in parallel with- or at the start of the voice component of an emerency call.
= !hould the P!.P re?uest additional data then this may be possible durin the established emerency call.
= The realisation of the transfer of data durin an emerency call shall minimise chanes to the oriinatin and
transit networ"s.
= 0oth the voice and data components of the emerency call shall be routed to the same P!.P or desinated
emerency call centre.
= The transmission of the data shall be ac"nowleded and if necessary data shall be retransmitted.
= The 32 shall indicate at call setup if the emerency call will carry supplementary data.
32s desined to be able to perform transfer data durin emerency calls and confiured to only perform emerency
calls with transfer of data (e1all only mode) shall comply with the followin additional re?uirementsI
= The 32 shall not perform mobility manaement procedures- includin reistration on a P5M&- e'cept when
attemptin to initiate and durin an emerency call- or to initiate a test or reconfiuration of the terminal upon
re?uest from the user..
= 7or 32s that have the ability to be called bac" by the P!.P- the 32 shall be capable to continue mobility
manaement procedures for a limited duration followin the termination of the e1all.
= The 32 shall contain an 3!%M application.
= %n the case where the user subscribes to other services provided by the P5M&- it shall be possible for the
networ" operator to reconfiure the 32 so that it can access the subscribed services.
= %t shall be possible for the user of the 32 to chane networ" operatorEservice provider (i.e. to use a different
3!%M) or for the subscriber to modify the e'istin subscription used with the 32.
= %t shall be possible for the 32 upon re?uest from the user to initiate a call to an operator desinated non=
emerency M!%!;& for the purpose of accessin test and terminal reconfiuration services.
.dditional national and reional re?uirements are as specified in .nne' ..
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2) Release 12
10.= Su##"e5e'%r8 service i'er%cio' !uri'3 e5er3e'c8 c%""s
!upplementary services that interrupt or divert the media path between a P!.P and the end device shall be handled as
specified in T! **.,83 K<+L (e.. 1ommunication Bold) for Multimedia Telephony. &o such !upplementary !ervices
are applicable to 1! 2merency 1alls (T!,*) accordin to T! **.++< K>L.
11 *u5(eri'3 #ri'ci#"es
The followin networ" addressin schemes listed below shall be supported at the relevant domainsI
= 2.,A<-
= 2.,A9-
= 2.*,*-
= G.,*,
= %nternet (includin e.. %P address- !%P 3/%).
11.1 *u5(er #or%(i"i8
11.1.1 Re;uire5e's 4or +S +* !o5%i'
!ome numberin schemes shall be fully independent of the supportin servin networ" and the home environment-
allowin users to transfer this number to another home environment. 7or further information see 3GPP T! **.+AA K8L.
.n M!%!;& shall be allocated to each new user at the start of a subscription. This number may be allocated from one
of several numberin domains. 7or e'ampleI
= home E servin environment numberin schemeJ
= national numberin schemeJ
= reional numberin schemeJ
= lobal numberin scheme.
. user shall be able to move subscription from one home environment to another without chanin the M!%!;&
provided that the new home environment offers service in the same eoraphic domain. %t is envisaed that home
environment s will be able to allocate M!%!;&s from each of these domains as re?uired.
11.1.2 Re;uire5e's 4or PS +* !o5%i'
&one identified.
11.1.3 Re;uire5e's 4or 6M +* su(s8se5
%t shall be possible to offer number portability for 2.,A< numbers within %M 1& subsystem. 7or further information
see 3GPP T! **.+AA K8L.
11.2 Evo"uio' #%$
!ince 3GPP specifications aim to be alined with %MT=*+++- a primary oal in numberin is the provision of lobal
user numberin in line with steps ta"en by the %T3 = !G*.
The numberin scheme and networ" implementation chosen shall allow for internationalElobal evolution.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 2* Release 12
11.3 Voi!
11.4 Voi!
11.5 Voi!
11.6 Priv%e 'u5(eri'3
. user may wish to use private numbers for the purposes of callin fre?uent numbers. Therefore there is a re?uirement
for the use- by the user- of Private &umberin Plans (P&Ps). These schemes may belon to the user himself- to a home
environment or a third party.
11.0 *u5(eri'3 sc$e5es
11.0.1 Mu"i#"e 'u5(eri'3 sc$e5e
The standards shall support the possibility of allowin the bearer service associated with an MT call to be implicitly
defined by the destination M!%!;&- for e'ample to use a different M!%!;& to establish voice- fa' or data . %t will be
possible for multiple M!%!;&s to be associated with a sinle subscription.
11.0.2 Si'3"e 'u5(eri'3 sc$e5e
The standards shall support the possibility of allowin MT calls of different bearer types (e voice- fa'- data) to be
routed to a sinle M!%!;&. %t is reconised that the implementation of this may depend on the availability of bearer
information associated with an incomin call from the adjoinin transit networ". %n particular the standards will
support this possibility in the case of an adjoinin %!;& transit networ".
11.0.3 &!!iio'%" 'u5(ers
The 3GPP system shall support the possibility to assin an additional M!%!;&- in addition to the oriinal M!%!;&-
to a user with a connection to the P! 1& domain. %f this additional M!%!;& is available it shall be used for
correlation of 1! and %M! in voice call and service continuity as well as %M! 1entrali(ed !ervice. %n this case the
oriinal M!%!;& may be used for charin and O.FM purposes and forwarded to the P! ateway to other pac"et
data networ"s.
11.= :#i5%" roui'3
The implementation of the numberin scheme used shall allow for optimal routinJ i.e. routin shall not ta"e place
simply on the number dialled.
!ee 3GPP T! **.+8: K9L for some scenarios for the 1! 1& domain. Optimal routin for %P services is supported by the
.ll=%P &etwor" K<*L.
11% 6!e'i4ic%io' Re;uire5e's
11%.1Su(scri(er 6!e'i4ic%io'
%n 3GPP the identity of a subscriber is encoded in a identity module application which is contained on a 3%11 or on a
G!M !%M card. The 3%11 or G!M !%M card is a removable component of the 3ser 2?uipment. Three types of
identity modules are used in the 3GPP systemI
= 3niversal !ubscriber %dentity Module (3!%M)
= %M! !ubscriber %dentity Module (%!%M)
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3" Release 12
= !ubscriber %dentity Module (!%M) accordin to G!M
General re?uirementsI
= %n the 3GPP system each subscriber shall be uni?uely identifiable.
= The servin networ"s shall be able to authenticate any subscriber that roams onto their networ"
= %f a 32- that is reistered on the servin networ"- contains a G!M !%M card or a 3%11 containin a identity
module application- the servin networ" shall be able to identify the associated home P5M&.
&ote ,I 32 support of G!M !%M is optional.
&ote *I !ee the chapter (3!%M- 3%11 and Terminal) of the present specification for a reference- which G!M
phase !%Ms need to be supported by the networ".
11%.2 Ter5i'%" 6!e'i4ic%io'
%t is a re?uirement that the terminal can be uni?uely identified by the home environment and servin networ". This
shall re?uire a terminal identity scheme which uni?uely identifies each terminal- see 3GPP T! **.+,AK,*L.
11%.3<o5e E'viro'5e' 1 Servi'3 *e2or9 6!e'i4ic%io'
Bome E servin environments need to route communication to the current location of the user. This shall re?uire a
identity scheme which uni?uely identifies the servin environment and shall be used for routin purposes.
11%.4Servi'3 E'viro'5e' 1 Mo(i"e Viru%" *e2or9 6!e'i4ic%io'
. mobile virtual networ" operator (M@&O) is a service provider that does not have its own radio access networ"- but
resells wireless services- typically under their own brand name- usin the networ" of a host P5M& operator.
%t should be possible to uni?uely identify subscribers belonin to a particular M@&O.
12 <u5%' )%cors %'! user #roce!ures
The 3ser %nterface (MM%) from the end=userQs point of view should be as fle'ible as possible while still meetin the
eneral service re?uirements. %n addition it should be capable of bein updated so as to meet new services which are
still to be envisaed.
%n eneral the followin principles should be encompassedI
= activation of services should be as simple as possible with minimum input e'pected from the userJ
= feedbac"- to the user from the various services- should be meaninfulJ
= any error recovery procedures provided should be simple to understand and e'ecute.
= input from the user and information to the user should be provided in alternative selectable modes in order to
match user capabilities- preferences and situation.
Bowever- a detailed specification for the 3ser %nterface shall not be defined. %n particular iven the lobal nature of
the third eneration systems- for different reions of the world- different criteria will determine the implementation of
the 3ser %nterface. .lso it is unli"ely that there will be a sinle common handset which will meet all the service
re?uirements and therefore a common 3ser %nterface would be impractical.
Given the fle'ibility of the services- there should be a wide rane of 3ser %nterface possibilities. These possibilities
include simple terminals with a sinle onEoff button throuh to comple' terminals providin support to
hearinEvisually impaired users.
1ontrol of 1! 1& ;omain supplementary services (3GPP T! **.++< K>L)- may use MM% procedures specified in 3GPP
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 31 Release 12
T! **.+3+ KAL and e'istin MM% related 32 features (.nne' .) may also be used. %n particular the followin features
are hihly desirable for uniform 32 implementation where appropriateI
= Mappin of numeric "eys to 2uropean alphabetic "eys to ensure compatible mnemonic dialin as defined in
3GPP T! **.+3+ KAL-
= HWH "ey function to enable one "ey international access as defined in .nne' .
= !tructure of the MM% as described in 3GPP T! **.+3+ KAL
= Presentation of %M2% (%nternational Mobile 2?uipment %dentity) as defined in 3GPP T! **.+3+ KAL
13 U6++, US6M %'! Ter5i'%"
This clause defines the functional characteristics and re?uirements of the 3ser !ervice %dentity Module (3!%M) and
%!%M (%M !ervices %dentity Module). The 3!%ME%!%M are applications residin on a 3%11.
13.1 T$e US6M16S6M %'! User Pro4i"es
13.1.1 T$e US6M
2very 3!%M shall have a uni?ue identity and shall be associated with one and only one home environment.
%t shall be possible for a home environment to uni?uely identify a user by the 3!%M.
The 3!%M shall be used to provide security features.
7or access to services- provided by P! or 1! 1& domains- a valid 3!%M shall be re?uired. Optionally- !%M accordin
to G!M phase *- G!M phase *W- 3GPP release ::- 3GPP release < specifications may be supported.
The 3!%M shall be able to support !%M .pplication Tool"it as specified in 3GPP T! **.+39 K3L.
The 3!%M shall reside on a 3%11. 3!%M specific information shall be protected aainst unauthorised access or
alteration.
%t shall be possible to update 3!%M specific information via the air interface- in a secure manner.
.ccess to the %M! services shall be possible usin the 3!%M application in the event of no %!%M bein present on the
3%11. %f an %!%M is present on the 3%11 it shall be used to access the %M!.
%t shall be possible to store provisionin parameters on the 3!%M accordin to ;M specifications K38L.
%t should be possible to store provisionin parameters on the 3!%M accordin to 1P specifications K39L.
%t shall be possible for the networ" operator to confiure the 3!%M to indicate (throuh personalisation and OT.)
whether provisionin parameters accordin to ;M specifications or provisionin parameters accordin to 1P
specifications shall be used.
&oteI To avoid misoperation of the 32 in a mi'ed provisionin environment e.. durin a transition phase
when both 1P and ;M clients are present in the 32- the 1P parameters on the 3!%M can be read first.
%f ;Minformation is present (provisioned OT. in the 1P parameters.)- then use ;M- otherwise use 1P.
.nne' . describes a number of features that may optionally be supported by the 32 and thus 3!%M.
13.1.2 User Pro4i"es
%t shall be possible for a user to be associated with one or a number of user profiles- which the user can select and
activate on a per call basis. The user profile contains information which may be used to personalise services for the
user.
%t shall be possible for one or more user profiles associated with the same user to be active simultaneously so that the
user may ma"e or receive calls associated with different profiles simultaneously. .ctivation of profiles shall be done in
a secure manner- for e'ample with the use of a P%&.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 32 Release 12
7or terminatin calls the correct profile shall be indicated by the user address used (e.. M!%!;&- !%P 3/%)- each
profile will have at least one uni?ue user address associated with it. 7or oriinatin calls the user shall be able to
choose from the available profiles- the appropriate one for the call. . profile identity will need to be associated with
the call for accountin and billin purposes. 3ser profile identities need not be standardised but a standardised means
is re?uired for indicatin that a particular profile is bein used.
!imultaneous use of the same user profile on multiple terminals for the same type of service shall not be allowed.
3ser profiles associated with different home environments shall not share the same user address.
13.1.3 U6++ us%3e i' GER&* o'"8 Ter5i'%"s
%n /elease > and later- terminals supportin only G2/.& shall support 3!%M.
&oteI %t is stronly recommended that manufacturers implement !%M support on G2/.& only terminals until
the population of !%Ms in the mar"et is reduced to a low level.
13.1.4 Mu"i#"e US6Ms #er U6++
The standard shall support more than one 3!%M per 3%11 even when those 3!%Ms are associated with different home
environments. Only one of the 3!%Ms or the !%M shall be active at a iven time. Chile the 32 is in idle mode- it shall
be possible for the user to selectEreselect one 3!%M application amonst those available on the 3%11. .t switch on-
the 5ast .ctive 3!%M shall be automatically selected. The 5ast .ctive 3!%M shall be stored on the 3%11. 0y default
if there is no 5ast .ctive 3!%M defined in the 3%11- the user shall be able to select the active 3!%M amonst those
available on the 3%11.
The standard must not prevent the coexistence of USIM applications, each associated with different home
environments on the same UICC, so long as the security problems which arise from such a coexistence are solved.
13.1.5 T$e 6S6M
.ccess to the %M! services shall be possible usin an %!%M application.
The %!%M shall be sufficient for providin the necessary security features for the %M! and %M! only.
The %!%M shall reside on a 3%11. %!%M specific information shall be protected aainst unauthorised access or
alteration.
%t shall be possible to update %!%M specific information via the air interface- in a secure manner.
&oteI Chen accessin %M! over G2/.&E3T/.&E23T/.& or %=C5.& usin %!%M- a 3!%M needs also be
present to access the rest of the 3GPP system. .lternatively 3!%M could be used to access %M!.
13.2 T$e U6++
1haracteristics includin physical formats of a 3%11 are defined in T! 3,.,+,K3AL.
.ccess to services via 3GPP system with a sinle 3%11 shall be possible.
13.2.1 T$e U6++ %'! &##"ic%io's o$er $%' $e US6M or 6S6M
%t shall be possible for the 3%11 to host other applications in addition to the 3!%M or %!%M- see fiure 3. !ervice
providers- subscribers or users may need to establish additional data or processes on the 3%11. 2ach application on an
3%11 shall reside in its own domain (physical or loical). %t shall be possible to manae each application on the card
separately. The security and operation of an application in any domain shall not be compromised by an application
runnin in a different domain. .pplications may need to use their own security mechanisms which are separate to
those specified by 3GPP e.. electronic commerce applications.
2'amples of 3%11 applications areI 3!%M- %!%M- off=line user applications li"e 3PT- electronic ban"in- credit
service- etc.
.pplications should be able to share some information such as a common address boo".
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 33 Release 12
%t shall be possible to address applications- which reside on the 3%11- via the air interface.
%1=card
3!%M Other appl. 3!%M
!P * !P ,
+i,ure 3 ./ample of a 0ultifunction 1233
13.2.1% U6++ %##"ic%io's %'! 6MS
3%11 applications may ma"e use of %M! functionalities controlled by M2.
&oteI This is to allow a 3%11 application to interact with an .pplication !erver (.!) throuh %M!. 2'amples of
3%11 applications include identity manaement- ban"in applications- etc.
13.2.2 )%s &ccess %'! Reriev%" o4 7%% 4ro5 U6++
.n optional Hhih speedH interface may be provided between the 3%11 and the M2.
%f provided- this interface shall allow fast access and retrieval of data to support functionalities re?uirin lare
amounts of data to be transfered to and from the 3%11. 2'amples includeI
= on=card web servers
= rapid access to data stored on the 3%11- e.. phone boo"- P5M& lists or user data
. 3%11EM2 interface supportin this Hhih speedH interface shall be bac"ward compatible with the T! ,+* **,
interface specified in 3GPP T! 3,.,+, K3AL.
13.3 Ter5i'%"s %'! Mu"i#"e U6++s
. sinle terminal may support the use of multiple 3%11 (e. with applications li"e 3!%M andEor ban"in- credit
card-...). Only one 3%11 shall be active at a time to access a P5M&. %n case the active 3%11 contains more than one
3!%M- the re?uirements of ,3.,.< shall apply.
%f the 3%11 with the active 3!%M is removed from the mobile terminal durin a call (e'cept for emerency calls)- the
call shall be terminated immediately. %f the 3%11 with an active %!%M is removed durin an %M! session the %M!
session shall be terminated.
14 T8#es o4 4e%ures o4 UEs
3GPP specifications should support a wide variety of user e?uipment- i.e. settin any limitations on terminals should
be avoided as much as possible. 7or e'ample user e?uipment li"e hand=portable phones- personal diital assistants and
laptop computers can clearly be seen as li"ely terminals.
%n order not to limit the possible types of user e?uipment they are not standardised. The 32 types could be cateorised
by their service capabilities rather than by their physical characteristics. Typical e'amples are speech only 32-
narrowband data 32- wideband data 32- data and speech 32- etc..
%n order to enhance functionality split and modularity inside the user e?uipment the interfaces of 32 should be
identified. %nterfaces li"e 3%11=interface- P1M1%.=interface and other P1=interfaces- includin software interfaces-
should be covered by references to the applicable interface standards.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3$ Release 12
32s have to be capable of supportin a wide variety of teleservices- multimedia services and applications provided in
P5M& environment. 5imitations may e'ist on 32s capability to support all possible teleservices- multimedia services
and information types (speech- narrowband data- wideband data- video- etc.) and therefore functionality to indicate
capabilities of a 32 shall be specified.
The basic mandatory 32 re?uirements areI
= !upport for 3!%M. Optional support of G!M phase *- *W- 3GPP /elease :: and /elease < !%M cards K3<L.
Phase ,- >@ !%M cards shall not be supported. !upport for the !%ME%!%M is optional for the 32- however- if it
is supported- the mandatory re?uirements for !%ME%!%M shall be supported in the 32J
&ote ,I There is no /elease > specification for the !%M- and therefore references to H!%MH apply to earlier
releases.
&ote *I %t is stronly recommended that manufacturers implement !%M support on terminals supportin
G2/.& until the population of !%Ms in the mar"et is reduced to a low level.
= Bome environment and servin networ" reistration and dereistrationJ
= 5ocation updateJ
= Oriinatin or receivin a connection oriented or a connectionless serviceJ
= .n unalterable e?uipment identificationJ %M2%- see 3GPP T! **.+,A K,*LJ
= 0asic identification of the terminal capabilities related to services such asJ the support for software
downloadin- application e'ecution environmentEinterface- M2'2 terminal class- supported bearer services.
= Terminals capable for emerency calls shall support emerency call without a !%ME3!%ME%!%M.
= !upport for the e'ecution of alorithms re?uired for encryption- for 1! and P! services. !upport for non
encrypted mode is re?uiredJ
= !upport for the method of handlin automatic callin repeat attempt restrictions as specified in 3GPP T!
**.++, K<LJ
= .t least one capability type shall be standardised for mobile terminals supportin the G2/.&-3T/.& and 2=
3T/.& radio interfaces.
= 3nder emerency situations- it may be desirable for the operator to prevent 32 users from ma"in access
attempts (includin emerency call attempts) or respondin to paes in specified areas of a networ"- see 3GPP
T! **.+,, K,,LJ
= 1ipherin %ndicator for terminals with a suitable displayJ
= The cipherin indicator feature allows the 32 to detect that the 3GPP radio interface cipherin (user plane) is
not switched on and to indicate this to the user. The cipherin indicator feature may be disabled by the home
networ" operator settin data in the !%ME3!%M. The default terminal behaviour shall be to ta"e into account
the operator settin data in the !%ME3!%M. Bowever- terminals with a user interface that can allow it- shall
offer the possibility for the user to confiure the terminal to inore the operator settin data in the !%ME3!%M.
%f this feature is not disabled by the !%ME3!%M or if the terminal has been confiured to inore the operator
settin data in the !%ME3!%M- then whenever a user plane connection is in place- which is- or becomes un=
enciphered- an indication shall be iven to the user. %n addition- if this feature is not disabled by the !%ME3!%M
or if the terminal has been confiured to inore the operator settin data in the !%ME3!%M- then additional
information may also be provided about the status of the cipherin. 1ipherin itself is unaffected by this
feature- and the user can choose how to proceedJ
= !upport for P5M& selection.
= !upport for handlin of interactions between tool"its concernin the access to 32 MM% inputEoutput
capabilitiesJ
= Chenever an application (e.. a !.TEM2'2EC.P application) re?uires the access to the 32 MM% inputEoutput
capabilities (e.. display- "eyboard-S )- the 32 shall rant this access subject to the capabilities of the 32. This
shall not cause the termination of any other applications (e.. C.P browser or M2'2E!.T application) which
were previously usin these 32 resources. The 32 shall ive the user the ability to accept or reject the new
application. %n the case that the application re?uest is rejected- the access to the 32 MM% inputEoutput
capabilities is returned to the applications which were previously usin these 32 resources. %f the user decides
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3& Release 12
to continue with the new application- then when this new application is terminated- the access to the 32 MM%
inputEoutput capabilities shall be returned to the 32 to be re=allocated to applications (e.. the precedin
application which was interrupted). !ubject to the capabilities of the 32- the user shall have the ability to
switch the MM% inputEoutput capabilities between applications.
&oteI /ejectin a re?uest to access the 32 MM% inputEoutput capabilities by an application does not
necessarily mean that it is terminated- but only that the access to the 32 MM% inputEoutput capabilities
are not ranted to this application. Bandlin of rejection (termination- put on hold-S) is the
responsibility of the application.
.nne' . describes a number of features which may optionally be supported by the 32.
15 Re"%io's$i# (e2ee' su(scri#io' %'! service
!e"iver8
15.1 Su(scri#io'
. subscription describes the commercial relationship between the subscriber and the service provider.
)ubscriber
)ubscription 3 )ubscription & )ubscription 4
) 0 Domain )ervices
)ervice B
)ervice )ervice 5 )ervice D
)ervice A
() 0 Domain
)ervices
+- 0 )ubs#stem )ervices
)ervice B6
)ervice D6
)ervice 6
)ervice A6
)ervice 7
)ubscription n
8i"ure 4: )ubscriber9 subscription and services relations!ip
. subscription to a networ" operator may provide the user with access to one or more domains. . !ubscription shall
identify the set of services- within particular domains- to which the user has access (see fiure 3)J each subscription
may specify a different set of services. These services may be provided by the 1! 1& ;omain andEor a P! 1& ;omain
andEor an %M 1& subsystem. !ubscriptions relate to services such as 0asic !ervices (e.. Teleservices- 0earer
services)- P! services and %M=!ervices (%P=based multimedia services)- which are typically provided by networ"
operators- and to value added services which typically are provided by networ" operators andEor other entities that
provide services to a subscriber
The subscription identifiesI
= the services and related services information that are made available to the subscriber by the service provider J
%n addition a subscription to a networ" operator may identifyI
= the domains to which the user has been ranted access by the networ" operator. %n particular- the P! service
profile and information on the allowed Do! parameter ranes shall be contained in the subscription.
= the identity of the subscriber within these domains.
&oteI The identity of a subscriber in the 1! 1& domain and P! 1& domain (e.. her %M!%) may potentially be
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3' Release 12
different to her identity in the %M 1& subsystem
= the radio access systems over which the subscriber may access their services e.. 3T/.&- G2/.&- 23T/.&-
%=C5.&.
15.2 :$er co'ce#s %ssoci%e! 2i$ services
(rovision of services:
.n action to ma"e a service available to a subscriber. The provision may beI
= eneralI where the service is made available to all subscribers (subject to compatibility restrictions
enforced) without prior arranements bein made with the service providerJ
= pre=arranedI where the service is made available to an individual subscriber only after the necessary
arranements have been made with the service provider.
:it!dra;al:
.n action ta"en by the service provider to remove an available service from a subscriber#s access. The withdrawal may
beI
= eneralI where the service is removed from all subscribers provided with the serviceJ
= specificI where the service is removed on an individual basis from subscribers provided with the
service.
&oteI .ccess to the %M subsystem re?uires %P connectivity provided- for e'ample- throuh provision of the P!
1& domain.
15.3 Re;uire5e's co'cer'i'3 service !e"iver8
%n eneral it is a re?uirement to allow the use of independent services simultaneously (i.e. 0asic- P!- %P multimedia
and operator specific).
,. The networ" usae shall be based on the services identified within the subscription- the terminal capabilities and-
where applicable- roamin areements between operators.
*. The Bome environment shall be able to decide on the service delivery in a roamin scenario. %.e. it shall control
how services are delivered in line with the subscription.
3. %f an offered or re?uired service (e.. voice) could be provided with different technoloies within the servin
networ"- the decision on service delivery shall be based on preferences identified in the user profile and servin
networ" capabilities and conditions (e.. load).
<. %f the user profile does not allow an alternative service delivery method and the re?uested delivery method is not
available in the servin networ" the service shall not be provided to the subscriber. This applies also to data
bearer services with defined Do! parameters (or parameter ranes).
2'amplesI
= . terminatin voice call for a subscriber with a dualEmulti mode terminal (e..3T/.&EG2/.&) could be
delivered in a hybrid networ" as %M service or 1! voice call (T!,,). The delivery decision is based on the
preferences of service delivery within the user profile and the networ" conditions. %f there is no preference
information of the Bome environment available the decision is made only on the networ" conditions from the
servin networ".
= . terminatin data service (e.. P! with Do! for real time audio) where the networ" cannot provide the Do! at
call setup. 0oth the oriinatin and terminatin application shall be informed about the possible Do!
confiuration for that call. The further handlin (setup continuation- termination) depends on the decisions of
the applications.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3( Release 12
15.3.1 Mo(i"e :ri3i'%e! Voice c%""s
Chen a M2 capable of offerin voice service both on 1! and %M! is 1! attached and %M! reistered MO 1! @oice
calls (T!,,) and MO %M! voice services shall be oriinated on the domain specified by the Bome operator policy or
users preferences. The Bome Operator policy shall have precedence to user preferences.
15.3.2 Mo(i"e Ter5i'%e! Voice c%""s
Chen a M2 capable of offerin voice service both on 1! and %M!- MT 1! @oice calls (T!,,) and MT %M! voice
services shall be delivered over the domain specified by the Bome operator policy or users preferences. The Bome
Operator policy shall have precedence to user preferences. %f the call delivery attempt fails in one domain- if specified
by operator policy- it should be possible to attempt the delivery in the other domain or the callEcommunication
forwardin supplementary services K<,- <+L may be invo"ed if provisioned.
&oteI The delivery decision will ta"e into account aspects such as %M! reistration and 1! attachment status.
16 +$%r3i'3 #ri'ci#"es
The cost of the call may cover the cost of sendin- transportin- delivery and storae. The cost of call related
sinallin may also be included. Provision shall be made for charin based on time- destination- location- volume-
bandwidth- access technoloy and ?uality. 1hares may also be levied as a result of the use of value added services.
%t shall be possible for information relatin to chareable events to be made available to the home environment at short
notice. The re?uirements shall includeI
= %mmediately after a chareable event is completedJ
= .t reular intervals of time- volume or chare durin a chareable event.
= ;elivery of the location of the terminal to the home environment- e.. cell identificationJ
!tandardised mechanisms of transferrin charin information are re?uired to ma"e these re?uirements possible.
%t should be possible for multiple le calls (e.. forwarded- conference or roamed) to be chared to each party as if
each le was separately initiated. Bowever- in certain types of call- the oriinatin party may wishEbe oblied to pay
for other les (e.. !M! MO may also pay for the MT le.).
%t shall be possible to chare accordin to the location (e.. cell- or (one) and access technoloy that are bein used to
access networ" services.
Provision shall be made for the chareable party to be chaned durin the life of the call. There shall be a fle'ible
billin mechanism which may include the use of stored value cards- credit cards or similar devices.
The chareable party (normally the callin party) shall be provided with an indication of the chares to be levied (e..
via the called number automatically or the .dvice of 1hare supplementary service) for the duration of the call (even
thouh the user may chane service environment)The user shall be able to ma"e decisions about the acceptable level
of accumulated chare dynamically or throuh their service profile.
%f a user is to be chared for acceptin a call then their consent should be obtained. This may be done dynamically or
throuh their service profile.
1harin and accountin solutions shall support the shared networ" architecture so that end users can be
appropriately chared for their usae of the shared networ"- and networ" sharin partners can be allocated their share
of the costs of the shared networ" resources.
10 Ro%5i'3
10.1 &ssu5#io's
%n order to roam- the followin appliesI
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3) Release 12
- Mobile terminal can connect to the radio access networ".
- .uthentication (charinEbillin networ") must occur in order to et access to services (e'cept for emerency
calls).
- The services offered to a roamin subscriber may be restricted by the capabilities of the visited networ"- and the
roamin areement between the visited and the home environment.
10.2 Pri'ci#"e
5on term evolution of the %M 1& subsystem shall not be restricted by the shortEmid term inter=domain roamin
re?uirements.
10.3 Re;uire5e's
1! visited
%M 1& subsystem
visited
Bome 2nvironment
1! profile
data
P! profile
data
%M 1&
profile data
@isited &etwor"s
P! visited
+i,ure &- Roamin, re4uirements
= The personalised services F capabilities available in a visited networ" are dependent upon the subscription
options in the home environment. This does not preclude the visited networ" offerin additional services- or
access to content providers.
= /oamin from this release#s home environment to 1! (this release or earlier) visited networ" is re?uired
= /oamin from this release#s home environment to %M 1& subsystem visited networ" is re?uired
= /oamin from this release#s home environment to P! (this release or earlier) visited networ" is re?uired
= /oamin from previous releases# home environment (or earlier) to this release 1! visited networ" is re?uired
= /oamin from previous releases# home environment (or earlier) to this release P! visited networ" is re?uired
&oteI Chen an operator allows a subscriber to roam to different domains- the home environment needs to
provide subscription data to the visited networ" . The mappin between service data of the different
domains is not standardisedJ it is determined by the home environment and may be influenced by
roamin areements.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 3* Release 12
1= <%'!over Re;uire5e's
.ny handover re?uired to maintain an active service while a user is mobile within the coverae area of a iven
networ"- shall be seamless from the userQs perspective. Bowever handovers that occur between different radio
environments may result in a chane of the ?uality of service e'perienced by the user.
%t shall be possible for users to be handed over between different networ"s subject to appropriate roaminEcommercial
areements.
7or further information see 3GPP T! **.,*: K:L.
1. *e2or9 Se"ecio'
&etwor" selection procedures are defined in 3GPP T! **.+,, K,,L.
Other procedures may be offered by the 32.
20 Securi8
!ecurity matters are considered in 3GPP T! *,.,33 K,>L and 3GPP T! 33.,*+ K,AL.
21 Voice +%"" +o'i'ui8
21.1 Ge'er%"
The 3GPP system shall be able to provide continuity between 1! voice services (Teleservice ,,K,<L) and the full
duple' speech component of %M! multimedia telephony service K<+L with no neative impact upon the userQs
e'perience of the voice service. This functionality is "nown as voice call continuity. @oice call continuity shall be
e'ecuted when continuation of a voice service is re?uired based on operator policy across a chane in the connection
of the 32 to the 3GPP system as the user moves from usin the 1! domain to usin %M! and vice versa.
The user e'perience shall be unaffected by the transition from a 1! voice service to a full duple' speech component of
%M! multimedia telephony and vice versa- and the user shall e'perience no disruption in the voice service provided.
The voice service is continued with the same M2.
%t shall be possible to support @oice call continuity between %M! and the 1! domain belonin to different operatorsJ
i.e.- when the userQs %M! services are under the control of the home %M! and the user is roamin in the coverae of
the visited 1! networ".
%t shall be possible for an operator to enable or disable @oice call continuity for a iven subscriber e.. based on
roamin conditions- terminal capabilities.
21.2 Su##or o4 Su##"e5e'%r8 Services
The voice call continuity userQs e'perience shall be such that- to the reatest deree possible- a consistency of service
is provided reardless of the underlyin communication infrastructure and technoloy. Cith reard to supplementary
services- the eneral principle is that 1!=based supplementary services only apply whilst a @11 subscriber is in the
1! domain and e?uivalent services over %M! only apply whilst a @11 subscriber is in the %M! domain- althouh
there are e'ceptions listed below. %t is not re?uired to synchronise the supplementary service settins of the 1! domain
with the related service settins of the %M! (e.. different forwardin numbers may apply over 1! and over %M!).
The followin supplementary services apply. The impact on the supplementary services in case the @11 is e'ecuted
for the callin party- the called party- or both is described below.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $" Release 12
21.2.1 Li'e 6!e'i4ic%io' Services
. user who has subscribed to the 15%P !upplementary !ervice and receives a call shall also receive the line identity or
appropriate %M! information of the callin party.
The identity presentation is not chaned for the duration of the call reardless of whether the call underoes @11.
%f the 15%/ !upplementary !ervice or %M! identity restriction is applicable to the call- then at call setup time the
called user shall receive an indication that the identity is not available because of restriction.
The indication is not chaned for the duration of the call reardless of whether the call underoes @11.
%f 1O5P or a correspondin %M! service is applicable to a call the callin subscriber shall receive the connected line
identity or appropriate %M! information at call setup time.
The identity presentation is not chaned for the duration of the call reardless of whether the call underoes @11.
%f the 1O5/ !upplementary !ervice or %M! identity restriction is applicable to the call- then the callin user shall
receive an indication at call setup time that the identity of the connected party is not available because of restriction.
The indication is not chaned for the duration of the call reardless of whether the call underoes @11.
21.2.2 &"" +%"" )or2%r!i'3s
%t shall be possible to perform @11 on a call which was forwarded due to call forwardin supplementary services in
the 1! or redirectin services in the %M!.
21.2.3 +%"" ?%ii'3
The functionality of call waitin supplementary service in the 1! domain shall not be affected by the userQs ability to
undero @11.
&oteI Chether the user will continue to receive call waitin notifications in the case their call is continued in
the %M! will depend on whether a call waitin service is available in the %M!.
21.2.4 +%"" <o"!
%t shall be possible to re=establish a call which has been put on hold before underoin @11- after the @11 has been
performed.
21.2.5 Mu"i#%r8
%t shall be possible for any party in a multiparty call to undero @11 and to stay in the call. %t shall be possible to
terminate the entire multiparty call when the served mobile subscriber releases even if she is connected via the %M!
after underoin @11.
21.2.6 &"" +%"" >%rri'3s
%f a call were to undero @11 and that would result in the call bein barred in the taret domainEsystem- it shall be up
to the home operator policy whether the call continues in the taret domainEsystem- the call terminates- or @11 is not
e'ecuted for the call.
21.2.0 Voi!
21.2.= Voi!
21.2.. &"" o$er Su##"e5e'%r8 Services
Other supplementary services are not discussed in this section as they do not apply to calls in proress (i.e. they apply
to call set up only) or their support andEor the need for standardised implementation has not been identified as critical
for @11 in this /elease.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $1 Release 12
21.3 Cu%"i8 o4 Service
@oice call continuity shall not adversely impact the ?uality of the voice service e'perienced by the user.
21.4 Securi8
@oice call continuity shall not adversely impact the security of the 3GPP system.
!ecurity mechanisms of the 3GPP system shall be reused for voice call continuity.
21.5 E5er3e'c8 c%""s
@oice call continuity for emerency calls shall be applicable to dual radio and sinle radio 32s.
@oice call continuity of emerency calls shall only be performed when all the followin conditions are metI
= the source networ" is %M!J
= the taret networ" supports emerency callsJ
= the user is movin out of coveraeJ
= the source and taret networ" belon to the same operatorJ
= the taret networ" supports voice call continuity.
21.6 +$%r3i'3
%t shall be possible to indicate in the charin information that a @11 event has occurred (e..- so that appropriate
ratins can be applied for the 1! and %M! parts of the continued voice call).
21.0 V++ &civ%io'
%t shall be possible to activate @11 based on operator policies- ta"in into account any of the followinI
= /adio conditions e.. radio ?uality thresholds and related hysteresis
= 1overae availability e.I .lways prefer %=C5.&- if certain !!%; are available
22 6MS +e'r%"iDe! Services
22.1 Ge'er%"
The %1! user shall receive both reistered and unreistered services in a consistent manner when the user accesses
%M! either via the 1! or the P! domain (both of which can be supported by 3GPP access networ"s or non=3GPP
access networ"s). !upport of 32s enhanced with %1! capability as well as 32s without %1! capability shall be
possible.
&oteI The impacts to support non=3GPP 1! domains to support of %1! are outside the scope of 3GPP.
22.2 Service +o'sise'c8
!ubscribers shall have a consistent user e'perience reardless of the domain used- subject to the constraints of the 32
and access networ".
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $2 Release 12
22.3 Service +o'i'ui8
%1! shall support service continuity between 1! and P! domains (both of which can be supported by 3GPP access
networ"s or non=3GPP access networ"s)- subject to the constraints of the 32 and access networ"s.
&ote I The impacts to support non 3GPP 1! domains are outside the scope of 3GPP.
The service continuity shall includeI
= 0asic services
= &on mid=call services
= Mid=call services
The support of service continuity for fa' and data (1!) media components is not re?uired.
22.4 6MS Services
The set of %M! services supported by %1! shall include at least the followin- subject to the constraints of the 32 and
access networ"sI
= %M! Multimedia Telephony services- includinI
= speech-
= video-
= fa'-
= data (1!)-
= !upplementary services defined within K<+LJ and
= Multimedia priority service.
&oteI Other %M! hosted services supported by an operator or 3rd party may be supported.
%1! shall not limit the %1! userQs capability to ma"e emerency calls
22.5 Ro%5i'3 Su##or
.n %1! user shall be able to receive full %1! support from the BP5M& while roamin in the @P5M&- subject to the
constraints of the @P5M& (e.. roamin areements- operator policies).
The Bome operator shall be able to control if the 32 enhanced with %1! capability shall act without %1! capability
while roamin.
23 +S 6P i'erco''ecio' re;uire5e's
23.1 6'ro!ucio'
1! %P interconnect represents the interconnection of M!1 !erver functionality between * 1! networ"s over an
underlyin %P infrastructure.
23.2 6P i'erco''ec
The %P connection used for 1! %P interconnect shall be eneric such that it can support all combinations of core
networ" interconnection. 2.. the %P interconnection shall be shared between the %M! interconnection and the 1! %P
interconnection.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $3 Release 12
%t shall be possible to handle the inter=connection of all services over this eneric %P interface. The handlin of
security and charin shall also be eneric for all %P interconnect scenarios.
23.3 MS+ server i'erco''ec
The followin re?uirements apply at the interconnection point when two P5M&s are interconnected by means of %P
transport technoloy for *G and 3G 1! services.
The system shall support the capability for 1! service interoperability and interwor"in.
%t shall be possible to apply operator defined policy at the interconnection point.
The system shall support the capability to control the session resources when two different networ" domains are
connected that may have- for e'ample- different %P addressin schemes.
The system shall support %P inter=connection between core networ"s either by direct connection or by usin an
intermediate carrier (e.. G!M. %PG K<3L).
The system shall support both bilateral interconnection between two carriers and multilateral interconnection (e.
G!M. %PG K<3L) by means of intermediate carrier.
The system shall support either
= transparent relay of the %P sinallin and trafficJ
= service aware interconnection
The system shall support codec neotiation across one or multiple interconnects to minimise transcodin (and
preferably eliminate it) to provide the hihest ?uality service to the user.
24 Service &"i3'5e' E Mi3r%io'
24.1 6'ro!ucio'
!ervices can be offered to the users via different service domains- e.. certain teleservices and supplementary services
via 1! or Multimedia Telephony and supplementary services via %M!. 2specially for the supplementary services iven
below a stron relationship e'ists from the user#s point of view. Therefore means shall be provided to enable a
consistent user e'perience when chanin from one service domain to the other.
The re?uirements in this clause are applicable durin the miration to an %1!. The ability to synchronise the service
settins will facilitate the miration from a 1! to an %M! based networ" and will allow networ" operators ma'imum
fle'ibility in their miration strateies.
24.2 &"i3'5e' o4 su##"e5e'%r8 services sei'3s
0ased on user preferences and if provisioned by the home operator the networ" shall automatically synchronise the
parameter settins of the supplementary services listed in the followin tableI
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $$ Release 12
3S #oice (TS11
Supplementary Services
.4uivalent 0ultimedia
Telephony Services in
20S domain
Service 5ehaviour Re4uired
+L6P1+L6R :6P1:6R +o'sise'c8 o4 #rese'%io'
+oLP1+oLR T6P1T6R +o'sise'c8 o4 #rese'%io'
+*&P :6P1:6R +o'sise'c8 o4 #rese'%io'
+%"" )or2%r!i'3 +76V +%"" 4or2%r!i'31+76V s$%"" 2or9 co'sise'"8 'o 5%er
2$ic$ !o5%i' $e user is i'. T$e sei'3s (e.3. 4or2%r!i'3
'u5(ers) s$%"" re5%i' $e s%5e %cross !o5%i's 4or %""
$e #%rs o4 $e service 4or 2$ic$ $ere is %' e;uiv%"e'.
+%"" ?%ii'3 +o55u'ic%io' ?%ii'3 T$e (us8 s%e o4 $e user s$%"" (e %v%i"%("e o (o$
!o5%i's so $% $is c%' (e %##"ie! 'o 5%er 4ro5 2$ic$
!o5%i' %' i'co5i'3 c%""1co55u'ic%io' ori3i'%es. T$e
%civ%io' s%us o4 +%"" ?%ii'3 %'! +o55u'ic%io'
?%ii'3 s$%"" (e s8'c$ro'ise!.
+%"" <o"! +o55u'ic%io' <:L7 &'8 c%""s $e"! i' o'e !o5%i' s$%"" re5%i' $e"! o' 5ovi'3
o % !i44ere' !o5%i'. 6 s$%"" (e #ossi("e o re-es%("is$ %
c%"" $% 2%s #u o' $o"! i' %'o$er !o5%i'.
Mu"i#%r8 +:*) &'8 co'4ere'ce (5u"i#%r8) c%""s se u# i' o'e !o5%i'
s$%"" re5%i' i' 4orce i4 %'8 user 5oves o %'o$er
!o5%i'.
+"ose! User Grou# +"ose! User Grou# +o'sise'c8 re;uire! %cross !o5%i's
++>S ++>S +o'sise'c8 re;uire! %cross !o5%i's
+%"" 7e4"ecio' 7e4i'e! i' +76V +o'sise'c8 re;uire! %cross !o5%i's
E/#"ici +%"" Tr%'s4er E+o55T +o'sise'c8 re;uire! %cross !o5%i's. T$e UE s%e (i.e.
i4 (us8 or 'o) s$%"" (e %v%i"%("e i' (o$ !o5%i's o
e'sure $% $is c%' (e %##"ie! co'sise'"8.
+%"" >%rri'3 +o55u'ic%io' >%rri'3 +%""1 +o55u'ic%io' >%rri'3 s$%"" 2or9 co'sise'"8 'o
5%er 2$ic$ !o5%i' $e user is i'. T$e sei'3s (i.e.
(%rre! 'u5(ers) s$%"" re5%i' $e s%5e %cross !o5%i's.
&o+ &o+ +o'sise' su##or %cross !o5%i's. 64 $e user 5oves
4ro5 o'e !o5%i' o $e o$er !uri'3 $e co55u'ic%io',
$e &o+ s$%"" i'!ic%e $e correc c$%r3e 4or $e o%"
!ur%io' o4 $e co55u'ic%io'.
The operator shall be able to provision the user with the possibility to define which of the above settins shall be
synchronised automatically and which settins can e'ist independently of each other. 2.. a user miht decide that the
activation status of 15%PEO%P- 15%/EO%/- 1all CaitinE1ommunication Caitin etc. is synchronised but that the call
forwardin status and forwarded=to=number is different from the communication diversion settins and the diverted=
to=party address.
%f the synchronisation of supplementary services- which use the 32#s busy state for invocation- is activated the busy
state of the 32 shall be available in both domains.
&oteI The Huser not reachableH or Huser not loed inH conditions in the different domains are independent of
each other. This means- e.. not bein reistered in the %M! does not affect the invocation of 17&/c in
the 1! domain.
!ynchronisation of settins means that the most recent chanes which have been applied in one domain are
propaated to the other domain.
There are certain circumstances under which the synchronisation will fail e.. when a user inserts a !%P 3/% as
diverted=to=party address in the %M! domain which has no Tel 3/% associated with it. %n such a case there is no valid
settin for the 1! domain for this particular parameter and therefore the 1! domain service settin shall remain
unchaned. The user may receive a notification about the failure of the synchronisation procedure and its cause.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $& Release 12
25 S8se5 o#i5is%io' 4or co55u'ic%io' 2i$ s#eci4ic
c$%r%cerisics
25.1 Voi!
25.2 *u5(eri'3 Resource E44icie'c8
The followin optional re?uirement is intended to provide better numberin resource efficiency for 32s that only
re?uire pac"et switched services.
= . networ" operator shall be able to provide P! only subscriptions with or without assinin an M!%!;&.
= /emote trierin shall be supported with or without assinin an M!%!;&.
= /emote 32 confiuration shall be supported without the use of an M!%!;&.
&ote ,I 1urrent remote 32 confiuration solutions (i.e. ;evice Manaement and Over=the=.ir confiuration)
are mainly based on !M!- which assumes the use of M!%!;&s.
&ote *I The re?uirements in this sub=clause apply to server=to=32 communication scenarios only.
25.3 *e2or9 #rovi!e! !esi'%io' 4or u#"i'9 !%%
The &etwor" Provided ;estination for 3plin" ;ata feature is intended for use when all data from a 32 is to be
directed to a networ" provided destination address.
= 7or uplin" data communication- the networ" shall be able to direct all uplin" P! data traffic to a networ"
provided destination address.
&oteI This feature may be used- for e'ample- when all data from an electricity meter is sent to a server maintained
by the networ" operator.
25.4 PS o'"8 su(scri#io's
The system shall support subscriptions that only allow pac"et based services and !M!.
26 Si'3"e Si3'-:' (SS:) Service
26.1 Re;uire5e's
26.1.1 Re;uire5e's 4or $e UE
.n !!O=capable 32 shall support 3GPP !!O .uthentication- without user intervention- based on Operator=controlled
credentials.
.n !!O=capable 32 shall be able to initiate the !!O !ervice reardless of the access networ" technoloies supported
by the 32.
.n !!O=capable 32 that supports 3GPP access and non=3GPP access shall support transparency of the !!O !ervice
from a user perspective durin transitions between 3GPP access and non=3GPP access- whether or not the transition
occurs durin a data application session.
.n !!O=capable 32 may support a re?uest for !!O 5ocal 3ser .uthentication from a ;ata .pplication Provider or an
%dentity Provider to confirm the presence of the reistered user of the data application.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $' Release 12
26.1.2 Re;uire5e's 4or % 3GPP SS: Service
The 3GPP !!O !ervice shall provide secure- seamless and transparent access to data applications for users of the !!O
!ervice independent of the access networ" technoloy.
The 3GPP !!O !ervice shall be able to interwor" with %dentity Manaement (%dM) specifications (e..- Open%; K>,L).
The 3GPP !!O !ervice shall support 3GPP !!O .uthentication based on Operator=controlled credentials and policies.
The 3GPP !!O !ervice may support neotiation and use of an areed authentication method between the 32 and the
3GPP !!O %dentity Provider. The neotiation of an authentication method may be repeated each time the user accesses
a ;.PQs service.
The 3GPP !!O !ervice may support mechanisms to ensure the presence of the reistered user of the data application
to satisfy policies of the ;ata .pplication Provider.
The 3GPP !!O !ervice shall be transparent from a user perspective when transitions occur between 3GPP access and
non=3GPP access- whether or not the transition occurs durin a data application session.
The 3GPP !!O !ervice shall be transparent from a user perspective when the user accesses a data application usin an
identity created throuh a 3rd Party !!O %dentity Provider. The user shall be able to confiure which 3rd party !!O
identities are used with the 3GPP !!O !ervice.
20 User #"%'e co'3esio' 5%'%3e5e'
20.1 6'ro!ucio'
/.& user plane conestion- in the conte't of this clause- is considered to be conestion that affects the user plane-
which may last for a few seconds- a few minutes- or a few hours due to arrival of new active users- increase of
communication intensity of e'istin users- the radio environment chanin- the mobile user chanin location- and
other reasons- thus causin the capacity of /.& resources to transfer user data to be e'ceeded. . short=duration burst
of user plane traffic should not be identified as /.& conestion.
20.2 Ge'er%"
a) The networ" shall be able to detect /.& user plane conestion onset and abatement. Mechanisms to cope with
/.& user plane conestions should be resilient to rapid chanes in the level of conestion.
b) The networ" shall be able to identify whether or not an active 32 is in a /.& user plane conested cell.
c) The networ" operator shall be able to confiure or provision and enforce policy rules to best deal with /.&
user plane conestion.
d) The system should react in a timely manner to manae a /.& user plane conestion situation- i.e. that the
measures ta"en become effective to promptly help resolve the /.& user plane conestion.
e) The sinallin overhead caused by /.& user plane conestion manaement solutions in the system shall be
minimi(ed.
f) The networ" shall be able to ta"e into consideration the /.& user plane conestion status and the subscriber#s
profile when copin with traffic conestion.
20.3 PrioriiDi'3 r%44ic
a) The networ" shall be able to identify- differentiate and prioriti(e traffic from different applications in order to
provide these applications with appropriate service ?uality based on /.& user plane conestion status- ta"in
user related information and content type into account.
&ote ,I The applications may include social networ"in- OTT video- bloin- internet ames- 7TP- software
patches and updates- non real time services- etc.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $( Release 12
b) .ccordin to operator policy- durin /.& user plane conestion the operator shall be able to select the
communications which re?uire preferential treatment and allocate sufficient resources for such communications
in order to provide these services with appropriate service ?uality.
c) .ccordin to operator policy- the networ" shall be able to select specific users (e.. heavy users- roamin users-
etc.) and adjust the Do! of e'istin connectionsEflows and apply relevant policies to new connectionsEflows
dependin on the /.& user plane conestion status and the subscriber#s profile.
&ote *I Preferably- connectionsEflows need to be adjusted such that the user e'perience is not neatively affected.
20.4 Re!uci'3 r%44ic
a) 0ased on /.& conestion status and accordin to operator policy- the networ" shall be able to reduce the user
plane traffic load (e.. by compressin imaes or by adaptation for streamin applications) ta"in into account
32 related information (e.. 32 capabilities- subscription).
b) The system shall be able to adjust the communication media parameters of real=time communications so that
they consume less bandwidth.
c) The system shall be able to distinuish between different media involved in the communication (e.. media for
voice and media for video portions) and in case of /.& user plane conestion (re=)neotiate each media
separately to consume less bandwidth.
d) .ccordin to operator policy- the networ" shall be able to select specific applications and control the data rate
of the identified applications based on /.& user plane conestion status- at the same time ta"in into
consideration user related information (e.. a HplatinumH subscription user should have ood e'perience even if
e'periencin conestion) and content type (e..- te't vs. imae).
e) .ny use of application identification should consider the impact on Multi=Operator 1ore &etwor" (MO1&)
partner(s) ainin information on the use of the networ" by the other MO1& partner(s).
20.5 Li5ii'3 r%44ic
a) The networ" shall be able to limit traffic from operator=controlled andEor third=party services based on /.&
user plane conestion status for a 32- e.. to defer Push services based on the /.& conestion status and
operator policy.
b) The system shall be able to apply different handlin (e.. be able to prohibit or delay) all or a particular
selection of %P bearer service re?uests dependin on whether a service re?uest is for 3nattended ;ata Traffic or
.ttended ;ata Traffic.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $) Release 12
&''e/ & ('or5%ive),
7escri#io' o4 o#io'%" user e;ui#5e' 4e%ures
&.1 7is#"%8 o4 c%""e! 'u5(er
This feature enables the caller to chec" before call setup whether the selected number is correct.
&.2 6'!ic%io' o4 c%"" #ro3ress si3'%"s
%ndications shall be iven such as tones- recorded messaes or visual display based on sinallin information returned
from the P5M&. On data calls- this information may be sinalled to the ;T2.
1all proress indicators are described in 3GPP T! **.++, K<L.
&.3 +ou'r81PLM* i'!ic%io'
The countryEP5M& indicator shows in which P5M& the 32 is currently reistered. This indicator is necessary so that
the user "nows when HroaminH is ta"in place and that the choice of P5M& is correct. 0oth the country and P5M&
will be indicated. Chen more than one visited P5M& is available in a iven area such information will be indicated.
The P5M& name is eitherI
= !tored in the M2 and associated with the M11WM&1 combination received on the broadcast channelJ
= &%TM (see **.+<* K,8L) (in which case it overrides the name stored in the 32)J
= stored in the 3!%M in te't and Eor raphic format and associated with the M11WM&1 combination- and
optionally the 5.%- received on the broadcast channel (in which case it overrides the name stored in the 32 and
R if present R the &%TM name).
%t shall be possible to store on the 3!%M at least ,+ P5M& %dentifications (M11WM&1 combination and optionally
the 5.%) for which the same P5M& name shall be displayed.
The P5M& name stored in the 3!%M has the hihest priority- followed by the P5M& name provided by &%TM. The
P5M& name stored in the M2 has the lowest priority.
%f the P5M& name stored in the 3!%M is not available in te't format and the 32 is unable to display the raphic
format- the P5M& name provided by &%TM has the hihest priority- the P5M& name stored in the M2 has the ne't
priority.
&.4 Service Provi!er *%5e i'!ic%io'
The service provider name is stored in the 3!%M in te't andEor optionally raphic format. %t shall be possible to
associate at least ,+ P5M& %dentifications (M11WM&1 combination) with the same !P &ame.
Chen reistered on the BP5M&- or one of the P5M& %dentifications used for !ervice Provider &ame displayI
(i) The !P &ame shall be displayedJ
(ii) ;isplay of the P5M& &ame is an operatorQs option by settin the appropriate fields in the 3!%M (i.e. the
!ervice Provider name shall be displayed either in parallel to the P5M& &ame or instead of the P5M& &ame).
Chen reistered on neither the BP5M&- nor one of the P5M& %dentifications used for !ervice Provider &ame displayI
(i) The P5M& name shall be displayedJ
(ii) ;isplay of the !P &ame is an operatorQs option by settin the appropriate fields in the 3!%M.
%f the 32 is unable to display the full name of the !ervice Provider the name is cut from the tail end. The storae of
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 $* Release 12
!ervice Provider name and options- and choice of options- shall be under control of the networ" operator.
&.4% +ore *e2or9 :#er%or *%5e i'!ic%io'
%t shall be possible for the 32 to display the name of the core networ" operator the user has selected.
&.5 Fe8#%!
. physical means of enterin numbers- enerally- thouh not necessarily- in accordance with the layout shown in
fiure ..,.
!ee also 3GPP T! **.+3+ KAL (Man=Machine %nterface).
.dditional "eys may provide the means to control the 32 (e.. to initiate and terminate calls).
1 2 3
$ & '
( ) *
6 " 7
+i,ure A!1
&.6 S$or 5ess%3e i'!ic%io' %'! %c9'o2"e!3e5e'
This feature allows the delivery of short messaes to a 32 from a service centre. !uch messaes are submitted to the
service centre by a telecommunications networ" user who can also re?uest information of the status of the messae by
further interroation of the service centre. The service centre then transmits the messae to an active 32 user.
The 32 must therefore provide an indication to the user that a messae has been received from the service centre and
must also send an ac"nowledement sinal to the P5M& to show that this indication has been activated. The P5M&
then returns this ac"nowledement to the service centre.
The short messae service teleservice is described in specification 3GPP T! **.++3 K,<L.
&.0 S$or 5ess%3e over4"o2 i'!ic%io'
.n indication shall be iven to the user of the short messae service when an incomin messae cannot be received
due to insufficient available memory.
&.= 6'er'%io'%" %ccess 4u'cio'
Provision is made for a direct- standard method of ainin international access. 7or this purpose the 32 may have a
"ey whose primary or secondary function is mar"ed HWH. This is sinalled over the air interface and would have the
effect of eneratin the international access code in the networ". %t may be used directly when settin up a call- or
entered into the memory for abbreviated diallin.
This feature is of benefit since the international access code varies between 12PT countries- which miht cause
confusion to a user- and prevent the effective use of abbreviated diallin when roamin internationally. 3sers may still
place international calls conventionally- usin the appropriate international access code.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &" Release 12
&.. Service 6'!ic%or (S6)
.n indication is iven to the user that there is ade?uate sinal strenth (as far as can be juded from the received
sinal) to allow a call to be made. .dditionally the networ" should be capable of providin- and the 32 may display-
an indication of the servin cells# capabilities e.. GP/!- B!;P.- B!3P..
%f indicated by the reistered networ"- the 32 in idle mode may display an indication of one of the radio access
technoloies provided to the 32 in the networ" on which the 32 is reistered with the followin priority orderI 2=
3T/.&- 3T/.&- G2/.&.
;isplayin the servin cell#s capabilities and the access technoloy are mutually e'clusive.
&.10 7u%" To'e Mu"i )re;ue'c8 (7TM))
The 32 shall be capable of initiatin ;TM7 in accordance with specifications 3GPP T! **.++3 K,<L. Optionally- the
32 may provide a suppress function which allows the user to switch off the ;TM7 function.
&.11 :'1:44 s2ic$
The 32 may be provided with a means of switchin its power supply on and off. !witch=off shall be HsoftH- so that on
activation- the 32 completes the followin house"eepin functionsI termination of a current call- detach (where
applicable) and storin re?uired data in the !%ME3!%M before actually switchin off. .s far as possible- this procedure
should also apply on power failure (e.. remote switch=off or low battery).
&.12 Su(-&!!ress
This feature allows the mobile to append andEor receive a sub=address to a ;irectory &umber- for use in call set=up-
and in those supplementary services that use a ;irectory &umber.
&.13 S$or Mess%3e Service +e"" >ro%!c%s
The !hort Messae !ervice 1ell 0roadcast enables the mobile e?uipment to receive short messaes from a messae
handlin system.
The short messae service cell broadcast teleservice is described in specification 3GPP T! **.++3 K,<L
&.14 S$or Mess%3e Service +e"" >ro%!c%s 7RA
This feature enables a mobile e?uipment to save on battery utili(ation- by allowin the mobile e?uipment to not listen
durin the broadcast of messaes the subscriber is not interested in.
&.15 Su##or o4 $e e/e'!e! S$or 5ess%3e ce"" (ro%!c%s
c$%''e"
This feature allows a mobile e?uipment by supportin of the e'tended !hort messae cell broadcast channel to
enhance the capacity of the service. The support of the e'tended channel has low priority- i.e. the 32 can interrupt the
readin of this channel if idle mode procedures have to be e'ecuted.
&.16 *e2or9 6!e'i8 %'! Ti5eDo'e
The feature provides the means for servin P5M&s to transfer current identity- universal time and the local time(one
to mobile e?uipments- and for the mobile e?uipments to store and use this information. This enhances roamin by
permittin accurate indication of P5M& identities that are either newer than the M2 or have chaned their name since
the M2 was sold. .dditionally time and time(one information can be utili(ed by M2s as desired.
The networ" name time and time(one information will normally be transferred from the networ" to the M2I
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &1 Release 12
,) 3pon reisterin on the networ".
*) Chen the 32 eoraphically relocates to a different 5ocal Time Mone.
3) Chen the networ" chanes its 5ocal Time Mone- e.. between summer and winter time.
<) Chen the networ" chanes its identity.
>) .t any time durin a sinallin connection with mobile e?uipment.
7urther details of this feature are described in 3GPP T! **.+<* K,>L.
&.10 *e2or9Gs i'!ic%io' o4 %"eri'3 i' $e UE
This feature provides the means for servin P5M&s to transfer to a 32 an indication that may be used by the 32 to
alert the user in a specific manner in the followin casesI
= mobile terminatin call
= networ" initiated 3!!;
= networ" initiated Mobile Oriinated (MO) connection- if the M2 supports the Hnetwor" initiated MO
connection H feature.
2iht different indications are defined- whether the mobile terminatin traffic is a call or 3!!; or related to the
networ" initiated MO connection procedure. These indications are sent by the networ" and received by the 32I
= Three of these indications are used as levels- reflectin some "ind of urencyI level + indicates that the 32
shall not alert the user for 3!!; and remain silent in the case of call- level * shall be considered by the 32 as
more important than level , for the purpose of alertin the user.
= The five other indications are used as cateories- identifyin different types of terminatin traffic. The 32 shall
inform the user in a specific manner for each of these five cateories. &evertheless- the possible forms of the
alert (different rinin tones- displayed te't- raphical symbols...) is still up to the mobile manufacturer (some
forms of alerts can be simultaneously used- e.. rinin tones and te't on the display).
The manaement of the feature by the 32 re?uires for the handlin of cateories that I
= the !%ME3!%M stores for each cateory an informative te't (ma'imum *> characters per cateory) describin
the type of terminatin traffic associated with the cateory. This information could be used by the 32 when
alertin the user (display on the screen). %t is necessary for the networ" operator to be able to chane the
meanin of each cateory.
= The user has the ability to set up hisEher own association between the type of terminatin traffic (identified by
each cateory) and the different types of alert provided by the 32. To help the user in this choice- the 32 uses
the informative te't associated with each cateory (as stored in the !%ME3!%M). The 32 should "eep this
association when switched off.
;efault settins should also be defined in the M2 for the followin cases I
= when the 32 receives a call- 3!!; or a re?uest for a networ" initiated MO connection with no alertin
indication-
= when the 32 receives a call- 3!!; or a re?uest for a networ" initiated MO connection with a cateory of
alertin not defined in the !%ME3!%M.
These default settins should be separated per type of mobile terminated traffic received (call- 3!!; or re?uest
for a networ" initiated MO connection).
. 32 supportin the feature shall act accordin to the followin points in case of mobile terminatin traffic I
= when a mobile terminatin traffic is received without any indication (level or cateory)- the M2 shall act as if it
was not supportin the feature- i.e. use a default alert (e.. associated with this type of mobile terminatin
traffic).
= if a level is indicated- the 32 shall use an alert enablin the user to differentiate between the three levels.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &2 Release 12
= if a cateory is indicated- then I
= if the !%ME3!%M used in the 32 does not store any information on that feature- the 32 shall inore the
cateory received with any mobile terminatin traffic and act as if it was not supportin the feature- i.e. use
a default alert (e.. associated with this type of mobile terminatin traffic).
= if the cateory is not defined in the !%ME3!%M- the 32 shall act as if it was not supportin the feature- i.e.
use a default alert (e.. associated with this type of mobile terminatin traffic).
= if the cateory is defined in the !%ME3!%M- the 32 shall use the alert associated with this cateory. %n
addition- it would be very useful for the user to be notified of the informative te't associated with this
cateory (e. on the display).
!ome interactions between this feature and other services related to alertin are described below I
= the call waitin service has priority on this feature- i.e. the call waitin tone will be played and not the alert
derived by this feature. %f possible- two different indications should be iven to the user (e.. the call waitin
tone and a te't on the display indicatin call waitin- and in addition a te't relative to the type of the new call
received).
= the presentation of the callin line identity ta"es priority on this feature- if it is not possible to display this
information and another information related to this feature.
= %n case of interaction between this feature and 32 specific features to alert the user (e.. whole silent mode)-
the user should still be able to differentiate between the different levels or different types of terminatin traffic-
even if the alert itself may be chaned.
&.1= *e2or9 i'ii%e! Mo(i"e :ri3i'%e! (M:) co''ecio'
The H&etwor" %nitiated Mobile Oriinated connectionH feature allows the networ" to as" the mobile e?uipment to
establish a mobile oriinated connection. The servin P5M& provides the mobile e?uipment with the necessary
information which is used by the mobile e?uipment to establish the connection.
1urrently only the networ" initiated mobile oriinated call feature is specified. %t is mandatory for a 32 supportin
110! and is used in the case of a 110! recall.
&.1. &((revi%e! !i%""i'3
The directory number or part of it is stored in the mobile e?uipment toether with the abbreviated address. .fter
retrieval the directory number may appear on the display.
.bbreviated diallin numbers stored in the 32 or 3!%M may contain wild characters.
%f wild characters are used to indicate missin diits- each wild character shall be replaced for networ" access or
supplementary service operation- by a sinle diit entered at the "eypad. The completed directory number is
transmitted on the radio path.
&.20 >%rri'3 o4 7i%""e! *u5(ers
This feature provides a mechanism so that by the use of an electronic loc" it is possible to place a bar on callin any
numbers belonin to a pre=prorammed list of numbers in the !%ME3!%M.
0arred ;iallin &umbers stored in the E3!%M may contain wild characters.
3nder control of P%&*- H0arred ;iallin ModeH may be enabled or disabled. The selected mode is stored in the
!%ME3!%M.
3nder P%&* control- it shall be possible to add- modify or delete a particular H0arred ;iallin &umberH (0;&) and to
allocate or modify its associated comparison method(s). This 0;& may have the function of an abbreviated diallin
number E supplementary service control (.;&E!!1)- overflow andEor sub=address.
Chen 0;& is inactive- no special controls are specified- and the barred diallin numbers may be read (thouh not
modified or deleted- e'cept under P%&* control) as if they were normal abbreviated diallin numbers. .ccess to
"eyboard and normal abbreviated diallin numbers (includin sub=address) is also permitted.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &3 Release 12
Chen 0arrin of ;ialled &umbers is activeI
= 1onsiderin a number dialled by the user- if it e'ists a 0;& for which there is a successful comparison (see
below) between that 0;& and the dialled number- then the M2 shall prevent the call attempt to that number. %f
there is no 0;& to fulfil those conditions- the call attempt is allowed by the M2.
Cith each 0;& is associated one (or a combination of) comparison method(s) used between that 0;& and the number
dialled by the user. .t least three different comparison methods are possibleI
= The comparison is made from the first diit of that 0;&- from the first diit of the dialled number and for a
number of diits correspondin to the lenth of the 0;&.
= The comparison is made from the first diit of that 0;&- from any diit of the dialled number and for a
number of diits correspondin to the lenth of the 0;&.
= The comparison is made bac"wards from the last diit of that 0;&- from the last diit of the dialled number
and for a number of diits correspondin to the lenth of the 0;&.
= %f a 0;& stored in the !%ME3!%M contains one or more wild characters in any position- each wild character
shall be replaced by any sinle diit when the comparison between that 0;& and the dialled number is
performed.
= %f a 0;& contains a sub=address- and the same number without any sub=address or with that sub=address is
dialled- the M2 shall prevent the call attempt to that number.
= &umbers specified as HbarredH may only be modified under P%&* control.
= %f the M2 does not support barrin of dialled numbers- the 32 with a 0;& enabled 3!%M shall not allow the
ma"in of calls and the 32 with 0;& enabled !%M shall not allow the ma"in or receivin of calls. Bowever-
this feature does not affect the ability to ma"e emerency calls.
%f H7i'ed &umber ;iallinH and H0arrin of ;ialled &umbersH are simultaneously active- the dialled number shall be
chec"ed aainst the two features before the M2 allows the call attempt. %n that case- a dialled number will only be
allowed by the M2 if it is in the 7;& list and if the comparison between that number and any number from the 0;&
list is not successful.
The 32 may support other selective barrins- e.. applyin to individual services (e.. telephony- data transmission) or
individual call types (e.. lon distance- international calls).
&.21 7TM) co'ro" !i3is se#%r%or
Provision has been made to enter ;TM7 diits with a telephone number- and upon the called party answerin the 32
shall send the ;TM7 diits automatically to the networ" after a delay of 3 seconds (X *+ Y). The diits shall be sent
accordin to the procedures and timin specified in 3GPP T! *<.++9 K,3L.
The first occurrence of the H;TM7 1ontrol ;iits !eparatorH shall be used by the M2 to distinuish between the
addressin diits (i.e. the phone number) and the ;TM7 diits. 3pon subse?uent occurrences of the separator- the 32
shall pause aain for 3 seconds (X *+ Y) before sendin any further ;TM7 diits.
To enable the separator to be stored in the address field of an .bbreviated ;iallin &umber record in the !%ME3!%M-
the separator shall be coded as defined in 3GPP T! 3,.,+* K,:L. The telephone number shall always precede the
;TM7 diits when stored in the !%ME3!%M.
The way in which the separator is entered and display in the 32- is left to the individual manufacturer#s MM%.
M2s which do not support this feature and encounter this separator in an .;& record of the !%ME3!%M will treat the
character as Hcorrupt dataH and act accordinly.
&.22 Se"ecio' o4 !irecor8 'u5(er i' 5ess%3es
The !hort Messae !ervice (!M!)- 1ell 0roadcast !ervice (10!)- Multimedia Messae !ervice (MM!)- &etwor"
%nitiated 3!!; or &etwor" /esponse to Mobile Oriinated 3!!; messae strins may be used to convey a ;irectory
&umber- which the user may wish to call.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &$ Release 12
&.23 L%s *u5(ers 7i%""e! (L*7)
The 5ast H&H &umbers dialled may be stored in the !%ME3!%M andEor the M2. H&H may ta"e the value up to ,+ in the
!%ME3!%M. %t may be any value in the M2. The method of presentation of these to the user for settin up a call is the
responsibility of the 32 but if these numbers are stored in both the !%ME3!%M and the 32- those from the !%ME3!%M
shall ta"e precedence.
&.24 Service 7i%""i'3 *u5(ers
The !ervice ;iallin &umbers feature allows for the storae of numbers related to services offered by the networ"
operatorEservice provider in the !%ME3!%M (e.. customer care). The user can use these telephone numbers to ma"e
outoin calls- but the access for updatin of the numbers shall be under the control of the operator.
&oteI &o MM% is envisaed to be specified for these numbers and it is left to mobile manufacturer
implementations.
. specific e'ample of !ervice ;iallin &umbers is the storae of mailbo' diallin numbers on the !%ME3!%M for
access to mailbo'es associated with @oicemail- 7a'- 2lectronic Mail and Other messaes.
&.25 )i/e! 'u5(er !i%""i'3
This feature provides a mechanism so that by the use of an electronic loc" it is possible to place a bar on callin any
numbers other than those pre=prorammed in the !%ME3!%M.
3nder control of P%& *- H7i'ed ;iallin ModeH may be enabled or disabled. The mode selected is stored in the
!%ME3!%M.
7i'ed ;iallin &umbers (7;&s) are stored in the !%ME3!%M in the 7i'ed ;iallin &umber field. 7;& entries are
composed of a destination addressE!upplementary !ervice 1ontrol. ;estination addresses may have the format
relevant to the bearer servicesEteleservices defined in K*,L and K,<L. 7;& entries may ta"e the function of an
.bbreviated ;iallin &umberE!upplementary !ervice 1ontrol (.;&E!!1)- Overflow andEor sub=address. 7i'ed
;iallin &umbers stored in the !%ME3!%M may contain wild card characters.
The 7i'ed ;iallin feature is optional- however when 7i'ed ;iallin Mode is enabled- an M2 supportin the feature
shallJ
= Prevent the establishment of bearer servicesEteleservices to destination addresses which are not in 7;& entries
on a per bearer serviceEteleservice basis. The list of bearer servicesEteleservices e'cluded from the 7;& chec"
shall be stored in the !%ME3!%M. Those bearer servicesEteleservices are characterised by their service code as
described in K*3L. 7or instance if the !M! teleservices is indicated in this list- !M! can be sent to any
destination. 0y default- the M2 shall prevent the establishment of any bearer serviceEteleservice to destination
addresses which are not in 7;& entries.
= Only allow modification- addition or deletion of 7i'ed &umber ;iallin entries under control of P%&*.
= .llow the establishment of bearer servicesEteleservice to destination addresses stored in 7;& entries. 7or !M!-
the !ervice 1enter address and the end=destination address shall be chec"ed.
= !upport the readin and substitution of wildcards in any position of an 7;& entry- via the M2 MM%.
= .llow the user to replace each wildcard of an 7;& entry by a sinle diit- on a per call basis without usin
P%&*. The diit replacin the wildcard may be used for networ" access or supplementary service operation.
= Only allow !upplementary !ervice (!!) 1ontrol (in ;edicated or %dle mode) if the !! control strin is stored as
an 7;& entry.
= .llow the e'tension of an 7;& entry by addin diits to the 7i'ed ;iallin number on a per call basis.
= .llow the emerency numbers (see !ection 9.<) to be called- even if it is not an 7;& entry.
= .llow normal access to .;& fields (i.e. allow .;& entries to be modified- added or deleted) and the "eyboard.
= .llow use of .;&s subject to the 7;& filter.
Chen 7;& is disabled- an M2 supportin 7;& shallJ
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 && Release 12
= .llow 7;& entries to be read as thouh they were normal .;& entries.
= Only allow modification- addition or deletion of 7i'ed &umber ;iallin entries under control of P%&*.
= .llow normal access to .;& fields and the "eyboard.
%f the M2 does not support 7;&- the 32 shall not allow the ma"in of calls when 7i'ed ;iallin is enabled in the
3!%M- and the 32 shall not allow the ma"in or receivin of calls when 7i'ed ;iallin is enabled in the !%M.
Bowever- emerency calls (,,* and other user defined emerency numbers) shall still be possible.
&oteI Cildcards are stored on the !%ME3!%M. The wildcard codin is iven in 3GPP T! 3,.,+* K,:L.
&.26 Mess%3e ?%ii'3 6'!ic%io'
. short messae may be used to provide and indication to the user about the status and number of types of messaes
waitin on systems connected to the P5M&. The M2 shall present this indication as an icon on the screen- or other
MM% indication- and store the indication status on the !%ME3!%M to allow the status to be retained throuh power
offEon- !%ME3!%M movement between 32s etc..
The M2 shall be able to accept and ac"nowlede these messae waitin status short messaes irrespective of the
memory available in the !%ME3!%M.
&.20 Re;uire5e's 4or $e r%'s4er o4 e+%"" Mi'i5u5 Se o4 7%%
(MS7)
Cith the e'ception of the followin specific re?uirements- considered necessary for the satisfactory operation of the
e1all service- all e'istin T!,* emerency call re?uirements shall apply.
.n e1all shall consist of a T!,* emerency call supplemented by a minimum set of emerency related data (M!;).
The M!; e.. vehicle identity- location information and other parameters- is defined by 12& K<AL.
= .n e1all may be initiated automatically- for e'ample due to a vehicle collision- or manually by the vehicle
occupantsJ
= .n %@!- or other 32 desined to support e1all functionality- shall include in the emerency call set=up an
indication that the present call is either a Manually %nitiated e1all (M%e1) or an .utomatically %nitiated e1all
(.%e1).
= The Minimum !et of ;ata (M!;) sent by the %n vehicle !ystem (%@!) to the networ" shall not e'ceed ,<+
bytesJ
= The M!; should typically be made available to the P!.P within < seconds measured from the time when end
to end connection with the P!.P is establishedJ
= !hould the M!; component not be included in an e1all- or is corrupted or lost for any reason- then this shall
not affect the associated T!,* emerency call speech functionality.
= . call proress indication shall be provided to the user whilst the M!; transmission is in proress.
= To reduce the time ta"en to establish an e1all an %@! whilst in e1all only mode- may receive networ"
availability information whilst not reistered on a P5M&.
= P5M&s should ma"e use of e1all indicators- received in the emerency call set=up- to differentiate e1alls from
other T!,* emerency calls.
= The M%e1 and .%e1 should be used by the servin networ" to filter and route e1alls to dedicated- e1all
e?uipped- P!.Ps.
= Chere the e1all indicators are not supported by the servin networ"- the time needed for the P!.P e1all
modem to differentiate between e1alls and other T!,* calls- before routin the call to an operator- shall not
e'ceed * seconds from when the %@! receives notification that the P!.P has answered the call.
= The P!.P shall be iven an indication that the incomin call is an e1all.
Throuhout the duration of the emerency call and followin receipt of the M!; by the P!.P
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &' Release 12
= %t shall be possible for the P!.P to send a confirmation to the %@! that the M!; has been acted upon.
= %t shall be possible for the P!.P to re?uest the %@! to re=send its most recent M!;.
= %t shall be possible for the P!.P to instruct the %@! to terminate the e1all.
&.2= Re;uire5e's 4or @6' +%se o4 E5er3e'c8@ (6+E) i'4or5%io'
The %n 1ase of 2merency (%12) information are used to enable first responders- such as paramedics- fire=fihters-
and police officers- to contact a victimQs emerency contact(s) in order to identify the victim and obtain important
medical information or other information re?uired durin an emerency.
. 32 shall have the capability to store one or more N%12 informationO on the 3%11. The N%12 informationO shall list
the type of information which is to be confiured by the mobile operator as described in the table below.
Ta8le A!2)!1- 923. information9 description
%12 information
type format
%12 information
type value
%12 information
value ,
%12 information
value *
%12 information
value n
;escription Two formats shall
be defined in this
releaseI
,= Phone number
format. 7or the
phone number
format it shall be
possible to store a
name and a
phone number.
*= 7ree format.
%t shall be
possible for the
mobile operator
to provision (ero-
one or several
instances of a
iven format on
the 3%11.
%t shall be
possible to store
this information
in te't or raphic
format.
%t shall be
possible to have at
least one %12
information value
field. %f more than
one information
value fields are
re?uired it shall
be indicated by
the %12
information type
format.
%t shall be
possible for the
subscriber to add-
modify- view- or
delete any %12
information
value.
7or the free
format %12
information type
format- it shall be
possible to store
information in
te't or raphic
format.
7or pre=defined
%12 information
type formats the
M2 should adapt
the input mode to
the type of the
%12 information
value (e..
numerical mode
for phone number
input).
Present only if
e'plicitly
indicated by the
%12 information
type format.
Present only if
e'plicitly
indicated by the
%12 information
type format.
The followin table provides an e'ample of %12 information stored on the 3%11I
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &( Release 12
Ta8le A!2)!2- :23. information; e/ample
%12 information type %12 information type value %12 information value , %12 information value *
Phone &umber H1ontact in case of
emerencyH
My Cife W33A<>AA
Phone &umber H1ontact in case of
emerencyH
7amily !mith W33A<>A>
Phone &umber H1ontact in case of
emerencyH
My 7amily doctorI ;r.
Vones
W33A<3*3<
7ree 7ormat HMedical %nformationH My blood type is .W- % am
alleric to etc.
&E.
7ree 7ormat HBome Postal .ddressH ,> rue de la Pai'- Paris-
7rance
&E.
7ree 7ormat N5anuaeO 7rench &E.
7ree 7ormat NTravel %nformationO 5ondon- from 3
rd
Vuly. to
*:
th
Vuly- *++9
&E.
Provision is made for direct and unambiuous read access from the 32 to %12 information stored on the 3%11.
The subscriber may choose not to enter any %12 information.
The default confiuration for this information shall be that they are accessible even when the security features on
either the 32 or 3%11 have been enabled (e.. the "eypad is loc"ed). %t shall be possible for the subscriber to chane
this default settin to prevent accessibility to the %12 information (i.e. a user confiurable settin in the 3%11
indicates whether the %12 information on the 3%11 shall be displayed or not- if the %12 access procedure described in
T! **.+3+ KAL is invo"ed).
The unloc"in of %12 information shall not allow access to other secure information on the 3%11 or 32. The %12
information value should not be accessible to M2 or 3%11 applications.
The %12 access procedure is described in T! **.+3+ KAL.
&''e/ > (i'4or5%ive),
&!!iio'%" 'u5(er use c%se
1ompany G is customer of operator M and has a subscription for voice and data with ,+ !%M cards. The company also
decides to subscribe to the private numberin plan feature of operator M. . certain corporate phone number is assined
to company G- e.. W<3 A8A 99999 '' (with '' bein the e'tensions of the users)- and they can freely choose the
e'tensions for up to ,++ !%M cards.
%nitially company G ta"e the e'istin ,+ !%M cards (with the e'istin M!%!;&s) and interate them into the private
numberin plan by assinin the e'tensions ,, to *+ to these cards via a web portal. This is not a permanent
assinment- the e'tensions can be chaned easily any time- old !%Ms can be deleted from the private numberin plan
and new ones can be interated whenever necessary. !pecial privilees or restrictions can be chosen on a per !%M
basis via the portal and special tariffs apply.
The 12O of company G calls a customer. The customer#s phone displays the corporate number W e'tension of the
12O as 15%. .fter a while the customer decides to call bac" the 12O and uses the corporate number W e'tension as
M!%!;&. 5ater they also e'chane some short messaes- aain the corporate number W e'tension of the 12O is used
as sender#s M!%!;&.
7or all these calls and short messaes operator M is able to collect charin records containin the corporate number W
e'tension.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &) Release 12
The 12O also uses her smart phone to establish P! connections to browse the internet and to access the intranet via
the operator#s ateway. The corporate number W e'tension is used for authentication and authorisation in the
company#s intranet and its web applications. 1harin for P! connections by operator M is also based on this number.
%n eneral the users in company G are not aware of their NrealO underlyin M!%!;&s in the system- they only see the
corporate number W their e'tension and there is no need for them to "now the underlyin M!%!;&.
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 &* Release 12
&''e/ + (i'4or5%ive),
+$%'3e $isor8
3han,e history
)-' 0o. ,Doc. 0o. /. 0o. )ection
affected
0e;
version
)ub<ect=omments
!MGZ** 3+*E:8 ++, <.A (/ole
Model)
3.,.+ !MG3 ?ueried the separation of networ"
operator into core and access- which- on
e'amination- !MG, find unhelpful
!MGZ** 3,:E:8
(!MG,
CP1
,*>E:8)
++* 3.,.+ 2ditorial 1hanesI 75MPT! was replaced by
%MT *+++- * new references iven- additional
clarifications.
!MGZ** 3*+E:8 ++3 9.>- :.3-
:.>- ,8
3.,.+ 1hanes on 2merency 1alls- 3ser
identification- Multiple profiles and additional
handover re?uirements.
.fter
!MGZ*3
!MG,
<33uE:8
:A>E:8
++< ;raft
3.*.+
0ased on .pproved 1hanes at !MGZ**
;istributed at !MG, in ;resden &ov 3=8- :8
to be .pproved at !MGZ*<
!MGZ*< :AAE:8 ++> !ections
9- :- ,,
3.*., /estructurin of sections 9-: and ,, to ather
all re?uirements relatin to multiple
subscriptions into one section and to improve
the clarity.
!MGZ*< :A8E:8 ++A !ection
9.,
3.*., To improve the accuracy of te't on numberin
principles and minor editorial chane to
section 9.,
!MGZ*8 :9=+>>, ++8 !ection
<.A and
misc.
3.3.+ /emoval of commercial role model from the
specification in order to improve clarity
SMG#27 98-0552
(Not
Approed!
008 Ne" Section
#8
(Not Applied!
$%$%0
&o include re'uirements (or net"or) selection in serice
principles* N+& A,,R+-./ 0 N+& A,,12./
(re>
!MGZ*9
(SMG# &doc
98-089$!
::=+<+
++9 r<
/ejected
&ew
!ection ,9
.pplied
K;raft
3.<.+L
.dded &etwor" !election section = .reed by
correspondence = Van ,3- ,::: = Prepared with
1/s applied with revision mar"s
!MGZ*8 :9=+>>3 ++: !ection <.3 3.3.+ To remove unnecessary reference to %& and 0=
%!;&
!MGZ*8 :9=+A9* +,+ !ection ,, 3.3.+ To improve the clarity of service re?uirements
for multiple user profiles
Pre-
SMGH2=
(SMG1
Tdoc
98-0869)
..-040
011 Secio's 1, 2,
3, 4, ., 10,
12, 10
7r%4 3.4.0
+"e%' u# 4or UMTS #$%se 1
&3ree! % SMG1 Ro5e
Pre-
SMGH2=
(SMG1
Tdoc
98-852)
..-040
012 Secio's
3,=,.,11,14,1
5
7r%4 3.4.0
+$%'3es i' 6+ c%r! %'! er5i'%" service re;uire5e's
&3ree! % SMG1 Ro5e
Pre-
SMGH2=
(SMG1
Tdoc
98-0894)
..-040
013r1 Secio' 3.2
E 4.3
7r%4
3.4.0
+"%ri4ic%io' o4 3e'er%" re;uire5e's 4or e44icie' use o4
r%!io resources
&3ree! (8 corres#o'!e'ce - I%' 13, 1... - Pre#%re!
2i$ +Rs %##"ie! 2i$ revisio' 5%r9s
*oe 7r%4 3.4.0
SMG1 %3ree! o'"8
#re-SMGH2= ..-040 015
ReJece!
10 7r%4 3.4.0
&ccor!i'3 o $e ouco5e o4 $e SMG 1 %!-$oc 5eei'3
o' $%'!over issues i is #ro#ose! $% i'er-o#er%or
$%'!over is 'o re;uire! 4or UMTS #$%se 1.(reJece! (8
s53H2=)
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '" Release 12
3han,e history
)-' 0o. ,Doc. 0o. /. 0o. )ection
affected
0e;
version
)ub<ect=omments
SMGH2= ..-305 00=r5 Revise!
Secio' 1=
3.4.0
*e2or9 Se"ecio' #rese'e! % SMGH2= i' 2201K00=r4
2%s 4ur$er revise! %'! &##rove! % SMGH2=.
*oe 3.4.0
Re5ov%" o4 Secio' 12 o' UPT 2i$ +R 011 c%uses %
s9i# secio' 4ro5 Secio' 11 o 13.
!an"e !istor#
TSG SA7 SA <oc! SA1 <oc Spec 3R Rev Rel 3at Su8ject=3omment >ld ?e@ A2
SP-03 SP-..104 S1-..202 22.101 &016 R.. > +o'ro" o4 su##"e5e'%r8 services
(GSM 02.04), 5%8 use MM6
#roce!ures s#eci4ie! i' GSM
02.30 %'! e/isi'3 GSM MM6
re"%e! MS 4e%ures (GSM 02.00)
5%8 %"so (e use!.
3.4.0
Pos-
S&H3
22.101 R.. U#!%e! Lo3o, B 3.5.0 3.5.1
SP-04 SP-..22. S1-..3=0 22.101 021 R.. > Mu"i*u5(eri'3, 6 2i"" (e
#ossi("e 4or 5u"i#"e MS6S7*s o
(e %ssoci%e! 2i$ % si'3"e
su(scri#io'.
3.5.0 3.6.0
SP-04 SP-..226 S1-..3.5 22.101 020 0 R.. > E5er3e'c8, To roue $e c%"" o
$e %##ro#ri%e e5er3e'c8
service i4 5ore $%' o'e
e5er3e'c8 'u5(er is su##ore!
i' % cou'r8.
3.5.0 3.6.0
SP-05 SP-..43. S1-..030 22.101 025 R.. > Su##or o4 S&T (8 US6M 3.6.0 3.0.0
SP-05 SP-..43. S1-..=16 22.101 024 R.. > +"%ri4ic%io' o' $e us%3e o' 2G
S6M %'! 3G US6M
3.6.0 3.0.0
SP-05 SP-..435 S1-..=51 22.101 022 R.. + +"%ri4ic%io' o4 E5er3e'c8 +%""
re;uire5e's
3.6.0 3.0.0
SP-06 SP-..524 S1-..1031 22.101 02. R.. > E5er3e'c8 +%"" 3.0.0 3.=.0
SP-06 SP-..520 S1-..103= 22.101 02= R.. + )7* 3.0.0 3.=.0
SP-06 SP-..51. S1-..1026 22.101 026 R.. 7 M%i'"8 e!iori%" u#!%e 4or
GSM13GPP use.
3.0.0 3.=.0
SP-00 SP-000060 S1-000112 22.101 030 R.. & Su##or o4 e'cr8#io' i' GPRS
5o(i"e s%io's
3.=.0 3...0
SP-00 SP-000000 S1-000130 22.101 031 R.. ) )i/e! 7i%"i'3 *u5(er ()7*) 3.=.0 3...0
SP-0= SP-000210 S1-000201 22.101 033 R.. 7 *e2or9 se"ecio' #roce!ures
re5ove! 4ro5 secio' 16,
re4ere'ce o 22.011 %!!e!
3...0 3.10.0
SP-0= SP-000200 S1-000350 22.101 035 R.. > E5er3e'c8 +%""s %'! 'u5(ers
use!
3...0 3.10.0
SP-0= SP-000201 S1-000362 22.101 03= R.. ) +S 5u"i5e!i% su##or 3...0 3.10.0
SP-0= SP-000202 S1-000326 22.101 03. R.. ) +"%ri4ic%io' 4or US6M &##"ic%io'
se"ecio'
3...0 3.10.0
SP-0= SP-000210 S1-000200 22.101 034 R00 7 *e2or9 se"ecio' #roce!ures
re5ove! 4ro5 secio' 16,
re4ere'ce o 22.011 %!!e!
3...0 4.0.0
SP-0= SP-000200 S1-000351 22.101 036 R00 > E5er3e'c8 +%""s %'! 'u5(ers
use!
3...0 4.0.0
SP-0= SP-000213 S1-000352 22.101 030 R00 > E5er3e'c8 +%"" e'$%'ce5e's 3...0 4.0.0
SP-0. SP-0003=3 S1-000603 22.101 040 R4 > Mu"i5e!i% 5ess%3i'3 4.0.0 4.1.0
SP-0. SP-0003=3 S1-000605 22.101 041 R4 + Service M%'%3e5e'
re;uire5e's
4.0.0 4.1.0
SP-0. SP-000430 S1-000000 22.101 042 1 R4 ) Ge'er%" correcio's %'!
c"%ri4ic%io's o 22.101 4or
Re"e%se 2000
4.0.0 4.1.0
SP-0. SP-0003=3 S1-0005.= 22.101 046 R4 7 E!iori%" c$%'3es o 22.101 4or
Re"e%se 2000
4.0.0 4.1.0
SP-0. SP-000430 S1-0006.= 22.101 040 1 R4 + *u5(eri'3 Pri'ci#"es 4.0.0 4.1.0
SP-0. SP-0003=3 S1-000620 22.101 04= R4 + Service evo"uio' 4.0.0 4.1.0
SP-0. SP-0003.1 S1-000503 22.101 04. R4 7 E5er3e'c8 +%"" 4.0.0 4.1.0
SP-0. SP-000405 S1-00064. 22.101 050 R4 > Te/ +o'vers%io' 4.0.0 4.1.0
SP-0. SP-0003=3 S1-000625 22.101 043 R5 ) +"%ssi4ic%io' o4 services 4.0.0 5.0.0
SP-0. SP-0003=3 S1-000622 22.101 044 R5 > 6P 5u"i5e!i% services 4.0.0 5.0.0
SP-0. SP-0003=3 S1-000621 22.101 045 R5 > 6P 5u"i5e!i% sessio' 4or
E5er3e'c8 c%""
4.0.0 5.0.0
SP-0. SP-000430 S1-0006.. 22.101 051 R5 + 6M *u5(er #or%(i"i8 4.0.0 5.0.0
SP-0. SP-000430 S1-000001 22.101 052 R5 ) 6'ro!ucio' o4 6M +* Su(s8se5 4.0.0 5.0.0
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '1 Release 12
!an"e !istor#
SP-0. SP-0003=3 S1-000004 22.101 053 R5 ) Su(scri#io' 4.0.0 5.0.0
SP-0. SP-0003=3 S1-000005 22.101 054 R5 ) Ro%5i'3 4.0.0 5.0.0
SP-10 SP-000533 S1-0000.. 22.101 05. Re"-5 & 7e"ei'3 E'cr8#e! US6M-ME
i'er4%ce
5.0.0 5.1.0 TE64
SP-11 SP-010053 S1-010002 22.101 063 Re"-5 & <%'!"i'3 o4 i'er%cio's (e2ee'
%##"ic%io's re;uiri'3 $e %ccess
o UE resources
5.1.0 5.2.0 Service
+"e%' u#
R..
SP-11 SP-010054 S1-01020= 22.101 065 Re"-5 & PLM* '%5e i'!ic%io' 5.1.0 5.2.0 TE64
SP-11 SP-010055 S1-01010. 22.101 060 Re"-5 & +R o 22.101 o' 6'ro!ucio' o4
+P<S 4e%ures
5.1.0 5.2.0 U6++1-
+P<S
SP-11 SP-010056 S1-010210 22.101 06. Re"-5 & 7is#"%8 o4 service #rovi!er '%5e
i' $e UE
5.1.0 5.2.0 TE64
SP-11 SP-010050 S1-010250 22.101 000 Re"-5 + +R o 22.101 o' +"%ri4ic%io's o'
6MS e5er3e'c8 c%"" su##or
5.1.0 5.2.0 EM+1-PS
SP-12 SP-010262 S1-010505 22.101 002 Re"-5 & Re#"%ce5e' o4 re4ere'ces o
23.121 4or R4 o'2%r!s
5.2.0 5.3.0 TE64
SP-12 SP-01025= S1-010504 22.101 003 Re"-5 + Su(scri#io' %'! Provisio'i'3 5.2.0 5.3.0 TE65
SP-12 SP-010255 S1-010500 22.101 005 Re"-5 & &!!iio' o4 % Sre%5i'3
#%r%3r%#$
5.2.0 5.3.0 PSTRE&M
SP-12 SP-010263 S1-010351 22.101 000 Re"-5 & +S Mu"i5e!i% 4%""(%c9 o s#eec$ 5.2.0 5.3.0 TE64
SP-12 SP-010253 S1-0105.5 22.101 0=0 Re"-5 & +"%ri4ic%io' o4 PLM* *%5e
6'!ic%io' %'! Service Provi!er
*%5e 6'!ic%io' 4e%ure.
5.2.0 5.3.0 SP&*ME
SP-13 SP-010441 S1-010=32 22.101 0=4 Re"-5 & &!!iio' o4 % s%e5e' o'
#%r%5eer sor%3e o' $e
S6M1US6M.
5.3.0 5.4.0 TE64
SP-13 SP-010436 S1-010==. 22.101 0=6 1 Re"-5 ) 7e4i'iio' o4 <o5e E'viro'5e' 5.3.0 5.4.0 V<E1
SP-15 SP-020052 S1-02060. 22.101 0=0 Re"-5 > +R 22.101 Re".5 > Service
c$%'3e %'! 4%""(%c9 4or U761R76
5u"i5e!i% c%""s
5.4.0 5.5.0 S+U76)
SP-15 SP-02004. S1-020510 22.101 0== Re"-5 + +R o 22.101o' 6MS %ccess 5.4.0 5.5.0 43000
SP-15 SP-020051 S1-020613 22.101 0=. Re"-5 + +R o 22.101 o' o' US6M
su##or i' Re"-5 GSM o'"8
er5i'%"s
5.4.0 5.5.0 U6++1
SP-15 SP-020050 S1-02065= 22.101 0.0 Re"-5 + +R o 22.101 o' &ccess o 6MS
services usi'3 6S6M
*oe, s#eci%" !is#e's%io' 2%s
3ive' (8 S& H15 o %""o2 so5e
"ee2%8 o' $e secio' 'u5(eri'3.
5.4.0 5.5.0 TE616S6M
SP-15 SP-020045 S1-020450 22.101 0.2 - Re"-5 & E!iori%" +R o correc er5s %'!
re4ere'ces
5.4.0 5.5.0 +:RRE+T
SP-15 SP-020126 22.101 0.3 Re"-5 ) +orrecio' o4 re4ere'ces o
o(so"ee S6P R)+ 2543 6ET)
s#eci4ic%io'
5.4.0 5.5.0 6MS-++R
SP-16 SP-0203=1 22.101 0.5 1 Re"-5 ) +R o 22.101 v5.5.0 o' REL5
c"e%' u#
5.5.0 5.6.0 6MS
SP-16 SP-020255 S1-020=4= 22.101 0.6 Re"-6 7 +R o 22.101 v5.5.0 o' E!iori%"
4or REL6
5.5.0 6.0.0 6MS
SP-10 SP-020550 S1-021=4. 22.101 103 Re"-6 ) +"%ri4ic%io' o4 S6M su##or i'
Re"-6
6.0.0 6.1.0 TE64
SP-10 SP-020550 S1-021055 22.101 104 Re"-6 > +R o 22.101 Re5ov%" o4
i5#"e5e'%io' !e%i"s 4or
!irecor8 'u5(er i' SMS %'!
o$er services
6.0.0 6.1.0 TE66
SP-10 SP-020550 S1-021005 22.101 105 Re"-6 ) +R o 22.101 Re"-6 +"e%' u# o4
6MS Re" 6 o re-i's%e
re;uire5e's
6.0.0 6.1.0 6MS
SP-1= SP-02065= S1-022064 22.101 100 Re"-6 > +R o 22.101 o' 6MS 'u5(er
#or%(i"i8 rev o4 1.0.
6.1.0 6.2.0 6MS
SP-1= SP-02065= S1-02211. 22.101 10= Re"-6 > +R o 22.101 Re" 6 o'
E5er3e'c8 c%""s
6.1.0 6.2.0 EM+1
SP-1= SP-020666 S1-022263 22.101 10. Re"-6 > +R o 22.101 o' ?L&*
i'er2or9i'3
6.1.0 6.2.0 ?L&*
SP-1= SP-020651 S1-022340 22.101 113 Re"-6 & +R o 22.101 o' Su##or o4 S6M
%'! US6M i' REL-6
6.1.0 6.2.0 TE65
SP-1. SP-030022 S1-030215 22.101 114 - Re"-6 > Si5u"%'eous co''ecio' o
3GPP s8se5s %'! 6-?L&*s
6.2.0 6.3.0 ?L&*-+R
SP-1. SP-030035 S1-03026. 22.101 115 - Re"-6 > Re;uire5e's 4or *e2or9
S$%ri'3 i' Re"-6
6.2.0 6.3.0 *TS$%r-
+R
SP-1. SP-03014= S1-030250 22.101 110 - Re"-6 & +R o 22.101 Re" 6 o' S6M
su##or
6.2.0 6.3.0 TE65
SP-20 SP-030351 22.101 125 1 Re"-6 & &"i3'5e' o4 Su(scri(er 6.3.0 6.4.0 TE65
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '2 Release 12
!an"e !istor#
6!e'i4ic%io' re;uire5e's o
curre' i5#"e5e'%io'
SP-21 SP-030450 S1-030.11 22.101 12= - Re"-6 & +"%ri4ic%io' o' US6M-(%se!
%ccess o 6MS
6.4.0 6.5.0 6MS
SP-21 SP-0304.2 S1-03104. 22.101 132 Re"-6 + +"e%'u# %'! 5o!i4ic%io's o'
i!e'i4ic%io' o4 e5er3e'c8
'u5(ers i' 22.101 Re"-6
6.4.0 6.5.0 EM+1
SP-21 SP-030534 S1-031061 22.101 134 1 Re"-6 & Su##or o4 Re"e%se 4 S6M i'
Re"e%se 6
6.4.0 6.5.0 TE65
SP-22 SP-030000 S1-03133. 22.101 135 - Re"-6 > &uo5%ic 7evice 7eecio' 6.5.0 6.6.0 TE6
SP-22 SP-030000 S1-031342 22.101 136 - Re"-6 + +orrecio' o4 +ore *e2or9
e5er3e'c8 c%"" re;uire5e's
6.5.0 6.6.0 EM+1
SP-22 SP-0306=0 S1-031344 22.101 130 - Re"-6 + +"%ri4ic%io' o4 e5er3e'c8 c%""
re;uire5e's
6.5.0 6.6.0 EM+1
SP-22 SP-0300.0 - 22.101 141 - Re"-6 & Re5ov%" o4 u''ecess%r8
'u5(ers 4ro5 $e ME !e4%u"
e5er3e'c8 'u5(er "is (Re"-6)
6.5.0 6.6.0 EM+1
SP-23 SP-0400=4 S1-0401.= 22.101 145 - Re"-6 & &"i3'5e' o TS 31.102 o'
)7*1>7* u'su##ore! er5i'%"
#roce!ure.
6.6.0 6.0.0 TE6
SP-23 SP-0400.1 S1-040215 22.101 146 - Re"-6 > 65#rove5e's o +ircui S2ic$e!
Vi!eo %'! Voice Service
#roce!ures
6.6.0 6.0.0 +S-VVS
SP-23 SP-040101 S1-04025= 22.101 150 - Re"-6 7 E/r%cio' o4 re!u'!%' ?L&*
i'4or5%io' L 'o2 i' ?L&*
TS22.234
6.6.0 6.0.0 ?L&*
SP-23 SP-040101 S1-040262 22.101 151 - Re"-6 7 E/r%cio' o4 re!u'!%' ?L&*
re"%e! si5u"%'eous co''ecio'
i'4or5%io' M 'o2 i' ?L&*
TS22.234N
6.6.0 6.0.0 ?L&*
SP-24 SP-0402== S1-040420 22.101 152 - Re"-6 ) +orrecio' o4 U6++ re"%e! e/. 6.0.0 6.=.0 TE6
SP-24 SP-0402.2 S1-040530 22.101 154 - Re"-6 ) E!iori%" +orrecio' o4 R5
re4ere'ce
6.0.0 6.=.0 6MS2
SP-24 SP-040301 S1-040513 22.101 153 - Re"-0 > Ter5i'%io' o4 "oc%io' #riv%c8
overri!e 4or e5er3e'c8 c%""s
6.0.0 0.0.0 L+S2O
EM+1
SP-20 SP-05005= S1-050161 22.101 15= - Re"-0 & +"e%'-u# i' +ore *e2or9
:#er%or *%5e 6'!ic%io' secio'
(22.101)
0.0.0 0.1.0 *TS$%r
SP-20 SP-05005. S1-050252 22.101 160 - Re"-0 & Re5ov%" o4 Re4ere'ce o TS
22.121
0.0.0 0.1.0 TE60
SP-2= SP-050216 S1-05051. 22.101 163 - Re"-0 & +"%ri4ic%io' o' o#io'%"i8 o4
Service Provi!er *%5e i'!ic%io'
0.1.0 0.2.0 TE6-6
SP-2= SP-050225 S1-0505=1 22.101 164 - Re"-0 > Voice c%"" co'i'ui8 re;uire5e's 0.1.0 0.2.0 V++
SP-2. SP-050522 S1-0500.3 22.101 0165 - Re"-0 ) +orrecio' o4 e5er3e'c8 'u5(er
e/%5#"e
0.2.0 0.3.0 TE60
SP-2. SP-050522 S1-050=03 22.101 0166 - Re"-0 ) Re;uire5e's o' $e 8#e o4
e5er3e'c8
0.2.0 0.3.0 TE60
SP-2. SP-050522 S1-0500.6 22.101 0160 - Re"-0 + Mo!i4ic%io' o c$%#er 4.2 o'
service c%#%(i"iies
0.2.0 0.3.0 TE60
SP-2. SP-05051= S1-050=.6 22.101 016= - Re"-0 ) Re4i'e5e' o4 3e'er%" !escri#io'
o4 V++
0.2.0 0.3.0 V++
SP-2. SP-05051= S1-050=.0 22.101 016. - Re"-0 + +$%r3i'3 re;uire5e's 4or voice
c%"" co'i'ui8
0.2.0 0.3.0 V++
SP-2. SP-05051= S1-050.36 22.101 0101 1 Re"-0 + +"%ri4ic%io' o4 V++ Tri33ers 0.2.0 0.3.0 V++
SP-2. SP-050522 S1-050.06 22.101 0102 - Re"-0 ) +"%ri4ic%io' o' $e i!e'i4ic%io'
o4 e5er3e'c8 'u5(ers
0.2.0 0.3.0 EM+1
SP-2. SP-050522 S1-050==3 22.101 0103 - Re"-0 > Provisio'i'3 #%r%5eers sore!
o' US6M
0.2.0 0.3.0 TE60
SP-2. SP-05051= S1-050.34 22.101 0104 - Re"-0 + Su##"e5e'%r8 Service
Re;uire5e's 4or V++
0.2.0 0.3.0 V++
SP-30 SP-050050 S1-051145 22.101 0106 - Re"-0 ) +orreci'3 re4ere'ce o :M& 7M
%'! +"ie' #rovisio'i'3
s#eci4ic%io's
0.3.0 0.4.0 TE60
SP-30 SP-050046 S1-05120. 22.101 0100 - Re"-0 ) +"%ri4ic%io' o4 su##"e5e'%r8
servces re;uire5e's 4or V++
0.3.0 0.4.0 V++
SP-30 SP-050046 S1-051220 22.101 010= - Re"-0 ) +"%ri4ic%io' o4 V++ Tri33ers 0.3.0 0.4.0 V++
SP-30 SP-050030 S1-051236 22.101 010. - Re"-0 & 6'ro!ucio' o4 +e"" c%#%(i"i8
i'!ic%or
0.3.0 0.4.0 TE66
SP-30 SP-050=05 - 22.101 01=0 1 Re"-0 > E5er3e'c8 si# uri o (e sore! i'
MT
0.3.0 0.4.0 EM+1
SP-31 SP-060200 - 22.101 01=2 1 Re"-= ) 6'c"usio' o4 &6P* 2i$i' $e
3GPP service #ri'ci#"es
s#eci4ic%io'
0.4.0 =.0.0 &6P*
SP-32 SP-06044= - 22.101 01=6 1 Re"-= ) +orrecio's o %"i3' $e Re"-= %'! =.0.0 =.1.0 TE6=
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '3 Release 12
!an"e !istor#
("%es) Re"-0 versio's o4 TS
22.101
SP-32 SP-060316 S1-060561 22.101 01=0 - Re"-= > V++ &!!iio'%" 4"e/i(i"i8 =.0.0 =.1.0 V++
SP-32 SP-060315 S1-060621 22.101 01.1 - Re"-= & +"%ri4ic%io' o4 6MS voice service =.0.0 =.1.0 V++
SP-32 SP-060435 - 22.101 01.2 1 Re"-= > CoS P%r%5eers Provisio'i'3 =.0.0 =.1.0 TE6=
SP-32 SP-06044. - 22.101 01.3 2 Re"-= > <i3$ S#ee! 6'er4%ce (e2ee' $e
Ter5i'%" %'! $e U6++
=.0.0 =.1.0 TE6=
SP-32 SP-060320 S1-060626 22.101 01.4 - Re"-= ) +"%ri4ic%io' o' $%'!"i'3 o4
e5er3e'c8 'u5(er
=.0.0 =.1.0 TE6-=
SP-33 SP-060400 S1-060.3. 22.101 01.0 - Re"-= & +"%ri4ic%io' o' 7o5%i' Se"ecio'
4or M: %'! MT :#er%io's
=.1.0 =.2.0 TE6=
SP-33 SP-06046= S1-060.50 22.101 01.. - Re"-= & E5er3e'c8 c%""s %'! 6S6M =.1.0 =.2.0 EM+1
SP-33 SP-060402 S1-060.64 22.101 0200 - Re"-= > Re;uire5e's 4or $e
!eer5i'%io' o4 ce"" c%#%(i"i8
us%3e - 2$e' re;uese! (8 +*
=.1.0 =.2.0 TE6=
SP-34 SP-060000 S1-061321 22.101 01.5 3 Re"-= + Re;uire5e's 4or $e %!!iio' o4 %
!%% co5#o'e' o TS12
e5er3e'c8 c%""s %'! e+%"" MS7
(!%%) r%'s4er re;uire5e's
=.2.0 =.3.0 TEM+7
SP-34 SP-060003 S1-061406 22.101 0201 - Re"-= > Servi'3 E'viro'5e' 1 Mo(i"e
Viru%" *e2or9 6!e'i4ic%io'
=.2.0 =.3.0 TE6=
SP-34 SP-060065 S1-061340 22.101 0204 - Re"-= & Re5ov%" o4 6MS e5er3e'c8 c%""
i!e'i4ier
=.2.0 =.3.0 EM+1
SP-35 SP-000130 S1-0001.0 22.101 0205 1 Re"-= 7 &!!iio' o4 Evo"ve! 3GPP S8se5
!escri#io' %'! correcio's o
re4ere'ces
=.3.0 =.4.0 S&E-R
SP-35 SP-000134 S1-0002.. 22.101 0200 1 Re"-= > Re3isr%io' i' 7e'se"8-#o#u"%e!
%re%
=.3.0 =.4.0 RE7
SP-36 SP-000355 S1-000603 22.101 0211 1 Re"-= + Gr%#$ic 4or5% o4 PLM* '%5e =.4.0 =.5.0 TE6=
SP-36 SP-000354 S1-000=02 22.101 0214 1 Re"-= & &"i3'5e' o4 SP76 !e4i'iio'
(e2ee' TS22.101 %'! TS31.102
=.4.0 =.5.0 TE65
SP-36 SP-000402 S1-0000.0 22.101 0215 2 Re"-= ) +orrecio' o4 $e (%c92%r!
co5#%i(i"i8 re;uire5e' 4or $e
<SP i'er4%ce
=.4.0 =.5.0 TE6-=
SP-30 SP-000661 S1-001314 22.101 21= 2 Re"-= > 6+S Re;uire5e's L Ge'er%" =.5.0 =.6.0 6+S-R&
SP-30 SP-000661 S1-001315 22.101 221 2 Re"-= > 6+S Re;uire5e's - Service
+o'sise'c8
=.5.0 =.6.0 6+S-R&
SP-30 SP-000661 S1-001316 22.101 222 2 Re"-= > 6+S Re;uire5e's - Service
+o'i'ui8
=.5.0 =.6.0 6+S-R&
SP-30 SP-000661 S1-001310 22.101 225 2 Re"-= > 6+S Re;uire5e's - 6MS Services =.5.0 =.6.0 6+S-R&
SP-30 SP-000662 S1-000..5 22.101 216 1 Re"-= + +"%ri4ic%io' o' 3r%#$ic 4or5% o4
PLM* '%5e
=.5.0 =.6.0 TE6=
SP-30 SP-000606 - 22.101 210 4 Re"-= > Re;uire5e's 4or e+%"" =.5.0 =.6.0 E7%%
SP-3= SP-000=50 S1-001012 22.101 0232 1 Re"-= > 6+S - +"%ri4ic%io' o4 Service
+o'i'ui8
=.6.0 =.0.0 6+SR&
SP-3= SP-000=50 S1-001013 22.101 0233 1 Re"-= > 6+S - Service +o'i'ui8
Re;uire5e's
=.6.0 =.0.0 6+SR&
SP-3= SP-000=50 S1-001014 22.101 0234 1 Re"-= > 6+S - Ro%5i'3 Su##or =.6.0 =.0.0 6+SR&
SP-3= SP-000=50 S1-001015 22.101 0235 1 Re"-= > +"%ri48 UE re;uire5e's 4or 6+S =.6.0 =.0.0 6+S-R&
SP-3= SP-000=61 S1-001.32 22.101 022. 2 Re"-= > Re;uire5e's 4or E5er3e'c8
+%""->%c9
=.6.0 =.0.0 TE6=
SP-3= SP-000=62 S1-001.20 22.101 0241 2 Re"-= > +S 6P 6'erco''ecio'
re;uire5e'
=.6.0 =.0.0 6P6*TER+
SP-3. SP-0=0036 S1-0=030. 22.101 0230 6 Re"-= > Re;uire5e's 4or @6' +%se o4
E5er3e'c8@ (6+E) i'4or5%io'
=.0.0 =.=.0 6+E
SP-3. SP-0=0042 S1-0=02.6 22.101 0250 1 Re"-= ) U#!%e $e re"%e! co'e's %(ou
@Evo"ve! P%c9e S8se5@
=.0.0 =.=.0 &6P*-S&E
SP-3. SP-0=0041 S1-0=02.0 22.101 0251 1 Re"-= ) +S 5u"i5e!i% c%""s =.0.0 =.=.0 TE6=
SP-3. SP-0=0041 S1-0=02.= 22.101 0252 1 Re"-= 7 correcio' o4 2ro'3 re4ere'ci'3 =.0.0 =.=.0 TE6=
SP-3. SP-0=0032 S1-0=0314 22.101 0253 2 Re"-= > Re;uire5e's 4or r%'s4er 4or !%%
!uri'3 e5er3e'c8 c%""s
=.0.0 =.=.0 E7%%
SP-3. SP-0=0032 S1-0=0266 22.101 0254 1 Re"-= > Re;uire5e's 4or $e r%'s4er o4
e+%"" Mi'i5u5 Se o4 7%%
=.0.0 =.=.0 E7%%
SP-3. SP-0=0043 S1-0=0330 22.101 0255 2 Re"-= > R&T i'!ic%or =.0.0 =.=.0 TE6=
SP-3. SP-0=003. S1-0=02=0 22.101 0256 1 Re"-= > 6+S re;uire5e' 4or ro%5i'3 =.0.0 =.=.0 6+SR&
SP-3. SP-0=0040 S1-0=0230 22.101 0262 1 Re"-= > &!!iio'%" re;uire5e's 4or +S 6P
i'erco''ecio'
=.0.0 =.=.0 6P6*TER+
SP-3. SP-0=0043 S1-0=02.. 22.101 0263 1 Re"-= > &!!iio' o4 U'i;ue 7evice
6!e'i4ier o +%""i'3 Li'e
=.0.0 =.=.0 TE6=
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '$ Release 12
!an"e !istor#
6!e'i4ic%io'
SP-3. SP-0=0040 S1-0=0320 22.101 0265 1 Re"-= > +"%ri4ic%io' o4 re;uire5e's 4or
+S 6P i'erco''ecio'
=.0.0 =.=.0 6P6*TER+
SP-40 SP-0=030= S1-0=0046 22.101 0260 3 Re"-= ) E5er3e'c8 +%"" 6'er%cio' =.=.0 =...0 EM+1
SP-40 SP-0=02.. S1-0=05=1 22.101 026. 1 Re"-= + e+%"" c%"" (%c9 re;uire5e's
c"%ri4ic%io'
=.=.0 =...0 E7&T&
SP-40 SP-0=02.= S1-0=0035 22.101 0200 3 Re"-= ) +o55o' 6MS Pro#os%"s -
Re;uire5e's 4or E5er3e'c8
+%""s
=.=.0 =...0 +6MSK3G
PP2
SP-40 SP-0=0306 S1-0=0015 22.101 0201 1 Re"-= ) +orrecio' o4 re4ere'ce 4or PLM*
%rc$iecure
=.=.0 =...0 &6P*-S&E
SP-40 SP-0=02.. S1-0=0014 22.101 0202 1 Re"-= ) +orrecio's o 3e'er%"
re;uire5e's 4or e5er3e'c8 c%""s
=.=.0 =...0 E7%%
SP-40 SP-0=030= S1-0=0560 22.101 0204 - Re"-= ) +"%ri4ic%io' o4 6MS E5er3e'c8
+%""s
=.=.0 =...0 EM+1
SP-40 SP-0=02.. S1-0=0043 22.101 0205 1 Re"-= + Reco'4i3ur%("e e+%"" o'"8 er5i'%"
%ccess o es %'! reco'4i3ur%io'
services
=.=.0 =...0 E7&T&
SP-40 SP-0=0302 S1-0=0005 22.101 0206 - Re"-= ) +orrecio' o4 6+E re;uire5e's =.=.0 =...0 6+E
SP-40 SP-0=0311 S1-0=0004 22.101 026= 3 Re"-. > Re;uire5e's 4or Service
&"i3'5e' %'! Mi3r%io'
=.=.0 ..0.0 ET?S-S1
SP-41 SP-0=04.= S1-0=21.2 22.101 02=2 1 Re"-. ) +"%ri4ic%io' o' 6MS services
su##ore! (8 6+S
..0.0 ..1.0 6+SR&
SP-41 SP-0=0643 - 22.101 02=0 2 Re"-. ) RE7 o#i5iD%io' o4 "oc%io'
u#!%e
..0.0 ..1.0 RE7
SP-42 SP-0=0==4 22.101 02.0 6 Re"-. & 6+S Service +o'i'ui8 ..1.0 ..2.0 +6MS=
SP-42 SP-0=000. S1-0=4415 22.101 2=1 2 Re"-. > User 7%% +o'ver3e'ce
Re;uire5e's
..1.0 ..2.0 U7+
SP-42 SP-0=00=1 S1-0=4100 22.101 02=3 2 Re"-. ) V++ 4or e5er3e'c8 c%""s ..1.0 ..2.0 6MSKEME
RKGPRSK
EPS
SP-42 SP-0=00=4 S1-0=4424 22.101 02.0 3 Re"-. + 6+S Service +o'i'ui8 ..1.0 ..2.0 TE6.
SP-42 SP-0=00=3 S1-0=4404 22.101 02.. 3 Re"-. > U6++ %##"ic%io's %ccess o 6MS ..1.0 ..2.0 TE6.
SP-42 SP-0=00=1 S1-0=40.6 22.101 300 - Re"-. ) M%9e 6MS e5er3e'c8 c%""s
%v%i"%("e i' %"" %ccess s8se5s
..1.0 ..2.0 TE6.
SP-43 SP-0.000. S1-0.0104 22.101 0300 1 Re"-. & +"%ri4ic%io' %'! e'$%'ce5e' o4
ci#$eri'3 i'!ic%or 4e%ure
..2.0 ..3.0 TE6.
SP-44 SP-0.0300 S1-0.1400 22.101 0312 4 Re"-. ) 7o5%i' se"ecio' 4or e5er3e'c8
c%""
..3.0 ..4.0 6MSKEME
RKGPRSK
EPS
SP-44 SP-0.036. S1-0.13.3 22.101 0313 - Re"-. & e+%"" - PS&P %c9'o2"e!3e5e'
o $e 6VS
..3.0 ..4.0 E!%%
SP-45 SP-0.0405 S1-0.32.0 22.101 0315 1 Re"-. & Mi'i5ise !e"%8 o e5er3e'c8
voice c%""s
..4.0 ..5.0 E7&T&
SP-45 SP-0.04=0 S1-0.32=2 22.101 321 1 Re"-. ) 7o5%i' se"ecio' 4or e5er3e'c8
c%""
..4.0 ..5.0 6MSKEME
RKGPRSK
EPS
SP-45 SP-0.04=3 S1-0.32=6 22.101 0316 1 Re"-10 ) &!! re4ere'ce o MS7
s#eci4ic%io'
..4.0 10.0.0 E7&T&
SP-45 SP-0.04=4 S1-0.3341 22.101 0320 4 Re"-10 > Se"ece! 6P Tr%44ic :44"o%! ..4.0 10.0.0 L6P&KS6PT
:
SP-45 SP-0.04=3 S1-0.3261 22.101 322 1 Re"-10 ) +"%ri4ic%io' o4 e5er3e'c8 c%""
(%c9 re;uire5e's
..4.0 10.0.0 TE610
SP-46 SP-0.0==0 S1-0.425. 22.101 0336 1 Re"-10 & Provi!i'3 e+%"" i'!ic%io' o $e
PS&P
10.0.0 10.1.0 E7&T&
SP-46 SP-0.0=36 S1-0.4262 22.101 033= - Re"-10 & Re5ove re;uire5e' 4or o#er%or
!eer5i'e! e+%"" c%""-(%c9
!ur%io'.
10.0.0 10.1.0 E7&T&
SP-46 SP-0.0=42 S1-0.4202 22.101 0330 1 Re"-10 & User !%% re#osior8 s$%"" (e
#ossi("e o (e s$%re! %5o'3
!i44ere' PLM*s $% $%ve ruse!
re"%io's$i#s
10.0.0 10.1.0 U7+
SP-46 SP-0.0=44 S1-0.44.. 22.101 0320 2 Re"-10 & Use o4 GTT-6P 4or 6MS
e5er3e'c8 c%""s (5irror)
10.0.0 10.1.0 TE6.
SP-46 SP-0.0=46 S1-0.44.6 22.101 032= 1 Re"-10 > 6+S E'$%'ce5e's 10.0.0 10.1.0 TE610
SP-46 SP-0.0=4. S1-0.4300 22.101 0325 3 Re"-10 > Ro%5i'3 %'! Mo(i"i8 %s#ecs 4or
Se"ece! 6P Tr%44ic :44"o%!
10.0.0 10.1.0 L6P&KS6PT
:
SP-40 SP-1001=0 S1-100321 22.101 033. 2 Re"-10 > S6PT: re;uire5e's co55o' 4or
5%cro 'e2or9 %'! <(e)*>
su(s8se5s
10.1.0 10.2.0 L6P&KS6PT
:
SP-40 SP-1001== S1-100445 22.101 0332 6 Re"-10 + +"%ri4ic%io' o E5er3e'c8 c%""
se"ecio' #rioriiD%io'
10.1.0 10.2.0 TE610
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '& Release 12
!an"e !istor#
SP-40 SP-1001== S1-100442 22.101 0340 1 Re"-10 + +"%ri4ic%io' o' 6+S 2r !%% (+S)
%'! 4%/
10.1.0 10.2.0 TE610
SP-40 SP-1001.1 S1-100431 22.101 0343 2 Re"-10 > 6MS e5er3e'c8 c%""
e'$%'ce5e's
10.1.0 10.2.0 6ESE
SP-4= SP-100431 S1-101060r 22.101 0340 6 Re"-10 > &!!iio' o4 Re;uire5e' 4or U7+
7%% Mo!e"
10.2.0 10.3.0 TE610
SP-4= SP-100401 S1-101060 22.101 0350 - Re"-10 ) +orrecio' o4 re4ere'ce 10.2.0 10.3.0 6ESE
SP-4. SP-1005=5 S1-102403 22.101 0353 2 Re"-11 > S6PT: 5o(i"i81co'i'ui8 10.3.0 11.0.0
S6PT:KS
+
SP-51 SP-11016= S1-1100== 22.101 0360 - Re"-11 )
+"%ri4ic%io' o' Service +o'i'ui8
4or S6PT: 11.0.0 11.1.0
S6PT:KS
+
SP-52 SP-110303 S1-111410 22.101 0360 3 Re"-11 > 6MS e5er3e'c8 c%"" re;uire5e's
4or %!!iio'%" 5e!i% 8#es
11.1.0 11.2.0 *:VES
SP-52 SP-110306 S1-11120. 22.101 036. - Re"-11 7 Re5ovi'3 e/ !iscre#%'c8
(e2ee' Re"-10 %'! Re"-11 4or
U7+ 7%% Mo!e"
11.1.0 11.2.0 TE611
SP-52 SP-11041= - 22.101 0302 2 Re"-11 & 6MS e5er3e'c8 c%""s 11.1.0 11.2.0 6MSKEME
RKGPRSK
EPS
+orrecio' o4 8#o o' cover #%3e 11.2.0 11.2.1
SP-53 SP-1105=2 S1-1123.2 22.101 0303 1 Re"-11 ) S6PT: i' $e Mo(i"e :#er%or
*e2or9 %'! Loc%"
Resi!e'i%"1E'er#rise *e2or9
11.2.0 11.3.0 TE611
SP-53 SP-110506 S1-112101 22.101 030. - Re"-11 > 6MS e5er3e'c8 c%"" su##or 2i$
o$er 5e!i% $%'!over
co'si!er%io's
11.2.0 11.3.0 *:VES
SP-53 SP-110506 S1-112344 22.101 03=0 1 Re"-11 > *oi4ic%io' o4 6MS e5er3e'c8 c%""
su##or 2i$ o$er 5e!i%
11.2.0 11.3.0 *:VES
SP-53 SP-110506 S1-112350 22.101 03=5 3 Re"-11 > 7o5%i' Se"ecio' 4or 6MS
e5er3e'c8 c%""s 2i$ %!!iio'%"
5e!i% 8#es
11.2.1 11.3.0 *:VES
SP-53 SP-11050. S1-1123=5 22.101 0304 1 Re"-11 ) S6PT: Service +o'i'ui8 11.2.0 11.3.0 S6PT:KS
+
SP-53 SP-11050. S1-1123.3 22.101 030= 2 Re"-11 + +"%ri4ic%io' o' co""ecio' o4 r%44ic
%'! si3'%""i'3 4or S6PT:
11.2.0 11.3.0 S6PT:KS
+
SP-53 SP-1105=2 S1-112025 22.101 0306 - Re"-11 ) +orrecio' o4 c"%use 'u5(ers %'!
e!iori%" correcio's
11.2.1 11.3.0 TE611
SP-53 SP-110651 S1-11232= 22.101 03=3 3 Re"-11 ) Movi'3 @*e2or9 #rovi!e!
!esi'%io' 4or u#"i'9 !%%@
re;uire5e' 4ro5 22.36= i'o
22.101
11.2.1 11.3.0 S6MT+
SP-53 SP-110651 S1-11232. 22.101 03=4 4 Re"-11 ) Movi'3 PS-:'"8 re;uire5e's
4ro5 22.36= i'o 22.101
11.2.1 11.3.0 S6MT+
SP-54 SP-110=11 S1-113245 22.101 03=0 1 Re"-11 ) 6MS Mu"i5e!i% E5er3e'c8
Sessio' su##or 4or UEs i'
Li5ie! Service Mo!e
11.3.0 11.4.0 *:VES
SP-54 SP-110=11 S1-11324. 22.101 03== 2 Re"-11 ) +orrecio' %'! re5ov%" o4
i'co'sise'cies o 6MS
E5er3e'c8 c%"" 2$e' usi'3 o$er
5e!i%
11.3.0 11.4.0 *:VES
SP-54 SP-110=11 S1-11324= 22.101 03.0 2 Re"-11 ) 6'!ic%io' o4 su##ore! 5e!i%
!uri'3 %' 6MS 5u"i5e!i%
e5er3e'c8 sessio'
11.3.0 11.4.0 *:VES
SP-54 SP-110=11 S1-113250 22.101 03.1 1 Re"-11 ) <%'!over o4 o$er 5e!i% o
'e2or9s $% !o 'o su##or 6MS
e5er3e'c8 voice c%""s
11.3.0 11.4.0 *:VES
SP-54 SP-110=03 S1-1130.3r 22.101 03.2 2 Re"-11 ) Me!i% %""o2e! o' c%""(%c9 4ro5
PS&P
11.3.0 11.4.0 *:VES
SP-54 SP-110=11 S1-1130.4 22.101 03.3 - Re"-11 ) Roui'3 6MS 5u"i5e!i% sessio's
o2%r!s $e PS&P
11.3.0 11.4.0 *:VES
SP-54 SP-110=13 S1-1130.= 22.101 03.4 - Re"-11 > PS %!!iio'%" 'u5(er 11.3.0 11.4.0 TE611
SP-55 SP-120103 S1-120256 22.101 0401 1 Re"-11 ) PS o'"8 su(scri#io's 2i$ SMS
su##or
11.4.0 11.5.0 S6MT+
SP-55 SP-120105 S1-120346 22.101 0400 4 Re"-12 > 6'ro!ucio' o4 S5%"" 7%%
&##"ic%io's re;uire5e's
11.4.0 12.0.0 TE612
SP-56 SP-1202=6 S1-121314 22.101 040. 1 Re"-12 & E5er3e'c8 c%""s 4ro5 'o' +SG
5e5(ers i' +SG ce""s
12.0.0 12.1.0 E<*>
SP-56 SP-1202== S1-1213.6 22.101 0412 1 Re"-12 & +"%ri4ic%io' o4 PS %!!iio'%"
'u5(ers re;uire5e'
12.0.0 12.1.0 TE611
SP-56 SP-1202== S1-1213.2 22.101 0415 - Re"-12 & Mo!i4ic%io' o4 $o2 ME re%s
e5er3e'c8 c%"" 8#e(s)
12.0.0 12.1.0 TE611
SP-50 SP-12051. S1-122463 22.101 0423 1 Re"-12 & +orrecio' o4 UE 5%'!%or8
4e%ures
12.1.0 12.2.0 TE6=
SP-50 SP-12052= S1-122221 22.101 0416 3 Re"-12 > 7e4i'iio's 4or i'e3r%io' o4
Si'3"e Si3'-:' (SS:)
12.1.0 12.2.0 SS:Ki'
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '' Release 12
!an"e !istor#
4r%5e2or9s 2i$ 3GPP 'e2or9s
SP-50 SP-12052= S1-122433 22.101 0410 2 Re"-12 > Re;uire5e's 4or i'e3r%io' o4
Si'3"e Si3'-:' (SS:)
4r%5e2or9s 2i$ 3GPP 'e2or9s
12.1.0 12.2.0 SS:Ki'
SP-5= SP-120=6= S1-124504 22.101 0433 5 Re"-12 7 MS6S7*-"ess SMS <%'!"i'3 12.2.0 12.3.0 MT+e-
SRM
SP-5= SP-120.1. S1-124416 22.101 0434 4 Re"-12 > &!!iio' o4 UP+:*
Re;uire5e's
12.2.0 12.3.0 UP+:*
SP-5. SP-130106 S1-131033 22.101 0444 - Re"-12 7 +"%ri4ic%io' o4 R&* user #"%'e
co'3esio' !e4i'iio'
12.3.0 12.4.0 UP+:*
SP-5. SP-130112 S1-131226 22.101 0445 3 Re"-12 > &!! Re;uire5e' o' e5er3e'c8
6M +* su(s8se5
12.3.0 12.4.0 ES67
3GPP
3GPP TS 22!1"1 #12!$!" (2"13%"3 '( Release 12