3rd Generation Partnership Project; V12.0.

0 (2011-12) Technical Specification Group Services and System Aspects; Technical (EPS Specification Service requirements for the Evolved Packet System (!elease "#

3GPP TS 22.278

The present document has been developed within the 3rd 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 Or ani!ational Partners and shall not be implemented. This "pecification is provided for future development wor# within 3GPP only. The Or ani!ational 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 Or ani!ational Partners$ Publications Offices.

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

%eywords
UMTS, LTE, architecture

3GPP Postal address 3GPP support office address

!ute "e# Luci!$e# - S!%hia &'ti%!$i# Va$(!''e - ) &*+E Te$., -33 . /2 /. .2 00 )a0, -33 . /3 65 .7 16 650

&nternet
htt%,11222.33%%.!r3

Copyright Notification 'o part may be reproduced e(cept as authori!ed by written permission. The copyri ht and the fore oin restriction e(tend to reproduction in all media.
) *+,,- 3GPP Or ani!ational Partners (./&0- .T&"- 11".- 2T"&- TT.- TT1). .ll ri hts reserved. 3MT"4 is a Trade Mar# of 2T"& re istered for the benefit of its members 3GPP4 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners 5T24 is a Trade Mar# of 2T"& re istered for the benefit of its Members and of the 3GPP Or ani!ational Partners G"M6 and the G"M lo o are re istered and owned by the G"M .ssociation

3GPP

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

+!'te't#
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 &ntroduction...............................................................................................................................................8 , "cope......................................................................................................................................................9 * /eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................;
3., :efinitions..............................................................................................................................................................; 3.* .bbreviations.........................................................................................................................................................;

< General description ...............................................................................................................................=

<., Objectives ..............................................................................................................................................................=

8 >i h?level re@uirements A user and operational aspects.........................................................................B

8.+ General...................................................................................................................................................................B 8., /e@uirements for 7i(ed Mobile &nterwor#in .....................................................................................................,+ 8.* /e@uirements for 7i(ed Mobile 1onver ence.....................................................................................................,, 8.3 /e@uirements for &nterwor#in with :ata .pplication Providers.......................................................................,,

9 0asic capabilities .................................................................................................................................,*

9., "upport of &P traffic.............................................................................................................................................,* 9.,., "upport of increased &P traffic demand.............................................................................................................,* 9.,.* Coid ,* 9.,.3 Coid ,* 9.,.< "upport of basic &P connectivity.......................................................................................................................,* 9.,.8 "upport of &P multicast service........................................................................................................................,* 9.* &P session control.................................................................................................................................................,* 9.3 Duality of "ervice................................................................................................................................................,< 9.< "upport of Multicast and 0roadcast "ervices......................................................................................................,8 9.8 "upport of 2mer ency 1alls................................................................................................................................,8

; Multi?access and seamless mobility....................................................................................................,9

;., Mobility mana ement..........................................................................................................................................,9 ;.,., >etero eneous access systems mobility...........................................................................................................,9 ;.,.* 5ocal brea#out...................................................................................................................................................,9 ;.,.3 7i(ed .ccess "ystems.......................................................................................................................................,; ;.,.< "ervice continuity..............................................................................................................................................,; ;.,.<., General ,; ;.,.<.* "ervice continuity at domain and /.T chan e for T" ,,- T" ,* and e@uivalent P" service......................,; ;.,.<.*. Coice 1all "ervice continuity between 3GPP defined /.Ts and non 3GPP defined /.Ts................,= ;.,.<.3 "ervice continuity between 2?3T/.' and 3GPP* accesses on 2volved Pac#et 1ore................................,= ;.,.<.< "ervice continuity between 3GPP and EiM.F access on 2volved Pac#et 1ore.........................................,= ;.,.8 .ccess networ# discovery................................................................................................................................,= ;.,.9 "teerin of access..............................................................................................................................................,B ;.,.; 1" fallbac#........................................................................................................................................................,B ;.,.;., General ,B ;.,.;.* /oamin in a CP5M' not supportin 1" fallbac#.......................................................................................,B

;.* &7OM "ervice re@uirements..............................................................................................................*+ = Performance re@uirements for the 2volved Pac#et "ystem..................................................................*+ B "ecurity and privacy............................................................................................................................**
B., General.................................................................................................................................................................** B.* "ecurity re@uirements...........................................................................................................................................** B.3 Privacy re@uirements............................................................................................................................................**

3GPP

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

,+ 1har in .spects...............................................................................................................................*3 Annex A (informative): Requirements for further study...........................................................24

.., Mana ement of access networ#s.........................................................................................................................*< ..* 3se cases for 7i(ed Mobile 1onver ence...........................................................................................................*<

Annex B (Normative): Evolved Pa !et "ystem (EP") a##li a$le s#e ifi ations.....................2%
0., 2P" .pplicable "pecifications ...........................................................................................................................*9

Annex B& ('nformative): 'nter(or!in) $et(een *o$ile +#erators and ,ata A##li ation Providers................................................................................................20,., "cenarios............................................................................................................................................................*; 0,.* 3se cases ..........................................................................................................................................................*B 0,.*., 3se cases for owned G collaborated scenarios................................................................................................*B 0,.*.* 3se cases for non?collaborated scenarios......................................................................................................3+ 0,.*.*., 32 initiates and re@uests M'O for preferential traffic handlin ................................................................3+ 0,.*.*.* 32 initiates and :ata .pplication Provider re@uests M'O for preferential traffic handlin .....................3,

Annex . (informative): .han)e history....................................................................................../2

3GPP

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

)!re2!r"
This Technical "pecification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuin wor# within the T"G and may chan e 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 chan e of release date and an increase in version number as followsH Cersion (.y.! whereH ( the first di itH , presented to T"G for informationI * presented to T"G for approvalI 3 or reater indicates T"G approved document under chan e control. y the second di it is incremented for all chan es of substance- i.e. technical enhancements- correctionsupdates- etc. ! the third di it is incremented when editorial only chan es have been incorporated in the document.

4'tr!"ucti!'
To ensure competitiveness in a lon er time frame an evolution of the overall 3GPP system needs to be considered. This document compiles re@uirements to ensure that an 2volved Pac#et "ystem can cope with the rapid rowth in &P data traffic and demandin re@uirements for new multimedia type of applications in terms of performance and @ualitydelivered to the user- whilst at the same time enablin cost effective deployment and operation. The 2volved Pac#et "ystem is characterised byH ? ? ? ? /educed latency >i her user data rates e@uatin to broadband performance &mproved system capacity and covera e 5ower operational costs

3GPP

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

Sc!%e

The present document describes the service re@uirements for the 2volved Pac#et "ystem. .dditional re@uirements for 2?3T/.' are contained in the specifications identified in anne( 0.

e5ere'ce#
/eferences are either specific (identified by date of publication- edition number- version number- etc.) or non?specific. 7or a specific reference- subse@uent revisions do not apply. 7or a non?specific reference- the latest version applies. &n the case of a reference to a 3GPP document (includin a G"M document)- a non?specific reference implicitly refers to the latest version of that document in the same Release as the present document. J,K J*K J3K J<K J8K J9K 3GPP T" **.++3H L1ircuit Teleservices supported by a Public 5and Mobile 'etwor# (P5M')L. 3GPP T" *,.B+8H LCocabulary for 3GPP specificationsL. 3GPP T" **.*8=H L"ervice /e@uirements for the .ll?&P 'etwor# (.&P')I "ta e,L. 3GPP T/ *8.B,3H L/e@uirements for 2volved 3T/. (2?3T/.) and 2volved 3T/.' (2? 3T/.')L. 3GPP T" **.,,8H L"ervice aspectsI 1har in and billin L. 2T"& T" ,+* *8+?,H L"peech Processin - Transmission and Duality .spects ("TD)I Do" aspects for popular services in G"M and 3G networ#sH Part ,H &dentification of Duality of "ervice aspectsL. 3GPP T/ *3.==*H L3GPP system architecture evolution (".2)H /eport on technical options and conclusionsL. 1."+++,?. 1."+++*?. &ntroduction to cdma*+++ "tandards for "pread "pectrum "ystems ? /elease .. Physical 5ayer "tandard for cdma*+++ "pread "pectrum "ystems ? /elease ..

The followin documents contain provisions which- throu h reference in this te(t- constitute provisions of the present document.

J;K J=K JBK J,+K J,,K J,*K J,3K J,<K J,8K J,9K J,;K J,=K

1."+++3?. Medium .ccess 1ontrol (M.1) "tandard for cdma*+++ "pread "pectrum "ystems ? /elease . addendum *. 1."+++<?. "i nalin 5in# .ccess 1ontrol (5.1) "pecification for cdma*+++ "pread "pectrum "ystems ?.ddendum *. 1."+++8?. 3pper 5ayer (5ayer 3) "i nalin "tandard for cdma*+++ "pread "pectrum "ystems ? /elease . addendum *. 1."+++9?. .nalo "i nalin "tandard for cdma*+++ "pread "pectrum "ystems ? .ddendum *.

.."+++; A .."+++B &nteroperability "pecification (&O") for >i h /ate Pac#et :ata (>/P:). .."++,, A .."++,; &nteroperability "pecification (&O") for cdma*+++ .ccess 'etwor# &nterfaces. F."++,, cdma*+++ Eireless &P 'etwor#. 1."++*<?. cdma*+++ >i h /ate Pac#et :ata .ir &nterface "pecification. 1."++*<?+ cdma*+++ >i h /ate Pac#et :ata .ir &nterface "pecification.

3GPP

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

J,BK J*+K J*,K J**K J*3K J*<K J*8K J*9K J*;K J*=K

Coid. EiM.F 7orum Mobile "ystem Profile- /elease ,.+ . 3GPP T" **.,+,H L"ervice .spectsI "ervice PrinciplesL. L/ecommendations and /e@uirements for 'etwor#s based on EiM.F 7orum 1ertifiedTM ProductsL (EiM.F sta e ,) LEiM.F 7orum 'etwor# .rchitecture ("ta e *H .rchitecture Tenets- /eference Model and /eference Points)L LEiM.F 7orum 'etwor# .rchitecture ("ta e 3H :etailed Protocols and Procedures)L Coid. "./++<=?. 3G Mobile 2@uipment &dentifier (M2&:) 007 T/?,<< ? 0roadband Multi?"ervice .rchitecture M 7ramewor# /e@uirements 007 Technical /eport T/?,*9 ? Triple?play "ervices Duality of 2(perience (Do2) /e@uirements

6e5i'iti!'# a'" a((re7iati!'#

3.1 6e5i'iti!'#
7or the purposes of the present document- the terms and definitions iven in T/ *,.B+8 J*K and the followin apply. Evolved Pa !et "ystem: is an evolution of the 3G 3MT" characteri!ed by hi her?data?rate- lower?latency- pac#et? optimi!ed system that supports multiple /.Ts. The 2volved Pac#et "ystem comprises the 2volved Pac#et 1ore to ether with the evolved radio access networ# (2?3T/. and 2?3T/.'). "ervi e .ontinuity: The uninterrupted user e(perience of a service that is usin an active communication (e. . an on oin voice call) when a 32 under oes a radio access technolo y chan e or a 1"GP" domain chan e without- as far as possible- the user noticin the chan e. 'oteH &n particular "ervice 1ontinuity encompasses the possibility that after a /.T G domain chan e the user e(perience is maintained by a different telecommunication service (e. . tele? or bearer service) than before the /.T G domain chan e.

3.2 &((re7iati!'#
7or the purposes of the present document- the abbreviations iven in T/ *,.B+8 J*K and the followin apply. '/T /T 'on /eal Time /eal Time

3GPP

!elease "#

&

3GPP TS ##$#%& '"#$($( (#("")"#

Ge'era$ "e#cri%ti!'

..1 8(9ecti7e#
The 2volved Pac#et "ystem is a hi her?data?rate- lower?latency- pac#et?optimi!ed system that supports multiple /.Ts. The focus of the 2volved Pac#et "ystem wor# is on enhancement of Pac#et "witched technolo y to cope with rapid rowth in &P traffic. The objectives of the 2volved Pac#et "ystem are toH ? ? ? ? ? Provide hi her data rates- lower latency- hi h level of security and enhanced Do"I "upport a variety of different access systems (e(istin and future)- ensurin mobility and service continuity between these access systemsI "upport access system selection based on a combination of operator policies- user preference and access networ# conditionsI /ealise improvements in basic system performance whilst maintainin the ne otiated Do" across the whole systemI Provide capabilities for co?e(istence with le acy systems and mi ration to the 2volved Pac#et "ystem.

3GPP

!elease "#

3GPP TS ##$#%& '"#$($( (#("")"#

:i3h-$e7e$ re;uire<e't# = u#er a'" !%erati!'a$ a#%ect#

5.0 Ge'era$
The 2volved Pac#et "ystem shall be capable of accommodatin a variety of different access systems thus providin a multi?access system environment to the user. The 2volved Pac#et "ystem shall provide mobility functionality within and across the different access systems. The 2volved Pac#et "ystem shall provide capabilities to support the efficient inte ration of 2?3T/.' P" 1ore 'etwor# 'odes and G2/.'G3T/.' P" 1ore 'etwor# 'odes. The 2volved Pac#et "ystem shall optimi!e mobility functionality meanin that it shall offer minimal si nallin overhead- minimal handover interruption time- secure handover procedure and local brea#out. The 2volved Pac#et "ystem shall provide capabilities to inter?wor# with a variety of broadband networ#s based on &P technolo ies includin those not specified by 3GPP. The 2volved Pac#et "ystem may provide capabilities to allow users to access all P5M' &P?based services via non? 3GPP access technolo ies outside the operator$s domain- under conditions where there are traffic restrictions (e. . only >TTP allowed). &n this case- service reachability shall maintain pre?e(istin 2P" security. The 2volved Pac#et "ystem shall provide enhanced performance e. .- low communication delay- low connection set?up time and hi h communication @uality. The 2volved Pac#et "ystem shall be able to efficiently support a variety of traffic models e. . user?to?user- user?to? roup and traffic models enerated by ubi@uitous services. The 2volved Pac#et "ystem shall provide functionality to support outbound roamin subscribers on other 2volved Pac#et "ystems and le acy networ#s. The 2volved Pac#et "ystem shall provide functionality to support inbound roamin subscribers from other 2volved Pac#et "ystems and le acy networ#s. The 2volved Pac#et "ystem shall be capable of supportin and inter?wor#in with P" services provided on /el?; and earlier networ#s. The 2volved Pac#et "ystem shall be capable of inter?wor#in with 1" services provided on /el?; and earlier networ#s. The 2volved Pac#et "ystem shall support service continuity between 3GPP access systems and also between 3GPP access systems and non 3GPP access systems whether the 32 supports simultaneous radio transmission or not. The 2volved Pac#et "ystem shall be able to accommodate fi(ed access systems and to inter?wor# with fi(ed networ#s in order to provide service continuity over fi(edGmobile conver ed networ#s. The 2volved Pac#et "ystem service capability set shall include- as a minimum- support for the followin cate ories of services that are li#ely to be used by the majority of operatorsH ? ? ? ? Coice Cideo Messa in :ata file e(chan e

The 2volved Pac#et "ystem shall provide for efficient usa e of system resources- especially of radio resources throu h both si nallin and transport optimi!ation- e. . overhead- terminal power- radio resources- mobility state- si nallin load.

3GPP

!elease "#

"(

3GPP TS ##$#%& '"#$($( (#("")"#

The 2volved Pac#et "ystem shall support efficient delivery of te(t?based broadcast messa es received from a le acy 101. The 2volved Pac#et "ystem shall support 2?3T/.' only operators. The system shall allow these operators to offer national roamin to their subscribers. The 2volved Pac#et "ystem shall be capable of uni@uely identifyin each device that connects via 3GPP access networ#s and 3GPP* access networ#s. 7or a dual mode device supportin both 3GPP and 3GPP* access technolo iesthere shall be a sin le persistent identifier used to identify the device. This device identifier shall be the same even when the device moves between 3GPP and 3GPP* access types. 'oteH The 3GPP* device identifier structure is consistent with the &M2& structure J*9K. The 2P1 shall be capable of restrictin access of specific 3GPP devices- 3GPP* devices and dual mode 3GPPG3GPP* devices.

5.1

e;uire<e't# 5!r )i0e" M!(i$e 4'ter2!r>i'3

The 2volved Pac#et "ystem shall support the followin scenariosH a sin le Operator offerin both fi(ed and mobile accessI different Operators collaboratin to deliver services across both networ#s. These scenarios will be supported by interwor#in between the access networ#s. The 2volved Pac#et "ystem shall support access to services on the mobile networ# via interwor#in with a fi(ed access networ# for the followin scenariosH ? ? ? /esidential scenarios for operators that own both wireless and wireline access networ#s /esidential scenarios for operators that own wireless access networ#s only 2nterprise scenarios with mana ed connectivity between mobile operators and enterprise networ#s

The 2volved Pac#et "ystem shall be able to support the followin functions for interwor#in between the fi(ed access in the above scenarios and 2volved Pac#et 1oreH ? ? ? ? ? ? connectivitysubscriber authenticationGauthori!ationoffline char in online char in for traffic routed via the 2volved Pac#et 1ore Policy 1ontrol and Duality of "ervice.

The 2volved Pac#et 1ore shall support the followin for fi(ed accessH ? ? ? policy mana ementauthentication for E5.' terminals and fi(ed deviceschar in

The 2P" shall be capable to set operator policies to support simultaneous access to P5M' services and traffic offloadin to the fi(ed networ#. &nterwor#in shall support the followin scenariosH Ehen traffic is routed via 2P1 ? ? Ehen >(e)'0 is bein used and traffic is offloaded in the local wireline networ# Ehen E5.' is bein used and traffic is offloaded in the local wireline networ# (i.e. non?seamless E5.' offloadin )

3GPP

!elease "#

""

3GPP TS ##$#%& '"#$($( (#("")"#

.dditionally the 2volved Pac#et "ystem shall be ableH ? ? ? to minimi!e Do" and Policy mana ement si nallin overhead while interwor#in between the fi(ed access and 2volved Pac#et 1ore. to route different simultaneously active P:' connections throu h different accesses while interwor#in between the fi(ed access and 2volved Pac#et 1ore. to route different &P flows belon in to the same P:' connection throu h different accesses while interwor#in between the fi(ed access and 2volved Pac#et 1ore.

The re@uirements for mobility in chapter ;.,.3 apply also to interwor#in between the fi(ed access and 2volved Pac#et 1ore.

5.2

e;uire<e't# 5!r )i0e" M!(i$e +!'7er3e'ce

The 2volved Pac#et "ystem shall be able to accommodate fi(ed access systems to provide services over a conver ed networ# supportin both fi(ed and mobile accesses. The 2volved Pac#et "ystem shall support common functions (e. . for policy mana ement- accountin ) when a sin le operator operates both fi(ed and mobile accesses. The 2volved Pac#et "ystem shall be capable of providin an e@uivalent e(perience to users consumin conver ed services on different accesses- subject to different accesses capabilities. The 2volved Pac#et "ystem shall provide the followin - while providin conver ed servicesH ? ? ? ? common operational and mana ement procedurescommon subscriber profilescommon services profilescommon char in procedures (e. . a common post?paid bill).

The 2volved Pac#et "ystem should optimi!e Do" and Policy mana ement. The re@uirements for mobility in clause ;.,.3 of this specification also apply to a conver ed networ# supportin both fi(ed and mobile accesses. The 2volved Pac#et "ystem shall support re@uests for allocation and enforcement of Do" for layer * and layer 3 in fi(ed broadband networ#s as defined in J*;K. The 2volved Pac#et "ystem shall support operator networ# policies for application sessions to re@uest Do" in fi(ed broadband networ#s as defined in J*;K. The 2volved Pac#et "ystem shall support user re@uests for authori!ation of Do" for application sessions in fi(ed broadband access networ# as defined in J*;K. The 2volved Pac#et "ystem shall support policy mana ement for Do" attributes of fi(ed broadband access networ# services (e. . voice- CP'- &PTC) as defined in J*=K. The 2volved Pac#et "ystem shall support policy mana ement for unicast and multicast traffic for fi(ed devices and &PTC services in fi(ed broadband access networ# as defined in J*;K.

5.3

e;uire<e't# 5!r 4'ter2!r>i'3 2ith 6ata &%%$icati!' Pr!7i"er#

The 2volved Pac#et "ystem shall support the followin interwor#in scenarios between a mobile operator and data application providersH ? ? "cenario N,H accessG&P connectivity and non?&M"Gnon?O". based data applications provided by the same mobile operator "cenario N*H collaboration between mobile operator providin accessG&P connectivity and non?&M"Gnon?O". based data applications provided by 3rd party providers

3GPP

!elease "#

"#

3GPP TS ##$#%& '"#$($( (#("")"#

"cenario N3H no collaboration between mobile operator providin accessG&P connectivity and non?&M"Gnon?O". based data applications provided by 3rd party providers

The 2volved Pac#et "ystem shall support all scenarios in non?roamin and roamin confi urations. The 2volved Pac#et "ystem shall support all scenarios for home routed and local brea#out roamin traffic e(cept for authentication and authori!ation as identified below. 7or scenarioN*- the 2volved Pac#et "ystem shall enable 3rd party data applications to rely on security derived from the security provided by the operator. 7or scenarioN*- the 2volved Pac#et "ystem shall support authori!ation and allocation of resources on 3GPP accesses for 3rd party data applications. The home networ# performs authentication and authorisation in the local?brea#out roamin scenario. The 2volved Pac#et "ystem shall support policy control interactions between a mobile operator and data applications for all scenarios tri ered by application layer si nallin or by user plane traffic. 7or scenario N3- the 2volved Pac#et "ystem shall support 32 initiated re@uests for prioritised traffic handlin throu h authorisation and allocation of resources on 3GPP access for 3rd party data applications. The 2volved Pac#et "ystem shall revert to normal traffic handlin if the re@uest is not confirmed by the 32 within a specified preview period. The 2volved Pac#et "ystem shall support online and offline char in models (e. .- user pays- application provider paysetc.) for all scenarios.

?a#ic ca%a(i$itie#

6.1 Su%%!rt !5 4P tra55ic

6.1.1 Su%%!rt !5 i'crea#e" 4P tra55ic "e<a'"
The 2volved Pac#et "ystem shall be able to provide uaranteed Do" for services and use the resources of the 2volved Pac#et "ystem with hi h efficiency i.e. ensure that @uality conditions for a particular communication are fulfilled without deterioration between the communicatin end?points.

6.1.2 V!i" 6.1.3 V!i" 6.1.. Su%%!rt !5 (a#ic 4P c!''ecti7it@

7ollowin re istration on the networ#- the 2volved Pac#et "ystem shall maintain an &P connectivity with the 32. 7ollowin re istration it shall be possible for an 32 to send and receive &P pac#ets.

6.1.5 Su%%!rt !5 4P <u$tica#t #er7ice

The 2volved Pac#et "ystem shall support &P multicast service.

6.2 4P #e##i!' c!'tr!$

The 2volved Pac#et "ystem shall provide for session mobility and session adaptation to terminal capabilities- user preferences- subscriber priorities- networ# conditions andGor other operator?defined criteria. "ession adaptation shall be under the control of the operator.

3GPP

!elease "#

"3

3GPP TS ##$#%& '"#$($( (#("")"#

The 2volved Pac#et "ystem shall support session control for multi?party sessions (e. . user?to? roup) and shall provide a scaleable solution. &n order to support the efficient routin of &P traffic- local brea#out (see "ection ;.,.*) shall be supported. The 2volved Pac#et "ystem shall support a 32 havin simultaneously more than one active P:' connections e(chan in traffic with more than one peer (e(ternal networ# or other 32)- when the networ# policies and user subscription allow it. &f a 32 is under the covera e of 3GPP access and one or more non?3GPP accesses- it shall be possible for the 32 to communicate usin multiple accesses simultaneously. The 2volved Pac#et "ystem shall provide the system operator with the means to control the number of simultaneously active P:' connections and combinations thereof to and from a 32. . sin le application runnin on the 32 shall not be re@uired to send and receive traffic throu h multiple P:'s.

3GPP

!elease "#

"*

3GPP TS ##$#%& '"#$($( (#("")"#

6.3 Aua$it@ !5 Ser7ice

The 2volved Pac#et "ystem shall have the ability to provide a @uality of service e@ual to or better than the Do" re@uirements specified for G"M and 3MT". Duality of "ervice from the customer$s perspective is to be considered in phases as specified in 2T"& T" ,+* *8+?,J9K.

.i/ure #0 Phases of service use from customer1s point of vie2 7i ure * shows the different phases (Duality of "ervice aspects) durin service use from the customer$s point of view. The meanin of these Do" aspects areH ,) Net(or! A ess: The networ# indication on the display of the mobile is a si nal to the customer that he can use the service of this networ# operator (or any other means to indicate to the user that a networ# is available). *) "ervi e A ess: &f the customer wants to use a service- the networ# operator should provide him as fast as possible access to the service. 3) "ervi e 'nte)rity: This describes the Duality of "ervice durin service use. <) "ervi e Retaina$ility: "ervice /etainability describes the termination of services (in accordance with or a ainst the will of the user). &n particular the 2volved Pac#et "ystem shall provide for the followin H ? There should be no perceptible deterioration of audio @uality of a voice call durin and followin handover between dissimilar 1" and P" access networ#s- and transitions between P" access networ#s supportin different &P protocol versions. There should be no loss of data- as a result of handovers between dissimilar fi(ed and mobile access systemsincludin those that support different versions of the &P protocol. There should be no discernable difference in perceived service @uality for users receivin services via unicast and users receivin the same service via multicast. The 2volved Pac#et "ystem shall support Do" differentiations for unicast bearers. The 2volved Pac#et "ystem shall support Do" bac#wards compatibility to earlier 3GPP Do" releases. &t shall be possible for the 2volved Pac#et "ystem to maintain end?to?end Do" without modification when the terminal moves from one access system to a new access system- and the new access system supports the re@uired Do". &t shall be possible for the 2volved Pac#et "ystem to chan e Do"- when the terminal moves from one access system to a new access system and the new access system can not provide the same Do" as the old access system or the new access system can provide hi her Do". &t shall be possible for the 2volved Pac#et "ystem to support service continuity for a terminal chan in access system and the new access system cannot provide the same Do" as the old one. The 2volved Pac#et "ystem shall support transport Do" differentiations for multicast bearers. &t shall be possible for the 2volved Pac#et "ystem to maintain Do" within a multicast session without Do" chan es for other members of the session when a terminal joins or leaves the multicast session or moves to a new access system. The 2volved Pac#et "ystem networ# shall support a minimum of = levels of Do" in parallel. The 2volved Pac#et "ystem networ# shall support a minimum of < parallel /T Do" levels with the appropriate Do" differentiation.

? ? ? ? ?

? ? ?

? ?

3GPP

!elease "#

"+

3GPP TS ##$#%& '"#$($( (#("")"#

'OT2 ,H The re@uirement for the number of simultaneously supported Do" levels is independent of any M0M" Do" levels. ? Multiple /T services- with similar Do" re@uirements- shall be served by the same /T Do" level and multiple '/T services- with similar Do" re@uirements- shall be served by the same '/T Do" level. The ma(imum number of parallel /T and '/T services shall not be limited in the 2volved Pac#et "ystem includin the 32. Only the number of parallel /T and '/T Do" levels are limited to the upper value supported by the 2volved Pac#et "ystem. ? ? :ifferentiated handlin based on Do" is needed for different traffic types. The 2volved Pac#et "ystem shall support parallel operation of /T and '/T services per user.

'OT2 *H The different Do" levels provided for /T and '/T services would be differentiated with re ards to e. . ma(imum end?to?end delay- pac#et si!e- pac#et drop percenta e- etc. 0andwidth is not used to define a Do" level.

6.. Su%%!rt !5 Mu$tica#t a'" ?r!a"ca#t Ser7ice#

The 2volved Pac#et "ystem shall be able to support Multicast and 0roadcast "ervices which shall be enhanced especially from some aspects- e. . optimi!ed service provisionin procedures- better performance compared to current M0M" system- and support of multiple access systems.

6.5 Su%%!rt !5 E<er3e'c@ +a$$#

The 2volved Pac#et "ystem shall support &M" emer ency calls applicable to the P" domain- defined in T" **.,+, J*,K

3GPP

!elease "#

",

3GPP TS ##$#%& '"#$($( (#("")"#

Mu$ti-acce## a'" #ea<$e## <!(i$it@

7.1 M!(i$it@ <a'a3e<e't

7.1.1 :eter!3e'e!u# acce## #@#te<# <!(i$it@

PST7
SC

9nternet Evolved
MM

3GPP 5e/acy System

...

Policy

Packet
AAA :ore ...

Evolved Packet System

E)6T!A and E)6T!A7

...

7on 3GPP Access System

.i/ure 30 3etero/eneous access system mo4ility 4et2een 3GPP 5e/acy Systems or E)6T!A7 and non 3GPP Access Systems includin/ .i8ed Access systems The 2volved Pac#et "ystem shall support mobility between hetero eneous access systems. The 2volved Pac#et "ystem shall provide mobility mechanisms to support fre@uent handovers within and across 3GPP le acy systems or 2?3T/.' and non 3GPP access systems in order to avoid service de radation. The 2volved Pac#et "ystem shall support mobility mechanisms that accommodates access systems within /el?; and earlier.

7.1.2 L!ca$ (rea>!ut

The 2volved Pac#et "ystem shall allow for local brea#out. 5ocal brea#out means that for a user which ma#es mobility within and across one operator?defined networ# re ion- routin is optimi!ed such that user plane traffic does not need to leave the current re ion. .n operator may define networ# re ions e. .- accordin to administrative domains. 5ocal brea#out is applicable for user?to?user traffic as well as for 3GPP?operator provided services (includin internet access). 5ocal brea#out shall be allowed independently from the access system bein used. 5ocal brea#out shall be allowed in both the non?roamin and the roamin case. The use of local brea#out shall be authorised by the >P5M'. &f local brea#out is not authorised- the user plane traffic shall be handled in the home routed mode.

3GPP

!elease "#

"%

3GPP TS ##$#%& '"#$($( (#("")"#

7.1.3 )i0e" &cce## S@#te<#

The 2volved Pac#et "ystem shall be able to support fi(ed access systems with very limited or no mobility functionality. The 2volved Pac#et "ystem shall be able to support mobility within and across 3GPP and non?3GPP access systems includin fi(ed access systems

7.1.. Ser7ice c!'ti'uit@

7.1...1 Ge'era$

"ervice shall be maintained durin and followin chan es of 3GPP access systems and non 3GPP systems. "ervice shall be maintained durin and followin a chan e of networ# in either direction between a /el?; and earlier networ# and an 2volved Pac#et "ystem. &t shall be possible to support &nter?P5M' handover with seamless service continuity within a 3GPP specified access system (3T/.'- 2?3T/.'). Ehen the access system chan es- Multicast and 0roadcast services shall be able to continue with their correspondin Multicast and 0roadcast services- if the correspondin services are provided in the tar et access system. 'oteH 1orrespondin Multicast and 0roadcast services are the Multicast and 0roadcast services in the tar et access system which is associated to the Multicast and 0roadcast services in the source access system- providin similar service e(perience- e. . with same content but different bit?rate.

E7!$7e" PLM*-&
3GPP c!re

E7!$7e" PLM*-?
3GPP c!re

3GPP acce##

3GPP acce##

.i/ure *0 9nter)P5;7 handover 2ith seamless service continuity 2ithin a 3GPP specified access system

7.1...2

Ser7ice c!'ti'uit@ at "!<ai' a'" e;ui7a$e't PS #er7ice

&T cha'3e 5!r TS 11, TS 12 a'"

&t shall be possible to support continuity of an established voice call- i.e. between a T",,- T",* and an e@uivalent P" service- when the 32 moves between two different domains and /.Ts. The user e(perience shall be as far as possible unaffected by the chan e of domain and /.T. The /.T chan e procedure e(ecuted to enable service continuity for an established voice call shall tar et an interruption time not hi her than 3++ ms. /.T chan e and domain selection shall be under the control of the re istered P5M'. Ehen the 32 is roamin - it shall be possible for the CP5M' to ta#e into account any userOs >P5M' operator policy. To support service continuity of an established voice call a 32 shall not be re@uired to support simultaneous radio transmission via different 3GPP defined /.Ts 'OT2H &n the case of 1" emer ency calls (T",*) the service continuity at domain and /.T chan e can only be performed if &M" emer ency calls are supported by the tar et system.

3GPP

!elease "#

"&

3GPP TS ##$#%& '"#$($( (#("")"#

7.1...2&

V!ice +a$$ Ser7ice c!'ti'uit@ (et2ee' 3GPP "e5i'e" "e5i'e" &T#

&T# a'" '!' 3GPP

1ontinuity of an established voice call- i.e. between a T",, and an e@uivalent P" service- when the 32 moves between 3GPP defined /.Ts and non 3GPP defined /.Ts- shall be supported provided that the non?3GPP defined /.Ts is connected to the 3GPP system via the 2volved Pac#et 1ore. The user e(perience shall be as far as possible unaffected by the chan e of /.T.

7.1...3

Ser7ice c!'ti'uit@ (et2ee' E-UT &* a'" 3GPP2 acce##e# !' E7!$7e" Pac>et +!re

The 2volved Pac#et "ystem shall support bidirectional service continuity between cdma*+++ ,(/TT /evision . J=KJBK- J,+K- J,,K- J,*K- J,3K- J,<K- J,8K and 2?3T/.'. 'OT2 ,H if bi?directional support is not practical- service continuity from 2?3T/.' to cdma*+++ ,(/TT /evision . should have the hi her priority. 'OT2 *H The 1" component of cdma*+++ ,(/TT /evision . is not e(pected to be connected to the 2volved Pac#et 1ore. The 2volved Pac#et "ystem shall support bidirectional service continuity between cdma*+++ >/P: (,(2C?:O) /evision . J,;K- J,<K- J,8K- J,9K and 2?3T/.' for best effort and real?time applications. The 2volved Pac#et "ystem shall support bidirectional service continuity between cdma*+++ >/P: (,(2C?:O) /evision + J,=K- J,<K- J,8K- J,9K and 2?3T/.' for best effort applications.

7.1....

Ser7ice c!'ti'uit@ (et2ee' 3GPP a'" BiM&C acce## !' E7!$7e" Pac>et +!re

The 2volved Pac#et "ystem shall support bidirectional service continuity between Mobile EiM.F J*+K- J**K- J*3KJ*<K and G2/.' P". The 2volved Pac#et "ystem shall support bidirectional service continuity between Mobile EiM.F J*+K- J**K- J*3KJ*<K and 3T/.' P". The 2volved Pac#et "ystem shall support bidirectional service continuity between Mobile EiM.F J*+K- J**K- J*3KJ*<K and 2?3T/.'. 'OT2H The above re@uirements assume that the service continuity ta#es place throu h the 2volved Pac#et 1ore.

7.1.5 &cce## 'et2!r> "i#c!7er@

To avoid unnecessary bac# round scan by the 32 and to facilitate service continuity by the 32 it shall be possible for the CP5M' and the >P5M' to provide the 32 with access networ# information pertainin to locally supported non? 3GPP access technolo ies- in a resource efficient and secure manner. This mechanism is meant to facilitate chan esincludin service continuity- between 3GPP access systems and non 3GPP access systems and vice versa. The information may be restricted to the access technolo ies the 32 can use. To reduce battery drain- a 32 should minimise the fre@uency of scannin for different access technolo ies. Ehen discoverin non?3GPP accesses a 32 shall be able to receive information from a non?3GPP access networ# concernin to which P5M'- or P5M's- the non?3GPP access networ# provides access. 'oteH The capability to provide such information by a non?3GPP access networ# is out of scope of 3GPP. Ehen a 32 receives service via a non?3GPP access it shall be possible for the P5M' that provides the non?3GPP access to indicate local availability of 3GPP access to the 32-- in a secure manner- subject to capabilities of the non? 3GPP access networ#.

3GPP

!elease "#

"-

3GPP TS ##$#%& '"#$($( (#("")"#

7.1.6 Steeri'3 !5 acce##

Ehen a 32 is accessin the 2volved Pac#et 1ore via 2?3T/.- the operator of the P5M' that provides the access (re istered P5M' or /P5M' for short) may re@uest the 32 to use ? any or a specific ? non?3GPP /.T. "imilarly- if a 32 is accessin the 2volved Pac#et 1ore via a non?3GPP /.T then the /P5M' may want to re@uest the 32 to use 2? 3T/.. The reason for such steerin may be load balancin (for camped? and traffic load balancin )- operator policyprivate networ#sGhome cells- service based mobility control etc. The /P5M' shall be able to download on the 32 a list of preferred access technolo ies in priority order. &f- while the 32 is re istered on that P5M'- an access technolo y with hi her priority than the one currently used is detected- the 32 shall attempt to use the hi her priority access networ# to access the /P5M'. The 32 shall only perform access technolo y selection within the /P5M'. &n case the 32 is connected to the P5M' via a non?3GPP access- then the P5M' reselection procedures specified for that access technolo y may be e(ecuted. 'ote ,H The P5M' operator may provide access to the 2volved Pac#et 1ore either throu h an own access networ# (2?3T/. or non?3GPP access) or in collaboration with an access networ# operator that operates a non? 3GPP access networ#. 'ote *H . specific non?3GPP /.T may e. . be identified by /.T type and the access networ# name (as adverti!ed by the access networ#)- or a list of access networ# names. The >P5M' may also provide the 32 with a list of preferred access technolo ies in priority order for use in the /P5M'. Only one list of preferred access technolo ies can be active at a time and the list provided by the /P5M' ta#es precedence over the list provided by the >P5M'. The list of preferred access technolo ies received from the CP5M' is specific to that CP5M' and P5M's e@uivalent to it.

7.1.7 +S 5a$$(ac>
7.1.7.1 Ge'era$

7or those services delivered via the >P5M' that the >P5M' only supports in the 1" domain (e. . voice services)when such services are invo#ed while the 32 is confi ured to use 1" 7allbac# and re istered in the 2?3T/.' (either in the >P5M' or in a CP5M')- it shall be possible for the 2P" to re@uest the 32 to perform a chan e of radio access technolo y in order to deliver the service over 3T/.' or G2/.' or ,(/TT. &n the case of an incomin 1" service to a 32 that is re istered for 1" services and active in 2?3T/.'- the 2P" shall transfer the 15& to the 32 if available and the callin party has not restricted the presentation- prior to tri erin 1" fallbac#. :ependin on 32 confi uration and when the 32 is in connected mode- the user or an application on behalf of the user may re@uest to accept or reject 1" fallbac# before performin a chan e of radio access technolo y. The default behaviour of the 32 is to accept the 1" fallbac#.

7.1.7.2

!a<i'3 i' a VPLM* '!t #u%%!rti'3 +S 5a$$(ac>

Ehen a 32 that is confi ured to use 1" fallbac# re isters over 2?3T/.' in a CP5M' not supportin 1" fallbac# the default behaviour of the 32 is to attempt to select a G2/.'G3T/.'G,(/TT 1" radio access technolo y in the CP5M' or in a P5M' e@uivalent to the CP5M'. The default behaviour of the 32 is not to autonomously attempt to (re?)select the 2?3T/.' for the duration of the time the 32 stays in a CP5M' and P5M's e@uivalent to the CP5M'. The default behaviour may be chan ed based on user preference settin s. The 32 may offer the user to perform a P5M' scan and display the list of available P5M's. The selection of a different P5M' is performed usin the manual mode.

3GPP

!elease "#

#(

3GPP TS ##$#%& '"#$($( (#("")"#

7.2

4)8M Ser7ice re;uire<e't#

"imultaneous active mode of operation is an optional capability for multimode 32s- which support 3GPP and E5.' access. 32 supportin simultaneous active mode of operation between one set of technolo ies may not be capable to support simultaneous active mode of operation between a different technolo y set (e. . due to radio interference limitations). The followin re@uirements apply to the case of 32s with multiple interfaces which will simultaneously connect to 3GPP access and one sin le E5.' access. ? ? &t shall be possible to provide service continuity when the 32 moves from the 3GPP access to E5.' access and vice versa. &f the 32 is under the covera e of more than one access- includin 3GPP and E5.' accesses and communicates usin multiple accesses simultaneously- it shall be possible to select one access when a flow is started and re?distribute the flows toGfrom a 32 between accesses while connected. &t shall be possible for the operator to enable and control via policies the simultaneous usa e of multiple accesses. &t shall be possible to distribute &P flows toGfrom a 32 between available accesses based on the characteristics of the flows and the capabilities of the available accesses- subjected to user$s preferences and operator$s policies. &t shall be possible for the operator to define policies for the control of the distribution of &P flows between available accesses. 2ach policy shall include a list of preferred accesses and whether the policy may be overridden by the user$s preferences. 'OT2H The possibility of manual selection or user override is not precluded. These policies may be defined per .P'- per &P flow class under any .P' or per &P flow class under a specific .P'. The &P flow class identifies a type of service (e. . &M" voice) or an operator defined a re ation of services. The policies apply with the followin priority orderH ,. *. 3. ? Policies per &P flow class under a specific .P'. Policies per &P flow class under any .P'. Policies per .P'.

? ? ?

:istribution of flows toGfrom a 32 between available accesses based on the characteristics of the flows andGor the capabilities of the available accesses shall be possible for flows e(chan ed by both operator controlled (e. . &M") and non operator controlled (e. . web and mail access) applicationsGservices. &t shall be possible to move all the flows toGfrom a 32 out of a certain access in case the 32 loses connectivity with that access (e. . 32 moves out of covera e of a E5.' access while maintainin connectivity throu h the 3GPP access). /e?distribution of flows toGfrom a 32 between accesses may be tri ered by chan es to the characteristics of the flows (e. . Do" re@uirements) or the capabilities of the available accesses (e. . due to networ# con estionmobility event- or 32 discovers a new access) durin the connection.

Per5!r<a'ce re;uire<e't# 5!r the E7!$7e" Pac>et S@#te<

The 2volved Pac#et "ystem comprises the 2volved Pac#et 1ore to ether with the evolved radio access networ# (2? 3T/. and 2?3T/.'). . study of the 2volved Pac#et 1ore can be found in T"*3.==* J;K and the evolved radio access networ# 2?3T/. and 2?3T/.' in T/*8.B,3 J<K.

3GPP

!elease "#

#"

3GPP TS ##$#%& '"#$($( (#("")"#

The performance objectives for the 2volved Pac#et "ystem include hi her user data rates- reduced latency- improved system capacity and covera e- reduced networ# comple(ity and lower operatin costs. The 2volved Pac#et "ystem shall meet or e(ceed the followin performance criteriaH a) The radio access networ# shall be capable of supportin instantaneous pea# pac#et data rates of ,++ Mbps on the radio access bearer downlin# to the 32 and 8+ Mbps on the uplin#. b) The 2volved Pac#et "ystem shall be capable of providin lower user and control plane latency when compared to e(istin 3GPP access networ#s. The ma(imum delay should be comparable to that for fi(ed broadband &nternet access technolo ies. Je. . less than 8ms in ideal conditionsK c) The system shall be capable of supportin lar e volumes of mi(ed e. . voice- data and multimedia traffic. 2nhanced load balancin and steerin of roamin methods should be used to minimise cell con estion. d) The level of system comple(ity and mobility mana ement si nallin shall be optimised to reduce infrastructure and operatin costs. 32 power consumption shall also be minimised accordin ly. e) 7or the 2volved Pac#et "ystem the interruption time durin handover of /T and '/T services shall be #ept to minimum and shall not e(ceed the values defined in T/ *8.B,3J<K.

3GPP

!elease "#

##

3GPP TS ##$#%& '"#$($( (#("")"#

Securit@ a'" %ri7ac@

/.1 Ge'era$
The 2volved Pac#et "ystem shall provide a hi h level of security and privacy for users and 2volved Pac#et "ystem operators.

/.2 Securit@ re;uire<e't#

The 2volved Pac#et "ystem shall provide a hi h level of security- e@uivalent or better than /el?; 3GPP systems. .ny possible lapse in security in one access technolo y shall not compromise security of other accesses. The 2volved Pac#et "ystem should provide protection a ainst threats and attac#s includin those present in the &nternet. The 2volved Pac#et "ystem shall support information authenticity between the terminal and 2volved Pac#et "ystems. The 2volved Pac#et "ystem shall allow for a networ# to hide of internal networ# elements from the 32. "ecurity policy shall be under the control of the home operator. The security solution should not interfere with service delivery or 3GPP inter?access handovers in a way that is noticeable to end?users or service providers. .ppropriate traffic protection measures should be provided by the 2volved Pac#et "ystem. The 2volved Pac#et "ystem shall provide appropriate mechanisms to enable lawful intercept. The 2volved Pac#et "ystem shall ensure that no unauthori!ed user can obtain a le itimate &P address that can be used to establish communication or enable malicious attac#s on evolved system entities. /elease BB or later /eleases$ 3"&M application on the 3&11 is re@uired to authenticate a user in an 2volved Pac#et "ystem and hence allowin the user to et services in the 2volved Pac#et "ystem accordin to herGhis subscription. 'oteH The above re@uirement is applicable when providin access to the 2P1 via 2?3T/.'.

Once authenticated via a 3GPP or 2volved Pac#et "ystem- the 3"&M shall not be re@uired to re?authenticate upon chan in between these systems- unless specifically re@uested by the operator (P5M'). 'OT2H &t may be possible to use other applications on the 3&11 in order to provide authentication on the 3GPP or 2volved Pac#et "ystem (e. . for connection to &M"). &n addition- in case it is desirable to improve the level of security or to add new security mechanisms for accessin the 2volved Pac#et "ystem compared to the one provided in /el?;- a revisedGup raded application on the 3&11 may be re@uired.

/.3 Pri7ac@ re;uire<e't#

The 2volved Pac#et "ystem shall provide several appropriate levels of user privacy includin communication confidentiality- location privacy- and identity protection. The privacy of the contents- ori in- and destination of a particular communication shall be protected from disclosure to unauthorised parties. The 2volved Pac#et "ystem shall be able to hide the identities of users from unauthorised third parties. &t shall be possible to provide no disclosure- at any level of ranularity- of location- location?related information- e. . eo raphic and routin information- or information from which a userOs location can be determined- to unauthorised parties- includin another party on a communication.

3GPP

!elease "#

#3

3GPP TS ##$#%& '"#$($( (#("")"#

10

+har3i'3 &#%ect#

The 2volved Pac#et "ystem shall support various char in models includin all those supported by the 3GPP system contained within T"**.,,8 J8K . 1har in models that shall be supported by the 2volved Pac#et "ystem include (non?e(haustive list)H ? ? ? ? ? ? ? callin party pays char in based on assured Do" char in based on the transport char in based on an event char in based on content char in adjustment (e. . based on subscription bands) alternate party char in

The 2volved Pac#et "ystem shall also be able to support introduction of new char in schemes includin online and offline schemes- and char in schemes for the multi?access system environment 1har in mechanisms of the 2volved Pac#et "ystem shall provide (non?e(haustive list)H ? ? ? ? 1ost effective 1ontrol and 1har in of &P 7lows Perform online char in "upport differentiated char in includin !ero ratin of the bearer and event char in .wareness of subscriber identity- time?of?day- roamin status- Do"- "ervice input etc

3GPP

!elease "#

#*

3GPP TS ##$#%& '"#$($( (#("")"#

&''e0 & (i'5!r<ati7e), e;uire<e't# 5!r 5urther #tu"@

&.1 Ma'a3e<e't !5 acce## 'et2!r>#
The 2volved Pac#et "ystem shall be able to allow for self?mana in technolo ies (e. . Plu ?and?Play) for dynamically addin and removin non?3GPP defined access networ#s. "uch self?mana in technolo ies shall ta#e into account the 2volved Pac#et "ystem and access networ# policies. 2. . dependin on such policies it shall be possible to for the 3GPP system operator to re@uest encryption of user traffic that is transmitted over the access networ#. 'OT2 ,H The non?3GPP access networ# needs to have defined interwor#in with 3GPP. .n e(ample could be a E5.' (operated by some E5.' operator) that can- if needed- automatically be connected to a P5M' to serve as an &?E5.' access. This would enable the P5M' operator to provide additional access resources on a dynamic basis and to provide service to more customers (e. . at mass events). 'OT2 *H The de ree of automation provided for networ# attachment is yet to be determined- but is intended to simplify (or completely automate) administration procedures.

&.2 U#e ca#e# 5!r )i0e" M!(i$e +!'7er3e'ce

. family has purchased a family subscription plan that is independent of access (e. . fi(ed or wireless) and location (e. . both when at home and away from home). The subscription contains at least the followin componentsH &nternet accessH Operator specific service such as firewall and content filterin (parental control) independent of access for selected devices within the family. The service should be available at home- within the home mobile networ# and when roamin to a visited mobile networ#. CoiceGMultimediaH Do" and mobility between home E5.' and 5T2 wide area 1har in schemas connected to access type- preference and location CideoH Premium Cideo on :emand "ervice incl. uaranteed bandwidth and Do" re ardless of access networ#.

,es ri#tion 0se ase &: 'nternet a ess (ith Parental ontrol and #ersonal fire(all The #ids leave their house and ta#e a bus to their randparentsO house. The operator specific services- li#e parental control and personal firewall- are invo#ed for specific users and terminals from both fi(ed networ# and from mobile networ#I this allows the #ids to et the same service and filterin inside the home- in the bus oin to randparents and at the randparents. &n this use case the randparents have a separate service provider than the family but the services will still be provided by the service provider where the family has a subscription. 0se ase 2: 1oi e2*ultimedia and .har)in) The father travels home after wor# while tal#in on the phone with his collea ue. The on oin CoiceGMultimedia call between the father and his collea ue is maintained while switchin over between 5T2 Eide area and residential fi(ed broadband E5.' networ#. Once the call is switched over to E5.' char in for home?based access is applied. 0andwidth and Do" is maintained for the duration of the call to uarantee the same service delivery. 0se ase /: 1ideo

3GPP

!elease "#

#+

3GPP TS ##$#%& '"#$($( (#("")"#

The #ids in the bac#seat of the car are watchin an &nternet TC show on their laptop usin 5T2 while drivin home from the randparentOs house. The TC show is sent from an &nternet TC provider. Once home the terminal detects indoor E5.' covera e where the subscriber has a E5.' /esidential Gateway connected to his 7i(ed 0roadband networ#. The user or the terminal automatically may select to switch the &P connection to the wireline broadband connection and enable the user to resume watchin the same TC show on the same laptop- possibly with a better @uality picture as allowed by the available bandwidth- user?specific policy- networ# policy and Do" settin . 0se ase 4: 3(e)NB24emto ell . subscriber desires to improve covera e and access speed for their 3GPP device in their home. They purchase and install a small e'ode0 (7emtocell .P) device for their home which attaches to the home 5.' and establishes a connection bac# to the subscriberOs mobile service provider networ#. The mobile networ# provider coordinates with the broadband access provider to deliver proper bandwidth and Do" to support a ood Do2 for calls and data sessions made within the home that access services from the mobile networ#. The 7emtocell also allows some types of data traffic to be shared with the home 5.'- includin traffic for &nternet applications. 5ocal traffic can be discerned and accounted for differently than traffic that is carried on the mobile networ#. 0se ase 5: A##li ation *o$ility . subscriber is in a multimedia call on their mobile device- and then wishes to chan e the device they are usin to a fi(ed networ# attached device (e. . "et Top 0o( G TC). The multimedia call is handed over from the mobile networ# to the fi(ed networ# after the subscriber chooses to transfer the multimedia call to a "T0 G TC. 0andwidth and Do" is maintained for the lar e screen e(perience to be meanin ful. .ccountin and settlement is supported amon the application and networ# service providers- and reflects the chan es to the access technolo y and re@uired bandwidth. 0se ase %: .ommon 6uota . 1ommon Duota (1D) can be assi ned for both fi(ed and mobile accesses for a limited time period for a defined set of subscriptions. :urin each session the networ# elements monitor the 1D which may be consumed by one or more devices over either the wireless or fi(ed networ#s. Ehen a defined percenta e of the 1D andGor all the 1D has been consumed- one or more subscribers in the defined set can be notified of the event (e. . via "M" andGor email). Ehen the 1D has been consumed the access to the services is bloc#ed. 0se ase -: 1ideo +n ,emand "ervi e Cideo On :emand (Co:) service is provided to the subscriber via the "et Top 0o( to the TC or to the P1. . user orders a Co: service interactin with the Co: infrastructure- which sends a resource re@uest to the networ#. The user may also re@uest mid?session re@uests tri erin the increaseGdecrease of networ# resources. The re@uests will be accepted or rejected accordin to the available networ# resources. 0se ase 7: Broad$and A ess 8holesale &n 0roadband networ# the wholesale scenario is @uite important as it may be re@uired by the re ulation- #nown as unbundlin (access- connectivity and services). 7or e(ample the operator of the broadband access networ# leaseGsell transport of the connection throu h its own networ# from the user to the buyer G leased networ#. "o in the wholesale scenario the rentin operator has the end?to?end "ervice responsibility to the customer and is viewed as the P/etailerQ of the service or application. Ehile the leasin networ# operator has the responsibility for the access networ# and for the connectivity.

3GPP

!elease "#

#,

3GPP TS ##$#%& '"#$($( (#("")"#

&''e0 ? (*!r<ati7e), E7!$7e" Pac>et S@#te< (EPS) a%%$ica($e #%eci5icati!'#

The specifications listed in clause 0.,contain re@uirements applicable to the 2volved Pac#et "ystem (2P").

?.1 EPS &%%$ica($e S%eci5icati!'#

TS 21./05 22.011 22.016 22.022 22.030 22.038 22.0.1 22.0.2 22.066 22.067 22.071 22.078 22.101 22.105 22.115 22.12/ 22.1.6 22.153 22.173 Title V!ca(u$ar@ 5!r 3GPP S%eci5icati!'# Ser7ice acce##i(i$it@ See '!te 4'ter'ati!'a$ M!(i$e E;ui%<e't 4"e'titie# (4ME4) Per#!'a$i#ati!' !5 M!(i$e E;ui%<e't (ME)D M!(i$e 5u'cti!'a$it@ #%eci5icati!' Ma'-Machi'e 4'ter5ace (MM4) !5 the U#er E;ui%<e't (UE) US4M &%%$icati!' T!!$>it (US&T1S&T)D Ser7ice "e#cri%ti!'D Sta3e 1 8%erat!r 6eter<i'e" +a$$ ?arri'3 *et2!r> 4"e'tit@ a'" Ti<e E!'e (*4TE) #er7ice "e#cri%ti!'D Sta3e 1 Su%%!rt !5 M!(i$e *u<(er P!rta(i$it@ (M*P)D Sta3e 1 e'ha'ce" Mu$ti-Le7e$ Prece"e'ce a'" Pre-e<%ti!' #er7ice (eMLPP)D Sta3e 1 L!cati!' Ser7ice# (L+S)D Ser7ice "e#cri%ti!'D Sta3e 1 +u#t!<i#e" &%%$icati!'# 5!r M!(i$e 'et2!r> E'ha'ce" L!3ic (+&MEL) Ser7ice Pri'ci%$e# Ser7ice# a'" Ser7ice +a%a(i$itie# +har3i'3 a'" ?i$$i'3 :a'"!7er re;uire<e't# (et2ee' UT &* a'" GE &* !r !ther ra"i! #@#te<# Mu$ti<e"ia ?r!a"ca#t1Mu$tica#t Ser7ice (M?MS)D Sta3e 1 Mu$ti<e"ia %ri!rit@ #er7ice 4P Mu$ti<e"ia +!re *et2!r> Su(#@#te< (4MS) Mu$ti<e"ia Te$e%h!'@ Ser7ice a'" #u%%$e<e'tar@ #er7ice#D Sta3e 1 22.17. Pu#h #er7iceD Sta3e 1 22.182 +u#t!<iFe" &$erti'3 T!'e# (+&T) e;uire<e't# 22.226 G$!(a$ te0t te$e%h!'@ (GTT)D Sta3e 1, Ser7ice "e#cri%ti!' 22.228 Ser7ice re;uire<e't# 5!r the 4'ter'et Pr!t!c!$ (4P) <u$ti<e"ia c!re 'et2!r> #u(#@#te< (4MS)D Sta3e 1 22.233 Tra'#%are't e'"-t!-e'" %ac>et-#2itche" #trea<i'3 #er7iceD Sta3e 1 22.23. e;uire<e't# !' 3GPP #@#te< t! Bire$e## L!ca$ &rea *et2!r> (BL&*) i'ter2!r>i'3 22.2.0 Ser7ice re;uire<e't# 5!r 3GPP Ge'eric U#er Pr!5i$e (GUP)D Sta3e 1 22.2.2 6i3ita$ i3ht# Ma'a3e<e't (6 M)D Sta3e 1 22.2.6 Mu$ti<e"ia ?r!a"ca#t1Mu$tica#t Ser7ice (M?MS) u#er #er7ice#D Sta3e 1 22.250 4P Mu$ti<e"ia Su(#@#te< (4MS) Gr!u% Ma'a3e<e'tD Sta3e 1 22.25/ Ser7ice re;uire<e't# 5!r Per#!'a$ *et2!r> Ma'a3e<e't (P*M)D Sta3e 1 22.27/ +!<(i'e" +ircuit S2itche" (+S) a'" 4P Mu$ti<e"ia Su(#@#te< (4MS) #e##i!'#D Sta3e 1 22.3.0 4P Mu$ti<e"ia Su(#@#te< (4MS) <e##a3i'3D Sta3e 1 *!te, 4' ca#e the UE i# c!''ecte" t! the PLM* 7ia a '!'-3GPP acce##, the' the PLM* (re)#e$ecti!' %r!ce"ure# #%eci5ie" 5!r that acce## tech'!$!3@ <a@ (e e0ecute".

3GPP

!elease "#

#%

3GPP TS ##$#%& '"#$($( (#("")"#

&''e0 ?1 (4'5!r<ati7e), 4'ter2!r>i'3 (et2ee' M!(i$e 8%erat!r# a'" 6ata &%%$icati!' Pr!7i"er#
This .nne( provides various scenarios and use cases applicable for interwor#in between mobile operators and data applications.

?1.1 Sce'ari!#
7i ure , shows the non?roamin scenario where the mobile operator owns the 2P" as well as application layer entities. .ccess and &P connectivity is provided by the mobile operator. .pplication platforms- also provided by the mobile operator- shown in the fi ure connect to the core networ# directly. .pplication platforms could be application servers (e. . Cideo on :emand "erver- P"" "erver- MT1 "erver- etc.). .pplications developed usin .P&s (e. . /2"T- G"M. One.P&) and resident on the .P& Gateway are connected to the operator core networ# via the .P& Gateway. The dashed lines between Operator 1' and &M" as well as .P& Gateway are already specified.

.i/ure "0 <perator o2ned non)roamin/ scenario 7i ure * provides the non?roamin scenario where the mobile operator does not own all the application layer entities. .ccess and &P connectivity is provided by the mobile operator. The 3rd party .pplication Platforms in this fi ure could be application servers (e. . Cideo on :emand "erver- P"" "erver- MT1 "erver- etc.) or could be 3rd party software development platforms. The hori!ontal line represents the demarcation between the mobile operator domain and the 3rd party application provider domain. The mobile operator and 3rd party application providers may have a reements.

3GPP

!elease "#

#&

3GPP TS ##$#%& '"#$($( (#("")"#

.i/ure #0 :olla4orative non)roamin/ scenario 7i ure 3 provides the roamin scenario for both the above owned and collaborative scenarios. This fi ure shows the home?routed scenario where all traffic is routed to home mobile operator 2P" and applications are delivered via roamin a reements between mobile operators.

.i/ure 30 <perator o2ned=colla4orative roamin/ scenario > 3ome !outed 7i ure < provides the roamin scenario between mobile operators and 3rd party application provider domains. &n this scenario the application provider has a reements with visited mobile operator. This fi ure shows the local?brea#out scenario where all traffic is routed to application domain from the visited operator networ#.

3GPP

!elease "#

#-

3GPP TS ##$#%& '"#$($( (#("")"#

.i/ure *0 :olla4orative roamin/ scenario > 5ocal ?reakout

?1.2 U#e ca#e#

?1.2.1 U#e ca#e# 5!r !2'e" 1 c!$$a(!rate" #ce'ari!#.
Pre9 onditions . data application provider F develops an application customi!ed for streamin hi h definition movies to the mobile end user over 3GPP access. The data application provider F develops this application specifically for a mobile networ# operator (M'O) R. The data application provider F hosts this application and establishes a reements with a mobile networ# operator (M'O) R to pilot the service. .uthentication and char in are provided by the M'O R. The data application provider F can collaborate with other M'Os as well. .lice has subscribed to a 3GPP device and video services from the M'O R. 0se ase &: Authenti ation and Authori:ation .lice ets onto a train for <?hour lon ride to a nei hborin country. "he turns on her device and loo#s at the movie catalo . "he decides to view a movie and selects the movie offered by the data application provider F and watches it without worryin about the radio access networ# she is usin and any additional lo inGpassword procedures. 0se ase 2: Allo ation of resour es and other #oli y intera tions .ll alon the M'O R mana es the resources and the Do" needed for hi h definition movie streamin to .lice. On the train- .lice ets distracted by the scenery and misses a few scenes. "he rewinds and views the missin scenes. 0se ase /: "imultaneous intera tions (ith multi#le a##li ation #roviders .lice comes across an interestin ad et in the movie and decides to pause on that scene and et a hi her resolution closeup view. The close up view prompts an advertisement to pop up for the ad et. 0ased on this advertisement- .lice purchases the ad et. "he is iven the choice of payin immediately or bein char ed on her M'O monthly bill. "he decides to char e to her M'O bill. 0se ase 4: Roamin) .lice continues watchin the movie and the train crosses the country border. "he starts roamin into another M'O Swhich has roamin a reement with M'O R. The movie @uality is unaltered in the process of roamin . 0se ase 5: .har)in) "he ets a bill from the M'O at the end of the month which includes the price for the movie she watched on the train and the ad et she purchased.

3GPP

!elease "#

3(

3GPP TS ##$#%& '"#$($( (#("")"#

?1.2.2
?1.2.2.1

U#e ca#e# 5!r '!'-c!$$a(!rate" #ce'ari!#. UE i'itiate# a'" re;ue#t# M*8 5!r %re5ere'tia$ tra55ic ha'"$i'3

Pre9 onditions ,. *. Mobile 'etwor# Operator R (M'O R) has no business relationship nor is there any service collaboration with :ata .pplication Provider F (:.P F). :.P F develops a free application customi!ed for streamin movies to the mobile end user over 3GPP access. :.P F develops the application independently from M'O R and hosts this application outside of M'O ROs networ#. The user accesses the service via the networ# of M'O R connected to :.P F via a transit networ#. The service is provided to the user transparently throu h M'O ROs networ#. The networ# of M'O R supports tiered bearers and M'O R offers prefential traffic handlin on demand from users with a preview period defined either by the operator or the application provider for acceptance of the service. M'O R has a roamin a reement with M'O S to provide preferential traffic handlin for users at an e(tra cost to the user. M'O R has no #nowled e or control of the service bein delivered by :.P F. 7urther M'O R has no #nowled e of the resources available at :.P F or of those in the transit networ# throu h which it is connected. .lice has subscribed to a 3GPP data service from M'O R and has downloaded the free movie streamin application from :.P F. "he has purchased credit throu h the application to enable streamin of content. 'o further authentication of authorisation is re@uired with :.P F in order for .lice to receive content. The movie streamin application uses default level of resources and Do" (e. . best effort- or based the subscriber profile) from the P5M'. .lice is on a train travellin across national boarder from 1ountry . to 1ountry 0. 1ountry . is served by M'O R. 1ountry 0 is served by M'O S.

3.

<.

8.

0se ase %: Authenti ation and Authori:ation .lice decides to watch a movie. "he turns on her device- re isters with the networ# operated by M'O R and launches the application to browse the movie catalo ue. "he decides to view a movie so she selects it and starts to watch it. 0se ase -: Allo ation of resour es and other #oli y intera tions .t some point in the movie (e. . due to mobility- networ# con estion- etc) .lice becomes dissatisfied with the @uality of the movie. .lice re@uests preferential traffic handlin from M'O R. .lternative ,. .lice does not notice any improvement in the @uality of the streamed movieand she does not confirm the re@uest for preferential traffic handlin within the preview period. .lternative *. .lice notices a mar#ed improvement in the @uality of the streamed movie and she confirms the re@uest for preferential traffic handlin . .s the train crosses the national boarder between 1ountry . and 1ountry 0- .lice is notified of the chan e in M'O and char in . .lternative 3. .lice decides not to consent for the additional char e. The @uality of the bearer reverts to its default level after the specified consent period has e(pired.

3GPP

!elease "#

3"

3GPP TS ##$#%& '"#$($( (#("")"#

.lternative <. .lice decides to pay additional char e and consents. The @uality of the bearer remains at its present level. 0se ase 7: .har)in) .lternative ,. .lice receives a bill from M'O R at the end of the month that includes roamin char es from M'O S- but no additional char es for preferential traffic handlin . .lternative * T .lternative 3. .lice receives a bill from M'O R at the end of the month that includes roamin char es from M'O S- and the cost for preferential traffic handlin from M'O R. .lternative * T .lternative <. .lice receives a bill from M'O R at the end of the month that includes roamin char es from M'O S- as well as the cost for preferential traffic handlin from M'O R and the additional cost for prefential traffic handlin from M'O S. .lice does not receive any bill from :.P F related to the re@uest for preferential traffic handlin . ?1.2.2.2 UE i'itiate# a'" 6ata &%%$icati!' Pr!7i"er re;ue#t# M*8 5!r %re5ere'tia$ tra55ic ha'"$i'3

Pre9 onditions ,. Mobile 'etwor# Operator R (M'O R) has a business relationship but no service collaboration with :ata .pplication Provider F (:.P F).

Other pre?conditions are as specified for 0,.*.*., .uthentication and .uthori!ation is as per 3se 1ase 9 in 0,.*.*., 0se ase ;: Allo ation of resour es and other #oli y intera tions .t some point in the movie (e. . due to mobility- networ# con estion- etc) .lice becomes dissatisfied with the @uality of the movie. .lice re@uests preferential traffic handlin from :.P F. .lternatives , to are as described in 3se case * under 0,.*.F. 0se ase &<: .har)in) .lternative ,. .lice receives a bill from M'O R at the end of the month that includes roamin char es from M'O S. .lternative * T .lternative 3. .lice receives her bill from M'O R at the end of the month that includes roamin char es from M'O S. &n addition- .lice receives a statement from :.P F which includes an entry for the cost of preferential traffic handlin from M'O R. .lternative * T .lternative <. .lice receives her normal bill from M'O R at the end of the month includin roamin char es from M'O S. &n addition- .lice receives a statement from :.P F which includes an entry for the cost of preferential traffic handlin from M'O R and M'O S.

3GPP

!elease "#

3#

3GPP TS ##$#%& '"#$($( (#("")"#

&''e0 + (i'5!r<ati7e), +ha'3e hi#t!r@

.han)e history
TSG SA@ SA Aoc$ SA" Aoc SP-35 SP-070128 S1-070187 SP-35 SP-36 SP-36 SP-36 SP-36 SP-070127 S1-0701/7 SP-070365 S1-070806 SP-07036/ S1-070556 SP-070367 S1-070807 SP-070370 S1-07076. Spec 22.278 22.278 22.278 22.278 22.278 22.278 :! 0001 0002 0003 0005 0006 0008 1 1 !ev !el 2 e$-8 3 e$-8 e$-8 e$-8 e$-8 e$-8 :at Su4ject=:omment ) +$ari5icati!' !' A!S c$a##e# 5!r e7!$7e" 3GPP #@#te< ? Pr!7i#i!' !5 acce## 'et2!r> i'5!r<ati!' t! the UE ? e;uire<e't 5!r ha'"!7er# (et2ee' LTE a'" 3GPP2 acce## 'et2!r># 6 E"it!ria$ c!rrecti!' 5!r %er5!r<a'ce re;uire<e't# 5!r e7!$7e" 3GPP #@#te< ? Per5!r<a'ce re;uire<e't# 5!r e7!$7e" 3GPP #@#te< ? e;uire<e't 5!r 'ati!'a$ r!a<i'3 (et2ee' LTE-!'$@ !%erat!r# a'" 2G13G-!'$@ !%erat!r# ? e;uire<e't# 5!r #er7ice c!'ti'uit@ (et2ee' 3GPP #@#te< a'" BiM&C 6 &""iti!' !5 3GPP re5ere'ce 5!r the e7!$7e" 3GPP %ac>et #@#te< (EPS) ? Mu$ti%$e 4P #e##i!' ? V!ice #er7ice c!'ti'uit@ (et2ee' 3GPP &T a'" '!' 3GPP &T ? &$i3'<e't !5 ter<i'!$!3@ 2ith S&2 ? &cce## 'et2!r> "i#c!7er@ + Su%%!rt 5!r e55icie't "e$i7er@ !5 te0t-(a#e" (r!a"ca#t <e##a3e# ? E<er3e'c@ +a$$ Su%%!rt ? E'ha'ce<e't# t! &cce## 'et2!r> "i#c!7er@ a'" #teeri'3 !5 acce## ) Mu$ti-acce## M?MS ? A!S cha'3e re;uire<e't c$ari5icati!' + &""iti!' !5 $i#t !5 a%%$ica($e #%eci5icati!'# 5!r the EPS a'" a<e'"e" #c!%e ) +$ari5icati!' !5 EPS acce## u#i'3 %re- e$-8 US4M# ) B4M&C )!ru< #%eci5icati!' re5ere'ce i' TS 22.278 +reati!' !5 7./.0.0. +!'te't i"e'tica$ t! 8...0 - + # 28r2 a'" 30r1 ((ut '!t i'c$u"i'3 + 27r1, a%%$ica($e t! e$-8 !'$@, t! re<!7e )eature# 2hich Sta3e 3 2a# '!t c!<%$ete" !' ti<e) & Ser7ice c!'ti'uit@ (<irr!r t! a e$-8 + ) & &cce## *et2!r> 6i#c!7er@ a'" Steeri'3 !5 &cce## & U%"ate 4P #e##i!' c!'tr!$ a'" $!ca$ (rea>!ut re;uire<e't# A Requi e!ent on "uppo t of #S $all%ac& & 6e-i<%$e<e'tati!' !5 + .3r3 a'" i<%$e<e'tati!' !5 .3r5, a# a%%r!7e" "uri'3 S&G.1 & 6e$eti!' !5 re"u'"a't re5ere'ce ? Ter<i'a$ 4"e'ti5icati!' !5 3GPP a'" 3GPP2 "e7ice# ? Su%%!rt 5!r Mu$ti<e"ia Pri!rit@ <ld 8.0.0 8.0.0 8.1.0 8.1.0 8.1.0 8.1.0 7e2 8.1.0 8.1.0 8.2.0 8.2.0 8.2.0 8.2.0 B9 S&ES&ES&ES&ES&ES&E-

SP-36 SP-37 SP-37 SP-37 SP-37 SP-37 SP-38 SP-38 SP-38 SP-38 SP-38 SP-38 SP-.0 SP-.0 SP-.0

SP-070.83 S1-070805 SP-070566 S1-07132. SP-070566 S1-0710/6 SP-070566 S1-0710/7 SP-070566 S1-070//. SP-070566 S1-071122 SP-070855 S1-071856 SP-070855 S1-071/12 SP-070856 S1-071/13 SP-070856 S1-071/15 SP-070856 S1-071/16 SP-070/2/ SP-080306 S1-0807.0 SP-080306 S1-080720 -

22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278

000/ 10 11 12 13 1. 0021 0022 0015 0017 0018 002. 0028 0030

5 2 1 1 1 1 2 1 3 1 1 2 2 1

e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8 e$-8

8.1.0 8.2.0 8.2.0 8.2.0 8.2.0 8.2.0 8.3.0 8.3.0 8.3.0 8.3.0 8.3.0 8.3.0 8...0 8...0 8...0

8.2.0 8.3.0 8.3.0 8.3.0 8.3.0 8.3.0 8...0 8...0 8...0 8...0 8...0 8...0 /.0.0 /.0.0 /.0.0

S&ES&ES&ES&ES&ES&E&4P*-S&E &4P*-S&E &4P*-S&E S&ES&E&4P*-S&E &4P*-S&E &4P*-S&E -

SP-.1 SP-.1 SP-.1 SP-41 SP-.1 SP-.2 SP-.2 SP-.2

SP-080./5 S1-082018 SP-08063/ SP-080./5 S1-0823/8 SP-080495 S1-082386 SP-080652 SP-08077. S1-08311. SP-080783 S1-083.65 SP-080778 S1-08.33.

22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278

0037 003/ 00.1 0043 00.3 00.5 00./ 0051

3 2 3 5 2 1

e$-/ e$-/ e$-/ Rel-9 e$-/ e$-/ e$-/ e$-/

/.0.0 /.0.0 /.0.0 9.0.0 /.1.0 /.1.1 /.1.1 /.1.1

/.1.0 /.1.0 /.1.0 9.1.0 /.1.1 /.2.0 /.2.0 /.2.0

&4P*-S&E &4P*-S&E &4P*-S&E A'P(-SA) &4P*-S&E &4P*-S&E TE4/ &4P*-S&E

3GPP

!elease "#

33

3GPP TS ##$#%& '"#$($( (#("")"#

.han)e history
SP-.2 SP-.2 SP-.2 SP-.2 SP-.2 SP-.. SP-.. SP-.. SP-.5 SP-.6 SP-.6 SP-.7 SP-./ SP-./ SP-./ SP-./ SP-./ SP-./ SP-50 SP-50 SP-50 SP-50 SP-50 SP-080783 S1-08.368 SP-080783 S1-08.06/ SP-080783 S1-08..25 SP-080783 S1-08..1. SP-080783 S1-08.363 SP-0/0.17 S10/1153re7 SP-0/0371 S1-0/116/ SP-0/0371 S1-0/1352 SP-0/0.76 S1-0/3272 SP-0/08.3 S1-0/.500 SP-0/0/0. SP-100185 S1-100236 SP-100575 S1-102056 SP-100582 S1-102032 SP-100582 S1-102303 SP-100582 S1-102307 SP-100582 S1-102308 SP-100582 S1-10230/ SP-100802 S1-103263 SP-100802 S1-103266 SP-100802 S1-1032.2 SP-100802 S1-103321 SP-100802 S1-103323 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 22.278 005. 0055 0056 0057 0058 0062 0066 0067 0060 0070 0071 0080 008/ 0083 008. 0086 0085 0087 00/0 00/1 00/3 00/5 00/7 1 3 1 1 2 . 2 7 5 1 1 2 2 1 2 3 1 e$-/ e$-/ e$-/ e$-/ e$-/ e$-/ e$-/ e$-/ e$-/ e$-/ + ? 6 + ? & & & & ) Ser7ice i' EPS EPS !%erati!'a$ "e%$!@<e't a'" <!(i$it@ !%ti<iFati!' e<!7a$ !5 cha%ter 6.1.2 a'" 6.1.3 E'ha'ce" &*6S) e;uire<e't# ?a#ic #u%%!rt 5!r <u$tiacce## &""i'3 a' a%%e'"i0 2ith )M+ u#e# ca#e# t! 22.278 &cce## Tech'!$!3@ Se$ecti!' acr!## PLM*# M!7e #e'te'ce a(!ut '!'-3GPP acce## )re;ue'c@ !5 Sca''i'3 5!r 6i55ere't &cce## Tech'!$!3ie# &$i3'<e't a(!ut acce%ti'31re9ecti'3 +S)? 8'e acti7e %!$ic@ ru$e#et i' &*6S) &""i'3 !5 4)8M e;uire<e't# e;uire<e't# 5!r )i0e" M!(i$e 4'ter2!r>i'3 e<!7a$ !5 re5ere'ce# t! 3GPP 8S& &""i'3 a :(e)*? u#e ca#e t! )M+ u#e ca#e# &""i'3 a &%%$icati!' M!(i$it@ u#e ca#e t! )M+ u#e ca#e# +$ari5icati!'# !' )M+ u#e ca#e# &""i'3 a +!<<!' Au!ta u#e ca#e t! )M+ u#e ca#e# *e2 e;uire<e't# 5!r )i0e" M!(i$e +!'7er3e'ce #ce'ari! +$ari5@i'3 the #ce'ari!# #u%%!rte" (@ )M+ i'ter2!r>i'3, i'c$u"i'3 (ui$"i'3 ($!c> 44 *e2 e;uire<e't# 5!r E'ter%ri#e 4'ter2!r>i'3 #ce'ari! 3GPP EP+ (a#e" )M+ U#e ca#e# 5!r ??&4 ?ui$"i'3 ?$!c> 3 - +!'7er3e" #ce'ari! E7!$7e" Pac>et +!re #u%%!rt 5!r 5i0e" acce## LTE $!3! cha'3e" i't! LTE &"7a'ce" $!3! Sce'ari!# 5!r 4'ter2!r>i'3 (et2ee' M!(i$e 8%erat!r# a'" &%%$icati!' Pr!7i"er# *e2 re;uire<e't# 5!r M8S&P U#e ca#e# 5!r M8S&P )i0e" ?r!a"(a'" &cce## *et2!r> e;uire<e't# 5!r ??&4 ?ui$"i'3 ?$!c> 3 - +!'7er3e't #ce'ari! U#er c!'#e't-(a#e" char3i'3 u#e ca#e 5!r M8S&P *!'-c!$$a(!rati!' re;uire<e't# 5!r M8S&P M8S&P - !a<i'3 L?8 &rchitecture +!rrecti!' E'" U#er Ser7ice eacha(i$it@ 7ia *!'-3GPP &cce## Tech'!$!3ie# /.1.1 /.1.1 /.1.1 /.1.1 /.1.1 /.2.0 /.2.0 /.2.0 /.3.0 /...0 /.2.0 /.2.0 /.2.0 /.2.0 /.2.0 /.3.0 /.3.0 /.3.0 /...0 /.5.0 TE4/ TE4/ TE4/ TE4/ TE4/ S&ES S&ES S&ES &4P*-S&E e&*6S)

e$-10 ? e$-10 ? e$-10 & e$-11 ? e$-11 ? e$-11 6 e$-11 ? e$-11 ? e$-11 ) e$-11 ? e$-11 ? e$-11 ? e$-11 ?

/.5.0 10.0.0 4)8M 10.0.0 10.1.0 ??&4 10.1.0 10.2.0 TE410 10.1.0 11.0.0 ??&4 10.1.0 11.0.0 ??&4 10.1.0 11.0.0 ??&4 10.1.0 11.0.0 ??&4 10.1.0 11.0.0 ??&4 11.0.0 11.1.0 ??&4 11.0.0 11.1.0 ??&4 11.0.0 11.1.0 ??&4 11.0.0 11.1.0 ??&4 11.0.0 11.1.0 ??&4 11.1.0 11.1.1 -

SP-51 SP-51 SP-51

SP-110165 S1-1102/7 SP-110165 S1-110.0. SP-110165 S1-110302

22.278 22.278 22.278

00/. 00/8 0100

2 3 2

e$-11 ? e$-11 ? e$-11 ?

11.1.0 11.2.0 M8S&P 11.1.0 11.2.0 M8S&P 11.1.0 11.2.0 M8S&P

SP-51 SP-52 SP-52 SP-53 SP-5.

SP-11016/ S1-110181 SP-110372 S1-111223 SP-110372 S1-111.12 SP-110575 S1-112357

22.278 22.278 22.278 22.278

00// 0101 0103 0110 0106

2 2 2 3 3

e$-11 ? e$-11 ? e$-11 ? e$-11 ) e$-12 ?

11.1.0 11.2.0 ??&4 11.2.0 11.3.0 M8S&P 11.2.0 11.3.0 M8S&P 11.3.0 11...0 M8S&P 11...0 12.0.0 SMU )#

SP-110883 S1-11326.r 22.278

3GPP