Vous êtes sur la page 1sur 51

3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control

over ! reference point Technical Specification V11.7.0 (2012-12) " elease ##$

3GPP TS 29.214

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, QoS, Charging, Po i!"

3GPP Postal address 3GPP support office address


#$0 %o&'( )(* L&!io (* - So+hia ,n'i+o i* Va -onn( - .%,/CE T( .0 133 4 92 94 42 00 .a20 133 4 93 #$ 47 1#

&nternet
h''+033444.3g++.org

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"& currently bein 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 %&'%#( )##'*'+ "%+#%,#%$

Con'(n'*
1ontents....................................................................................................................................................3 7oreword...................................................................................................................................................8 , "cope......................................................................................................................................................9 * /eferences..............................................................................................................................................9 3 :efinitions and abbreviations.................................................................................................................;
3., :efinitions..............................................................................................................................................................; 3.* .bbreviations.........................................................................................................................................................<

8 /( reference point..................................................................................................................................<
8., Overview................................................................................................................................................................< 8.* /( reference model................................................................................................................................................= 8.3 7unctional elements...............................................................................................................................................> 8.8 P11 procedures over /( reference point.............................................................................................................,+

9 /( protocol...........................................................................................................................................,=
9., Protocol support...................................................................................................................................................,= 9.* &nitiali!ation- maintenance and termination of connection and session...............................................................,= 9.3 /( specific .?Ps.................................................................................................................................................,= 9.8 /( re@used .?Ps..................................................................................................................................................3+ 9.9 /( specific 2(perimental@/esult@1ode .?P values............................................................................................33 9.; /( messa es.........................................................................................................................................................38

.., Provision of "ervice &nformation at P@1"17....................................................................................3= ..* 2nablin of &P 7lows........................................................................................................................3> ..3 "upport for "&P for#in ....................................................................................................................8+
..3., P11 rule provisionin for early media for for#ed responses...........................................................................8+ ..3.* 3pdatin the provisioned P11 rules at the final answer.................................................................................8+

..8 'otification of .7 "i nallin Transmission Path "tatus..................................................................8, ..9 &ndication of 2mer ency "ession.....................................................................................................8, ..; 'otification &P@1.' Type 1han e .................................................................................................8, ..< "upport for 2arly "ession disposition ":P......................................................................................8,
..<., General.............................................................................................................................................................8, ..<.* "ervice &nformation Provisionin for 2arly Media..........................................................................................8, ..<.3 3pdatin the Provisioned "ervice &nformation when :ialo ue is established................................................8* ..= Provision of "i nallin 7low &nformation at P@1"17........................................................................................83

..> Aandlin of MP" "ession.................................................................................................................83 0., 7ormat of a flow identifier................................................................................................................88


0.,., General............................................................................................................................................................88 0.,.* :erivation of 7low &dentifiers from ":P........................................................................................................89

0.* 2(ample ,.........................................................................................................................................89 0.3 2(ample *.........................................................................................................................................8; 0.8 2(ample 3 without media components.............................................................................................8< 0.9 2(ample 8.........................................................................................................................................8=

3GPP

elease ##

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

.or(4or)
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 followsB ?ersion (.y.! whereB ( the first di itB , presented to T"G for informationC * presented to T"G for approvalC 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.

3GPP

elease ##

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

S!o+(

The present document provides the sta e 3 specification of the /( reference point for the present release. The functional reDuirements and the sta e * specifications of the /( reference point are contained in 3GPP T" *3.*+3 E*F. The /( reference point lies between the .pplication 7unction and the Policy and 1har in /ule 7unction. Ghenever it is possible the present document specifies the reDuirements for the protocol by reference to specifications produced by the &2T7 within the scope of :iameter. Ghere this is not possible- e(tensions to :iameter are defined within the present document.

%(5(r(n!(*
/eferences are either specific (identified by date of publication andHor edition number or version number) or non@specific. 7or a specific reference- subseDuent 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. E,F E*F E3F E8F E9F E;F E<F E=F E>F E,+F E,,F E,*F E,3F E,8F E,9F 3GPP T/ *,.>+9B I?ocabulary for 3GPP "pecificationsI. 3GPP T" *3.*+3B IPolicy and 1har in 1ontrol architectureI. void void 3GPP T" *>.*+>B IPolicy control over GD interfaceI- latest /el@; version. void 3GPP T" *>.*,,B I/( &nterface and /(HG( si nallin flowsI- latest /el@; version. 3GPP T" *>.*,*B IPolicy and 1har in 1ontrol (P11)C /eference pointsI. 3GPP T" *>.*,3B IPolicy and 1har in 1ontrol si nallin flows and Jo" parameter mappin I. &2T7 /71 39==B I:iameter 0ase ProtocolI. &2T7 /71 399;B I"ession :escription Protocol (":P) 0andwidth Modifiers for /TP 1ontrol Protocol (/T1P) 0andwidthI. &2T7 /71 8++9B I:iameter 'etwor# .ccess "erver .pplicationI. &2T7 /71 89;;B I":PB "ession :escription ProtocolI. &2T7 /71 8++;B I:iameter 1redit 1ontrol .pplicationI. 2T"& T" ,=3 +,< v3.*.,B ITelecommunications and &nternet 1onver ed "ervices and Protocols for .dvanced 'etwor#in (T&"P.')C /esource and .dmission 1ontrolB :&.M2T2/ protocol for session based policy set@up information e(chan e between the .pplication 7unction (.7) and the "ervice Policy :ecision 7unction ("P:7)C Protocol specificationI. 3GPP T" *3.**=B I&P Multimedia "ubsystem (&M")C "ta e *I. 3GPP T" *8.**>B I&P Multimedia 1all 1ontrol Protocol based on "&P and ":PC "ta e 3I.

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

E,;F E,<F

3GPP

elease ##

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

E,=F E,>F E*+F E*,F E**F E*3F E*8F E*9F E*;F E*<F E*=F E*>F E3+F E3,F E3*F E33F

&2T7 /71 3*;8B I.n OfferH.nswer Model with the "ession :escription Protocol (":P)I. ?oid &2T7 /71 3,;*B I/adius and &Pv;I. &2T7 /71 9+3,B I. 3niform /esource 'ame (3/') for 2mer ency and Other Gell@%nown "ervicesI. ?oid 3GPP T" 3*.*8+B ITelecommunication mana ementC 1har in mana ementC 1har in architecture and principlesI. 3GPP T" 3*.*>>B ITelecommunication mana ementC 1har in mana ementC :iameter char in applicationsI. 3GPP T" *>.**>B I1( and :( interfaces based on the :iameter protocolC Protocol detailsI 3GPP T" *8.*>*B I&P Multimedia (&M) 1ore 'etwor# (1') subsystem 1entrali!ed "ervices (&1")C "ta e 3I. &2T7 /71 3>9> (:ecember *++8)B IThe 2arly "ession :isposition Type for the "ession &nitiation Protocol ("&P)I. 3GPP T" *3.3=+B I&M" /estoration ProceduresI. 3GPP T" *3.339B I3ser :ata 1onver ence (3:1)C Technical reali!ation and information flowsC "ta e *I. 3GPP T" *>.339B I3ser :ata 1onver ence (3:1)C 3ser :ata /epository .ccess Protocol over the 3d interfaceC "ta e 3I. 3GPP T" **.,93B IMultimedia Priority "erviceI. ?oid 3GPP T" *>.*<8B I3GPP 2volved Pac#et "ystem. 2volved GP/" Tunnellin Protocol for 2P" (GTPv*)I.

6(5ini'ion* an) a--r(7ia'ion*

3.1 6(5ini'ion*
7or the purposes of the present document- the terms and definitions iven in 3GPP T/ *,.>+9 E,F and the followin applyB Application Function (AF): element offerin application(s) that use &P bearer resources 'OT2B One e(ample of an .7 is the P@1"17 of the &M 1' subsystem.

AF Session: application level session established by an application level si nallin protocol offered by the .7 that reDuires a session set@up with e(plicit session description before the use of the service. 'OT2B One e(ample of an application session is an &M" session.

Attribute-Value Pair (AVP): "ee /71 39== E,+F- corresponds to an &nformation 2lement in a :iameter messa e. binding: P1/7 process of associatin &P flows described in .7 "ervice &nformation with &P@1.' bearers. IP-CAN bearer: &P transmission path of defined capacity- delay and bit error rate- etc. "ee 3GPP T" *,.>+9 E,F for the definition of bearer.

3GPP

elease ##

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

IP-CAN session: association between a 32 and an &P networ# (for GP/"- .P'). The association is identified by one 32 &Pv8 address andHor one &Pv; prefi( to ether with a 32 identity information- if available- and a P:' represented by a P:' &: (e. . an .P'). .n &P@1.' session incorporates one or more &P@1.' bearers. "upport for multiple &P@1.' bearers per &P@1.' session is &P@1.' specific. .n &P@1.' session e(ists as lon as the related 32 &Pv8 address andHor &Pv; prefi( are assi ned and announced to the &P networ#. IP flow: unidirectional flow of &P pac#ets with the same source &P address and port number and the same destination &P address and port number and the same transport protocol Port numbers are only applicable if used by the transport protocol. MPS session: . session for which priority treatment is applied for allocatin and maintainin radio and networ# resources to support the Multimedia Priority "ervice (MP"). MP" is defined in 3GPP T" **.,93 E3,F. pac et flow: . specific user data flow carried throu h the P127. . pac#et flow can be an &P flow. PCC rule: set of information enablin the detection of a service data flow and providin parameters for policy control andHor char in control ser!ice infor"ation: set of information conveyed from the .7 to the P1/7 over the /( interface to be used as a basis for P11 decisions at the P1/7- includin information about the .7 session (e. . application identifier- type of mediabandwidth- &P address and port number) ser!ice data flow: .n a re ate set of pac#et flows.

3.2 ,--r(7ia'ion*
7or the purpose of the present document- the abbreviations iven in 3GPP T/ *,.>+9 E,F and the followin applyB .:1 .7 ."P .?P 1/7 &P@1.' MP" P11 P127 P1/7 P:7 P@1"17 Jo" ":7 "P/ T:7 3:1 32 3:/ .pplication :etection and 1ontrol .pplication 7unction .pplication "ervice Provider .ttribute ?alue Pair 1har in /ules 7unction &P 1onnectivity .ccess 'etwor# Multimedia Priority "ervice Policy and 1har in 1ontrol Policy and 1har in 2nforcement 7unction Policy and 1har in /ule 7unction Policy :ecision 7unction Pro(y@1all "ession 1ontrol 7unction Juality of "ervice "ervice :ata 7low "ubscriber Profile /epository Traffic :etection 7unction 3ser :ata 1onver ence 3ser 2Duipment 3ser :ata /epository

%2 r(5(r(n!( +oin'

4.1 87(r7i(4
The /( reference point is used to e(chan e application level session information between the Policy and 1har in /ules 7unction (P1/7) and the .pplication 7unction (.7). .s defined in the sta e * specifications (3GPP T" *3.*+3 E*F)- this information is part of the input used by the P1/7 for the Policy and 1har in 1ontrol (P11) decisions. The P1/7 e(chan es the P11 rules with the Policy and 1har in 2nforcement 7unction (P127) and Jo" rules with the 0earer 0indin and 2vent /eportin 7unction (002/7) as specified in 3GPP T" *>.*,* E=F. "i nallin flows related to the both /( and G( interfaces are specified in 3GPP T" *>.*,3 E>F.

3GPP

elease ##

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

4.2 %2 r(5(r(n!( 9o)(


The /( reference point is defined between the P1/7 and the .7. The relationships between the different functional entities involved are depicted in fi ure 8.,. and 8.*.

Su1scription Profile epository "SP $

S+

/pplication 0unction "/0$ 2nline Charging System "2CS$

Policy and Charging ules 0unction "PC 0$ S"

G22

S)

G2 Polic$ and C(arging &nforce"ent Function

%earer %inding and &!ent 'eporting Function

G" 2ffline Charging System "20CS$

(%%&'F)
AN-#atewa$

Traffic 3etection 0unction "T30$

(PC&F)
G:

#atewa$

0igure ('#4 ! reference point at the Policy and Charging Control "PCC$ architecture with SP 'OT2 ,B The P127 may be enhanced with T:7 capabilities. Gith the 3:1@based architecture- as defined in 3GPP T" *3.339 E*>F and applied in 3GPP T" *3.*+3 E*F- the 3:/ replaces "P/ and the 3d reference point provides access to the subscription data in the 3:/. The 3d interface as defined in 3GPP T" *>.339 E3+F is the interface between the P1/7 and the 3:/.The relationships between the different functional elements are depicted in fi ure 8.*. Ghen 3:1 architecture is used- "P/ and "p- whenever mentioned in this document- are replaced by 3:/ and 3d.

3GPP

elease ##

& /pplication 0unction "/0$

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

6ser 3ata epository "63 $

U)

2nline Charging System "2CS$

Policy and Charging ules 0unction "PC 0$ S"

G22

S)

G2 Polic$ and C(arging &nforce"ent Function

%earer %inding and &!ent 'eporting Function

G"

(%%&'F)
AN-#atewa$

Traffic 3etection 0unction "T30$

(PC&F)
G:

#atewa$

2ffline Charging System "20CS$

0igure ('%4 ! reference point at the Policy and Charging Control "PCC$ architecture with 63 'OT2 *B The details associated with the "p reference point are not specified in this /elease. The "P/$s relation to e(istin subscriber databases is not specified in this /elease. 'OT2 3B The 3:1 .pplication &nformational Model related to the P1/7 is not specified in this /elease. 'OT2 8B The P127 may be enhanced with T:7 capabilities. 'OT2 9B P127 is located in the Gateway node implementin the &P access to the P:'. /efer to .nne(es of 3GPP T" *3.*+3 E*F for application to specific &P@1.' types. 'OT2 ;B /efer to .nne(es ..9 and A.* of 3GPP T" *3.*+3 E*F for application of .'@Gateways.

4.3 .&n!'iona ( (9(n'*


4.3.1 ,.
The .7 is an element offerin applications that reDuire the Policy and 1har in 1ontrol of traffic plane resources (e. . 3MT" P" domainHGP/" domain resources). One e(ample of an application function is the P@1"17. The .7 shall use the /( reference point to provide session information to the P1/7. 'OT2B The .7s may be deployed by the same operator offerin the &P@1.' or may be provided by e(ternal third party service provider.

4.3.2 PC%.
The P1/7 (Policy 1ontrol and 1har in /ules 7unction) is a functional element that encompasses policy control decision and flow based char in control functionalities. These * functionalities are the herita e of the release ; lo ical entities P:7 and 1/7 respectively. The P1/7 provides networ# control re ardin the service data flow detectionatin - Jo" and flow based char in (e(cept credit mana ement) towards the P127. The P1/7 receives session and media related information from the .7 and informs .7 of traffic plane events.

3GPP

elease ##

#+

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The P1/7 may chec# that the service information provided by the .7 is consistent with the operator defined policy rules before storin the service information. The service information shall be used to derive the Jo" for the service. The P1/7 may reject the reDuest received from the .7 and as a result the P1/7 shall indicate- in the response to the .7the service information that can be accepted by the P1/7. The P1/7 may use the subscription information as basis for the policy and char in control decisions. The subscription information may apply for both session based and non@session based services. The subscription specific information for each service may contain e. . ma( Jo" class and ma( bit rate. &f the .7 reDuests it- the P1/7 shall report &P@1.' session events (includin bearer events and events on .7 si nallin transport) to the .7 via the /( reference point. The P1/7 P11HJo" /ule decisions may be based on one or more of the followin B @ @ @ @ @ the session and media related information obtained from the .7 via the /( reference pointC the bearer and subscriber related information obtained from the P127 over the G( reference pointC the bearer and subscriber related information obtained from the 002/7 over the G(( reference pointC subscriber and service related data the P1/7 may be aware of by confi uration or throu h the "p reference pointC pre@confi ured information in the P1/7. The details associated with the "p reference point are not specified in this /elease. The "P/$s relation to e(istin subscriber databases is not specified in this /elease.

'OT2B

The P1/7 shall provision P11HJo" /ules to the P127H002/7 via the G(HG(( reference point.

4.4 PCC +ro!()&r(* o7(r %2 r(5(r(n!( +oin'


4.4.1 ;ni'ia Pro7i*ioning o5 S(**ion ;n5or9a'ion
Ghen a new .7 session is bein established and media information for this .7 session is available at the .7 and the related media reDuire P11 supervision- the .7 shall open an /( :iameter session with the P1/7 for the .7 session usin an ..@/eDuest command. The .7 shall provide the full &P address of the 32 usin either 7ramed@&P@.ddress .?P or 7ramed@&Pv;@Prefi( .?P- and the correspondin "ervice &nformation within Media@1omponent@:escription .?P(s). The .7 shall not include circuit@switched bearer related media in the service information sent to the P1/7. The .7 shall indicate to the P1/7 as part of the Media@1omponent@:escription whether the media &P flow(s) should be enabled or disabled with the 7low@"tatus .?P. 'OT2 ,B The .7 does not need to open an /( :iameter session with the P1/7- if the ":P payload is only proposin to use a circuit@switched bearer (i.e. IcKI line set to IP"T'I and an ImKI line set to IP"T'Irefer to 3GPP T" *8.*>* E*;F). 'OT2 *B The /( :iameter session used for an .7 session is different from the /( :iameter session possibly used for the notifications of the status of the .7 si nallin transmission path. . new /( :iameter session is established for each new .7 session. The .7 may include the .7@.pplication@&dentifier .?P into the ..@/eDuest in order to indicate the particular service that the .7 session belon s to. This .?P can be provided at both .7 session level- and Media@1omponent@:escription level. Ghen provided at both levels- the .7@.pplication &dentifier provided within the Media@1omponent@:escription .?P will have precedence. The .7 may include the .7@1har in @&dentifier .?P into the ..@/eDuest for char in correlation purposes. The .7 may also include the "pecific@.ction .?P to reDuest notification for certain user plane events- e. . bearer termination. The .7 may include the "ervice@3/' .?P in order to indicate that the new .7 session relates to emer ency traffic. &f the P1/7 receives the "ervice@3/' .?P indicatin an emer ency session- the P1/7 may apply special policies- for instance prioritisin service flows relatin to the new .7 session or allowin these service flows free of char e.

3GPP

elease ##

##

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The .7 may include the MP"@&dentifier .?P in order to indicate that the new .7 session relates to an MP" session. &f the P1/7 receives the MP"@&dentifier .?P indicatin an MP" session- the P1/7 may ta#e specific actions on the correspondin &P@1.' to ensure that the MP" session is prioriti!ed as specified in 3GPP T" *>.*,* E=F. 7or Multimedia Priority "evice handlin - see .nne( ..>. &f the .7 provides service information that has been fully ne otiated (e. . based on the ":P answer)- the .7 may include the "ervice@&nfo@"tatus .?P set to 7&'.5L"2/?&12L&'7O/M.T&O'. &n this case the P1/7 shall authori!e the session and provision the correspondin P11HJo" rules to the P127H002/7. The .7 may additionally provide preliminary service information not fully ne otiated yet (e. . based on the ":P offer) at an earlier sta e. To do so- the .7 shall include the "ervice@&nfo@"tatus .?P with the value set to P/25&M&'./M "2/?&12 &'7O/M.T&O'. 3pon receipt of such preliminary service information- the P1/7 shall perform an early authori!ation chec# of the service information. 7or GP/"- the P1/7 shall not provision P11 rules towards the P127 unsolicitedly. Aowever- the P1/7 may authori!e a P11HJo" rule reDuest received from the P127H002/7 as per 3GPP T" *>.*,* E=F. 7or sponsored data connectivity- the .7 shall provide the application service provider identity and the sponsor identity to the P1/7 byincludin the .pplication@"ervice@Provider@&dentity .?P and the "ponsor@&dentity .?P in the "ponsored@1onnectivity@:ata .?P in the ..@/eDuest. 'OT2 3B The relationship between the .7 and "ponsor is out of scope of this specification. . sin le .7 can serve multiple ."Ps and multiple sponsors- .n ."P can also be a sponsor. To support the usa e monitorin of sponsored data connectivity- the .7 may also include the Granted@"ervice@3nit .?P in the "ponsored@1onnectivity@:ata .?P and the "pecific@.ction .?P set to the value 3".G2L/2PO/T in the ..@/eDuest to reDuest notification when the usa e threshold has been reached. 'OT2 8B &f the .7 is in the user plane- the .7 can handle the usa e monitorin and therefore it is not reDuired to provide a usa e threshold to the P1/7 as part of the sponsored data connectivity information. &f the 32 is roamin with the visited access case and the .7 is located in the AP5M' or roamin with the home routed case and operator policies do not allow accessin the sponsored data connectivity with this roamin case- the A@P1/7 shall reject the service reDuest indicatin 3'.3TAO/&N2:L"PO'"O/2:L:.T.L1O''21T&?&TM to the .7. &f the 32 is roamin with the visited access case and the .7 is located in the ?P5M'- the ?@P1/7 shall reject the service reDuest indicatin 3'.3TAO/&N2:L"PO'"O/2:L:.T.L1O''21T&?&TM to the .7. &f the 32 is in the non@roamin case or roamin with the home routed case and the operator policies allow accessin the sponsored data connectivity with this roamin case- the followin procedures applyB @ &f the P127 does not support sponsored connectivity and the reDuired reportin level for that service indicates a sponsored connectivity level accordin to 3GPP T" *>.*,* E=F- clause 8.9.*+- then the P1/7 shall reject the reDuest indicatin /2J32"T2:L"2/?&12L'OTL.3TAO/&N2:. @ &f the P127 supports sponsored data connectivity feature or the reDuired reportin level is different from sponsored connectivity level as described in 3GPP T" *>.*,*E=F- then the P1/7- based on operator policiesshall chec# whether it is reDuired to validate the sponsored connectivity data. &f it is reDuired- it shall perform the authori!ations based on sponsored data connectivity profiles. &f the authori!ation fails- the P1/7 responds to the .7 with an ..@.nswer includin the 2(perimental@/esult@1ode .?P set to the value 3'.3TAO/&N2:L"PO'"O/2:L:.T.L1O''21T&?&TM. The profile may include a list of .pplication "ervice Providers and their applications per sponsor. 'OT2 9B &f the .7 is in the operator$s networ# and is based on the O".HParlay@O GG- the P1/7 is not reDuired to verify that a trust relationship e(ists between the operator and the sponsors. Ghen the P1/7 receives an initial ..@/eDuest from the .7- the P1/7 shall perform session bindin as described in 3GPP T" *>.*,3 E>F. To allow the P1/7 to identify the &P@1.' session for which this reDuest applies- the .7 shall provide either the 7ramed@&P@.ddress or the 7ramed@&Pv;@Prefi( containin the full &P address applicable to an &P flow or &P flows towards the 32. &n case of private &P address bein used- the .7 may provide P:' information if available in the 1alled@"tation@&d .?P for session bindin . The .7 may provide the domain identity in the &P@:omain@&d .?P for session bindin .

3GPP

elease ##

#%

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

'OT2 ;B The &P@:omain@&d .?P is helpful in the followin scenarioB Githin a P5M'- there are several separate &P address domains- with P127(s) that allocate &Pv8 &P addresses out of the same private address ran e to 32s. The same &P address can thus be allocated to 32s served by P127s in different address domains. &f one P1/7 controls several P127s in different &P address domains- the 32 &P address is thus not sufficient for the session bindin . .n .7 can serve 32s in different &P address domains- either by havin direct &P interfaces to those domains- or by havin interconnections via '.Ts in the user plane between P127s and the .7. &f a '.T is used- the .7 obtains the &P address allocated to the 32 via application level si nallin and supplies it for the session bindin as 7ramed@&P@.ddress to the P1/7. The .7 supplies an &P@:omain@&d value denotin the &P address domain behind the '.T in addition. The .7 can derive the appropriate value from the source address (allocated by the '.T) of incomin user plane pac#ets. 'OT2 <B Ghen the scenario described in 'OT2 ; applies and the .7 is a P@1"17 it is assumed that the P@1"17 has direct &P interfaces to the different &P address domains and that no '.T is located between P@GG and P@1"17. Aow a non@&M" .7 obtains the 32 private &P address to be provided to the P1/7 is out of scope of the present releaseC it is unspecified how to support applications that use a protocol that does not retain the ori inal 32$s private &P address. &f the P1/7 fails in e(ecutin session bindin - the P1/7 responds to the .7 with an ..@.nswer includin the 2(perimental@/esult@1ode .?P set to the value &P@1.'L"2""&O'L'OTL.?.&5.052. 7urther details on how the P1/7 identifies suitable &P@1.' sessions can be found in the bindin mechanism described in 3GPP T" *>.*,3 E>F. &f the reDuest contains Media@1omponent@:escription .ttribute@?alue Pair(s) (.?P(s)) the P1/7 shall store the received "ervice &nformation. The P1/7 shall process the received "ervice &nformation accordin to the operator policy and may decide whether the reDuest is accepted or not. The P1/7 may ta#e the priority information within the /eservation@Priority .?P into account when ma#in this decision. &f the service information provided in the ..@ /eDuest command is rejected (e. . the subscribed uaranteed bandwidth for a particular user is e(ceeded)- the P1/7 shall indicate in the ..@.nswer the cause for the rejection with the 2(perimental@/esult@1ode .?P set to the value /2J32"T2:L"2/?&12L'OTL.3TAO/&N2:. The P1/7 may additionally provide the acceptable bandwidth within the .cceptable@"ervice@&nfo .?P. To allow the P1/7 and P127 to perform P11 rule authori!ation and bearer bindin for the described service &P flowsthe .7 shall supply both source and destination &P addresses and port numbers within the 7low@:escription .?P- if such information is available. 'OT2B &n ":P source port information is usually not available.

The .7 may specify the /eservation@Priority .?P at reDuest level in the ..@/eDuest in order to assi n a priority to the .7 "ession as well as specify the /eservation@Priority .?P at the media@component@description .?P level to assi n a priority to the &P flow. The presence of the /eservation@Priority in both levels does not constitute a conflict as they each represent different types of priority. "pecifically the /eservation@Priority at the ..@/eDuest level provides the relative priority for a session while the /eservation@Priority at the media@component@description level provides the relative priority for an &P flow within a session. &f the /eservation@Priority .?P is not specified the reDuested priority is :27.35T (+). The .7 may reDuest notifications of specific &P@1.' session events throu h the usa e of the "pecific@.ction .?P in the ..@/eDuest command. The P1/7 shall ma#e sure to inform the .7 of the reDuested notifications in the event that they ta#e place. The .7 may include the /(@/eDuest@Type .?P set to &'&T&.5L/2J32"T in the ../. The P1/7 shall chec# whether the received "ervice &nformation reDuires P11HJo" /ules to be created and provisioned andHor authori!ed Jo" to be provisioned. Provisionin of P11HJo" /ules and .uthori!ed Jo" to the P127H002/7 shall be carried out as specified at 3GPP T" *>.*,* E=F. The P1/7 shall reply with an ..@.nswer to the .7. The ac#nowled ement towards the .7 should ta#e place before or in parallel with any reDuired P11 /ule provisionin towards the P127 and shall include the .ccess@'etwor#@ 1har in @&dentifier(s) and may include the .ccess@'etwor#@1har in @.ddress .?P- if they are available. The ..@ .nswer messa e shall also include the &P@1.'@Type .?P- if such information is available. &n that case- the ..@ .nswer messa e shall also include the /.T@Type .?P when applicable for the specific &P@1.' Type (e. . 3GPP &P@ 1.' Type). &n addition- if &P flow mobility applies to service data flows as specified in 3GPP T" *>.*,* E=F- such that

3GPP

elease ##

#3

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

a subset of the flows within the .7 session are affected- the P1/7 shall also include &P@1.'@type and /.T@type information (if applicable) to &P flow mobility related flows- if such information is available. The &P flow mobility affected service data flows are included within the 7lows .?P at command level. &f the P1/7 needs to terminate the /( session before it has sent the .. .nswer- the P1/7 shall send the .. .nswer immediately and before the ." /eDuest. The behaviour when the .7 does not receive the .. .nswer- or when it arrives after the internal timer waitin for it has e(pired- or when it arrives with an indication different than :&.M2T2/L"3112""- are outside the scope of this specification and based on operator policy.

4.4.2 Mo)i5i!a'ion o5 S(**ion ;n5or9a'ion


The .7 may modify the session information at any time (e. . due to an .7 session modification or internal .7 tri er) by sendin an ..@/eDuest command to the P1/7 containin the Media@1omponent@:escription .?P(s) with the updated "ervice &nformation. The .7 shall send an ..@/eDuest command to the P1/7- only after the previous ..@ /eDuest has been ac#nowled ed. &f the .7 provides service information that has been fully ne otiated (e. . based on the ":P answer)- the .7 may include the "ervice@&nfo@"tatus .?P set to 7&'.5L"2/?&12L&'7O/M.T&O'. &n this case the P1/7 shall authori!e the session and provision the correspondin P11 rules to the P127. The .7 may additionally provide preliminary service information not fully ne otiated yet (e. . based on the ":P offer) at an earlier sta e. To do so- the .7 shall include the "ervice@&nfo@"tatus .?P with the value set to P/25&M&'./M "2/?&12 &'7O/M.T&O'. 3pon receipt of such preliminary service information- the P1/7 shall perform an early authori!ation chec# of the service information. 7or GP/"- the P1/7 shall not provision P11 rules towards the P127 unsolicitedly. Aowever- the P1/7 may authori!e a P11HJo" rule reDuest received from the P127H002/7 as per 3GPP T" *>.*,* E=F. The .7 may include the /(@/eDuest@Type .?P set to 3P:.T2L/2J32"T in the ../. The .7 may include the MP"@&dentifier .?P in order to indicate that the modified .7 session relates to an MP" session. &f the P1/7 receives the MP"@&dentifier .?P- it may ta#e specific actions on the correspondin &P@1.' to ensure that the MP" session is prioriti!ed as defined in 3GPP T" *>.*,* E=F. 7or Multimedia Priority "evice handlin see .nne( ..>. 7or sponsored data connectivity- the .7 shall provide the application service provider identity and the sponsor identity to the P1/7 by includin .pplication@"ervice@Provider@&dentity .?P and the "ponsor@&dentity .?P in the "ponsored@ 1onnectivity@:ata .?P in the ..@/eDuest. To support the usa e monitorin of sponsored data connectivity- the .7 may also include the Granted@"ervice@3nit .?P in the "ponsored@1onnectivity@:ata .?P in the ..@/eDuest. 'OT2B &f the .7 is in the user plane- the .7 can handle the usa e monitorin and therefore it is not reDuired to provide a usa e threshold to the P1/7 as part of the sponsored data connectivity information.

The P1/7 shall process the received "ervice &nformation accordin the operator policy and may decide whether the reDuest is accepted or not. &f the updated "ervice &nformation is not acceptable (e. . subscribed uaranteed bandwidth for a particular user is e(ceeded)- the P1/7 shall indicate in the ..@.nswer the cause for the rejection with the 2(perimental@/esult@1ode .?P set to the value /2J32"T2:L"2/?&12L'OTL.3TAO/&N2:. The P1/7 may additionally provide the acceptable bandwidth within the .cceptable@"ervice@&nfo .?P. &f accepted- the P1/7 shall update the "ervice &nformation with the new information received. :ue to the updated "ervice &nformation- the P1/7 may need to create- modify or delete the related P11 rules and provide the updated information towards the P127 followin the correspondin procedures specified at 3GPP T" *>.*,* E=F. The procedures to update the .uthori!ed Jo" for the affected &P@1.' bearer are also specified at 3GPP T" *>.*,* E=F. The P1/7 shall reply with an ..@.nswer to the .7. The ac#nowled ement towards the .7 should ta#e place before or in parallel with any reDuired P11 /ule provisionin towards the P127 and shall include the .ccess@'etwor#@ 1har in @&dentifier(s) and may include the .ccess@'etwor#@1har in @.ddress .?P- if they are available at this moment and have not been yet supplied earlier to the .7. The ..@.nswer messa e shall include the &P@1.'@Type .?P if such information is available and has not yet been supplied earlier to the .7. &n that case- the ..@.nswer messa e shall also include the /.T@Type .?P when applicable for the specific &P@1.' Type (e. . 3GPP &P@1.' Type). &n addition- if &P flow mobility applies to service data flows as specified in 3GPP T" *>.*,* E=F- such that a

3GPP

elease ##

#(

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

subset of the flows within the .7 session are affected- the P1/7 shall also include &P@1.'@type and /.T@type information (if applicable) to &P flow mobility related flows- if such information is available and has not yet been supplied earlier to the .7. The &P flow mobility affected service data flows are included within the 7lows .?P at command level. &f the P1/7 needs to terminate the /( session before it has sent the .. .nswer- the P1/7 shall send the .. .nswer immediately and before the ." /eDuest. &f the P1/7 does not have an e(istin session for the /( session bein modified (such as after a P1/7 failure)- the P1/7 may reject the reDuest with an ..@.nswer with the result code set to :&.M2T2/L3'%'OG'L"2""&O'L&:.

4.4.3 Ga'( %( a'() Pro!()&r(*


:ependin on the application- in the "ervice &nformation provision- the .7 may instruct the P1/7 when the &P flow(s) are to be enabled or disabled to pass throu h the &P@1.'. The .7 does this by sendin the ..@/eDuest messa e containin the Media@1omponent@ :escription .?P(s) that contains the flow status information (in the 7low@"tatus .?P) for the flows to be enabled or disabled. &n response to this action the P1/7 shall set the appropriate ate status for the correspondin active P11 rule(s). &f a Media@"ub@1omponent .?P under a Media@1omponent@:escription .?P contains a 7low@3sa e .?P with the value /T1P- then the correspondin /T1P &P 7lows in both directions shall be enabled even if the 7low@"tatus .?P under the Media@"ub@1omponent .?P is set to 2'.052:@3P5&'%- 2'.052:@:OG'5&'%- 2'.052:- or :&".052:. The P1/7 shall reply with an ..@.nswer and shall include the .ccess@'etwor#@1har in @&dentifier(s) available at this moment. The P1/7 forwards the .7 decision to enable or disable the authori!ed &P flows. The behaviour when the .7 does not receive the ...- or when it arrives after the internal timer waitin for it has e(pired- or when it arrives with an indication different than :&.M2T2/L"3112""- are outside the scope of this specification and based on operator policy. &f the P1/7 modifies e(istin P11HJo" rules based on the updated service information and the modification fails due to resource allocation failure as specified in 3GPP T"*>.*,* E=F and if reDuested by the .7- the P1/7 shall send an /./ command to the .7 with the "pecific@.ction .?P set to the value &':&1.T&O'LO7L7.&52:L/2"O3/12"L.55O1.T&O' to report the modification failure. The .7 shall send an /.. command to ac#nowled e the /./ command.

4.4.4 ,. S(**ion T(r9ina'ion


Ghen an .7 session is terminated- if the .7 had received a successful ..@.nswer for the initial ..@/eDuest- the .7 shall send a "ession@Termination@/eDuest command to the P1/7. Otherwise- the .7 shall wait for the initial ..@ .nswer to be received prior to sendin the "ession@Termination@/eDuest command to the P1/7. Ghen the P1/7 receives a "T@/eDuest from the .7- indicatin an .7 session termination- it shall ac#nowled e that reDuest by sendin a "T@.nswer to the .7. .fterwards- it shall free the resources allocated for the correspondin "ervice :ata 7low(s). &n order to do that- the P1/7 shall initiate the reDuest for the removal of any related P11HJo" rules from the P127H002/7 and for the update of the .uthori!ed Jo" for the affected &P@1.' bearer followin the correspondin procedures specified at 3GPP T" *>.*,* E=F. &f the .7 session bein terminated corresponds to an MP" session- the P1/7 may revo#e the actions related to the prioriti!ation of the MP" session in the correspondin &P@1.' as defined in 3GPP T" *>.*,* E=F. 7or Multimedia Priority "evice handlin - see .nne( ..>. 7or sponsored data connectivity- and if a volume threshold was provided for the sponsored data connection at initial provisionin of session information (clause 8.8.,) or modification of session information (clause 8.8.*) procedures- the P1/7 shall provide the volume consumed to the .7. 7or such purpose- the P1/7 shall initiate the &P@1.' session modification procedure accordin 3GPP T" *>.*,* E=F in order to obtain the consumed volume. The P1/7 shall send then the "T@.nswer to the .7 includin the 3sed@"ervice@3nit .?P for reportin accumulated usa e within the "ponsored@1onnectivity@:ata .?P.

3GPP

elease ##

#-

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

4.4.$ S&-*!ri+'ion 'o /o'i5i!a'ion o5 Signa ing Pa'h S'a'&*


.n .7 may subscribe to notifications of the status of the .7 "i nallin transmission path. To do so- the .7 shall open an /( :iameter session with the P1/7 for the .7 si nallin usin an ..@/eDuest command. The .7 shall provide the 32$s &P address (usin either the 7ramed@&P@.ddress .?P or the 7ramed@&Pv;@Prefi( .?P) and the "pecific@.ction .?P reDuestin the subscription to I&':&1.T&O'LO7L5O""LO7 02./2/I andHor P&':&1.T&O'LO7L/252."2LO7L02./2/Q. The .7 shall additionally provide a Media@1omponent@:escription .?P includin a sin le Media@"ub@1omponent .?P with the 7low@3sa e .?P set to the value I.7L"&G'.55&'GI. The Media@1omponent@:escription .?P shall contain the Media@1omponent@'umber .?P set to P+Q. &f the procedures in 1lause 8.8.9a are not applied- the Media@"ub@1omponent .?P shall contain the 7low@'umber .?P set to P+Q- and the rest of .?Ps within the Media@1omponent@:escription and Media@"ub@1omponent .?Ps shall not be used in this case. Ghen the P1/7 receives an ..@/eDuest as described in the precedin para raph from the .7- the P1/7 shall perform session bindin as described in 3GPP T" *>.*,3 E>F and ac#nowled es the ../ command by sendin an ..@.nswer command to the .7. P11HJo" /ules related to .7 "i nallin &P 7lows should be provisioned to P127H002/7 usin the correspondin procedures specified at 3GPP T" *>.*,* E=F at an earlier sta e (e. . typically at the establishment of the &P@1.' bearer dedicated for .7 "i nallin &P 7lows). The P1/7 may install the correspondin dynamic P11HJo" rule for the .7 si nallin &P flows if none has been installed before. The .7 may cancel the subscription to notifications of the status of the .7 "i nallin transmission path at any time. &n that case- if the /( :iameter "ession is only used for subscription to 'otification of "i nallin Path "tatus- the .7 shall use a "ession@Termination@/eDuest ("T/) command to the P1/7- which shall be ac#nowled ed with a "ession@ Termination@.nswer ("T.) command. 'OT2B The /( :iameter "ession created for the .7 si nallin can also be used when the .7 reDuests notifications of &P@1.' type chan e andHor when the .7 provisions .7 "i nallin 7low &nformation.

4.4.$a Pro7i*ioning o5 ,. Signa ing . o4 ;n5or9a'ion


.n .7 may provision information about the .7 si nallin &P flows between the 32 and the .7. To do so- the .7 shall ma#e use of an /( :iameter session already opened with the P1/7 if an /( :iameter session related to the .7 si nallin is already established. The .7 may modify an already open /( :iameter session related to the .7 si nallin (e. . an /( :iameter session established for the purpose of subscription to notification of si nallin path status as described in 8.8.9) or it may open a new /( :iameter session related to the .7 si nallin if none e(ists. To provision the .7 si nallin flow information the .7 shall provide the 32$s &P address usin either 7ramed@&P@ .ddress .?P or 7ramed@&Pv;@Prefi( .?P. The .7 shall additionally provide a Media@1omponent@:escription .?P includin one or more Media@"ub@1omponent .?P(s) representin the .7 si nallin &P flows. The Media@1omponent@ :escription .?P shall contain the Media@1omponent@'umber .?P set to I+I. 2ach Media@"ub@1omponent .?P representin an .7 si nallin &P flow shall contain the 7low@'umber .?P set accordin to the rules described in .nne( 0 and one or two 7low@:escription .?P(s) set to the &P flows of the .7 si nallin . .dditionally- the Media@ "ub@1omponent .?P shall include the 7low@3sa e .?P set to the value I.7L"&G'.55&'GI- the 7low@"tatus .?P set to I2'.052:I and the .7@"i nallin @Protocol .?P set to the value correspondin to the si nallin protocol used between the 32 and the .7. Ghen the P1/7 receives from the .7 an ..@/eDuest as described in the precedin para raph- the P1/7 shall perform session bindin as described in 3GPP T" *>.*,3 E>F and shall ac#nowled e the ../ command by sendin an ..@.nswer command to the .7. P11HJo" /ules related to the .7 si nallin &P flows could have been provisioned to P127H002/7 usin the correspondin procedures specified in 3GPP T" *>.*,* E=F at an earlier sta e (e. . typically at the establishment of the &P@1.' bearer dedicated for .7 "i nallin &P 7lows). The P1/7 shall install the correspondin dynamic P11HJo" rule for the .7 si nallin &P flows. The .7 may de@provision the information about the .7 si nallin &P flows at any time. To do that- if the /( :iameter session is only used to provide information about the .7 "i nallin &P flows- the .7 shall close the /( :iameter session by sendin a "ession@Termination@/eDuest ("T/) command to the P1/7- which shall be ac#nowled ed with a

3GPP

elease ##

#.

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

"ession@Termination@.nswer ("T.) command. Otherwise- the .7 shall remove the &P flows within the Media@"ub@ 1omponent@ .?P by supplyin the 7low@"tatus .?P with value I/2MO?2:I.

4.4.# Tra55i! P an( E7(n'*


4.4.#.1 ;P-C,/ S(**ion T(r9ina'ion

Ghen an &P@1.' session is terminated- the P1/7 shall inform the .7 about the &P@1.' session termination by sendin an ."/ (abort session reDuest) command to the .7 on each active /( :iameter session. Ghen the .7 receives the ."/ command- it shall ac#nowled e the command by sendin an .". (abort session answer) command to the P1/7 and indicate the termination of the session by sendin an "T/ (session termination reDuest) command to the P1/7. The P1/7 shall ac#nowled e the termination of the session by sendin an "T. (session termination answer) command to the .7. "i nallin flows for &P@1.' session termination cases are presented in 3GPP T" *>.*,3 E>F.

4.4.#.2

S(r7i!( 6a'a . o4 6(a!'i7a'ion

&t may happen that one or more P11HJo" /ules (i.e. "ervice :ata 7lows) are deactivated at the P127H002/7 at a certain time- either permanently or temporarily. Ghen the P1/7 ets the #nowled e that one or more ":7s have been deactivated- (e. . due to a bearer release or loss of bearer or out of credit condition)- the P1/7 shall inform the .7 accordin ly if the .7 has previously subscribed usin the "pecific@.ction .?P in the ../ command. Ghen not all the service data flows within the .7 session are affected- the P1/7 shall inform the .7 by sendin an /./ (re@authori!ation reDuest) command. The /./ command shall include the deactivated &P 7lows encoded in the 7lows .?P and the cause encoded in the "pecific@.ction .?P. Ghen the .7 receives the /./ command- it shall ac#nowled e the command by sendin an /.. (re@authori!ation answer) command to the P1/7. The .7 may also update the session information by sendin an ../ (..@reDuest) command to the P1/7. &f the P1/7 receives the ../ command- it shall ac#nowled e the command by sendin an ... (..@answer) command to the .7. Ghen all the service data flows within the .7 session are affected- the P1/7 shall inform the .7 by sendin an ."/ command on the /( :iameter session related to the .7 session. Ghen the .7 receives the ."/ command- it shall ac#nowled e the command by sendin an .". (abort session answer) command to the P1/7. .fter that the .7 shall initiate an .7 session termination procedure as defined in clause 8.8.8. "i nallin flows for "ervice :ata 7low :eactivation cases are presented in 3GPP T" *>.*,3 E>F.

4.4.#.3

/o'i5i!a'ion o5 Signa ing Pa'h S'a'&*

&n the event that the P1/7 is notified of the loss or release of resources associated to the P11HJo" /ules correspondin with .7 "i nallin &P 7lows- the P1/7 shall inform the .7 about the 5oss of the "i nallin Transmission path by sendin a /e@.uthori!ation /eDuest (/./) command to the .7. The /./ shall include the "pecific@.ction .?P set to the value I&':&1.T&O'LO7L5O""LO7L02./2/I or P&':&1.T&O'LO7L/252."2LO7L02./2/Q and the deactivated &P 7low encoded in the 7lows .?P. 'OT2B &f the &M" si nallin specific P11 rules include a J1& correspondin to a non@G0/ bearer- the &':&1.T&O'LO7L5O""LO7L02./2/ will not be reported. Ghen the .7 receives the /./ command- it shall ac#nowled e the command by sendin an /.. command to the P1/7. The .7 may then decide to terminate the /( :iameter session used for the notification of the status of the .7 "i nallin transmission path. The .7 may also decide to terminate any other active /( :iameter session with the P1/7 related to the .7 "i nallin which is not available any lon er. &n that case- the .7 shall then initiate the .7 Termination procedure towards the P1/7 as defined in clause 8.8.8.

3GPP

elease ##

#*

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

4.4.#.4

;P-C,/ '"+( !hang( /o'i5i!a'ion

&f the .7 has successfully subscribed to chan e notifications in 32$s &P@1.' type and /.T type- the P1/7 shall send an /./ command when a correspondin event occurs- i.e. when the 32$s &P@1.' type or /.T type (if the &P@1.' type is GP/")- chan es. &n this case the /./ from the P1/7 shall include the "pecific@.ction .?P for the subscribed event and include the &P@1.'@Type .?P and /.T@Type .?P (in case of 3GPP &P@1.') for the 32$s new &P@ 1.'H/.T. &f the P1/7 is informed of an &P@1.' type chan e due to &P flow mobility as specified in 3GPP T" *>.*,* E=F- where a subset the flows within the .7 session are affected- the P1/7 shall include &P@1.'@type and /.T@type information (if applicable) to &P flow mobility affected service data flows. The &P flow mobility affected service data flows are included within the 7lows .?P at command level. 'OT2B The /.T type event is only applicable for &P@1.' type GP/"- the P1/7 will provide the /.T type information to the .7 not only in case of GP/" &P@1.' type- but also in case of other 3GPP &P@1.' types.

4.4.#.$

,!!(** /('4or< Charging ;n5or9a'ion /o'i5i!a'ion

&f the .7 has subscribed to a notification about .ccess 'etwor# 1har in &nformation- the P1/7 shall provide the .ccess 'etwor# 1har in &nformation in the response- if already #nown by the P1/7. &f not available- the P1/7 shall provide the .ccess 'etwor# 1har in &nformation by sendin a /e@.uthori!ation@/eDuest (/./) command when the .ccess 'etwor# 1har in &nformation is received from the P127. &f different .ccess 'etwor# 1har in &nformation is applicable to the &P@1.' session- the P1/7 shall notify the .7 about the .ccess 'etwor# 1har in &nformation that applies to each authori!ed flow. The /./ shall include the "pecific@.ction .?P set to the value I1A./G&'GL1O//25.T&O'L2O1A.'G2I and shall include the assi ned .ccess@'etwor#@1har in @&dentifier(s) and may include the .ccess@'etwor#@1har in @.ddress .?P.

4.4.#.#

%(+or'ing U*ag( 5or S+on*or() 6a'a Conn(!'i7i'"

Ghen the .7 session is associated with a sponsor and the .7 provided usa e monitorin thresholds for such sponsor to the P1/7 when the /( :iameter session was established or modified- the P1/7 shall report accumulated usa e to the .7- when @ @ @ the P1/7 detects that the usa e threshold provided by the .7 has been reachedC or the .7 session is terminated by the .7 C or the .7 session is terminated due to the &P@1.' session termination or the home operator policy disallowin the 32 accessin the sponsored data connectivity in the roamin case.

Ghen the P1/7 detects that the usa e threshold has been reached- the P1/7 shall report the accumulated usa e as provided by the P127 to the .7 in a /.@/eDuest (/./) command with the "pecific@.ction .?P set to the value 3".G2L/2PO/T Otherwise- when the .7 session is terminated by the .7 or the .7 session is terminated due to the &P@1.' session termination or the home operator policy disallowin the 32 accessin the sponsored data connectivity in the roamin case- the P1/7 shall report the accumulated usa e as provided by the P127 to the .7 in "T@.nswer ("T.) command.. The accumulated usa e shall be reported in the 3sed@"ervice@3nit .?P within the "ponsored@1onnectivity@:ata .?P. &f the .7 receives a /./ command indicatin the usa e threshold is reached- the .7 may terminate the .7 session or provide a new usa e threshold in the Granted@"ervice@3nit .?P within the "ponsored@1onnectivity@:ata .?P to the P1/7 in the ../ comand. .lternatively- the .7 may allow the session to continue without providin new usa e threshold in the ../ command. 'OT2B .fter the P1/7 reports the accumulated usa e to the .7- the .7 can provide a new usa e threshold to the P1/7. The monitorin will not start until the P1/7 receives the new threshold from the .7 and provide it to the P127

4.4.#.7

%(+or'ing ,!!(** /('4or< ;n5or9a'ion

&f the .7 reDuests the P1/7 to report the access networ# information (e. . user location andHor user time!one information)- the .7 shall subscribe to the I.112""L'2TGO/%L&'7OL/2PO/TI within the "pecific@.ction .?P and shall include the reDuired access networ# information within the /eDuired@.ccess@&nfo .?P.

3GPP

elease ##

#5

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

Ghen the P1/7 receives the access networ# information from the P127H002/7 and the .7 has subscribed to a notification about .ccess 'etwor# &nformation- the P1/7 shall provide the correspondin access networ# information to the .7 within the 3GPP@3ser@5ocation@&nfo .?P (if available)- 3GPP@"G"'@M11@M'1 .?P (if location info is not available) andHor 3GPP@M"@TimeNone .?P. P1/7 shall also provide the .112""L'2TGO/%L&'7OL/2PO/T within "pecific@.ction .?P. &f the .7 subscribes to the I.112""L'2TGO/%L&'7OL/2PO/TI- but the access networ# information is not available and the P1/7 has received the servin P5M' identifier from the P127H002/7- the P1/7 shall provide the servin P5M' identifier within 3GPP@"G"'@M11@M'1 .?P to the .7.

%2 +ro'o!o

$.1 Pro'o!o *&++or'


The /( interface in the present release is based on /( and GD protocols defined for /elease ; as specified in 3GPP T" *>.*,, E<F and 3GPP T" *>.*+> E9F respectively. Aowever- to be able to separate the policy and char in rules function (P1/7) of the present release from the policy decision function (P:7) and char in rules function (1/7) of /elease ;the /( application in the present release has an own vendor specific :iameter application. The /( application is defined as an &2T7 vendor specific :iameter application- where the vendor is 3GPP and the .pplication@&: for the /( application in the present release is ,;<<<*3;. The vendor identifier assi ned by &.'. to 3GPP (httpBHHwww.iana.or Hassi nmentsHenterprise@numbers) is ,+8,9. 'OT2B . route entry can have a different destination based on the application identification .?P of the messa e. Therefore- :iameter a ents (relay- pro(y- redirection- translation a ents) must be confi ured appropriately to identify the 3GPP /( application within the .uth@.pplication@&d .?P in order to create suitable routein tables.

:ue to the definition of the commands used in /( protocol- there is no possibility to s#ip the .uth@.pplication@&d .?P and use the ?endor@"pecific@.pplication@&d .?P instead. Therefore the /( application identification shall be included in the .uth@.pplication@&d .?P. Gith re ard to the :iameter protocol defined over the /( reference point- the P1/7 acts as a :iameter server- in the sense that it is the networ# element that handles .7 session authori!ation reDuests for a particular realm. The .7 acts as the :iameter client- in the sense that is the networ# element reDuestin the authori!ation of resources for an .7 session.

$.2 ;ni'ia i:a'ion, 9ain'(nan!( an) '(r9ina'ion o5 !onn(!'ion an) *(**ion


The initiali!ation and maintenance of the connection between each .7 and P1/7 pair is defined by the underlyin protocol. 2stablishment and maintenance of connections between :iameter nodes is described in /71 39== E,+F. .fter establishin the transport connection- the P1/7 and the .7 shall advertise the support of the /( specific .pplication by includin the value of the application identifier in the .uth@.pplication@&d .?P and the value of the 3GPP (,+8,9) in the ?endor@&d .?P of the ?endor@"pecific@.pplication@&d .?P contained in the 1apabilities@2(chan e@/eDuest and 1apabilities@2(chan e@.nswer commands. The 1apabilities@2(chan e@/eDuest and 1apabilities@2(chan e@.nswer commands are specified in the :iameter 0ase Protocol (/71 39== E,+F). The termination of the :iameter user session is specified in /71 39== E,+F in clauses =.8 and =.9. The description of how to use of these termination procedures in the normal cases is embedded in the procedures description (clause 8.8).

$.3 %2 *+(!i5i! ,VP*


Table 9.3., describes the :iameter .?Ps defined for the /( interface protocol- their .?P 1ode values- types- possible fla values- whether or not the .?P may be encrypted and which supported feature the .?P is applicable to. The ?endor@&d header of all .?Ps defined in the present document shall be set to 3GPP (,+8,9).

3GPP

elease ##

#&

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

'OT2B

Most of these .?Ps have already been defined in 3GPP T" *>.*+> E9F for /el@;. Their definition is based on the one used for /el@; with some possible modifications to be applied to the /el@< protocols. Ta1le -'3'#4 ! specific 3iameter /)Ps
7ay 8ncr' = = /pplica1ility "note 3$

/ttri1ute Name

,-or'-Ca&*( ,!!(**-/('4or<-Charging,))r(** ,!!(**-/('4or<-Charging$02 $.3.3 Gro&+() M,V P = ;)(n'i5i(r ,!!(**-/('4or<-Charging$03 $.3.4 8!'('S'ring M,V P = ;)(n'i5i(r-Va &( ,!!(+'a- (-S(r7i!(-;n5o $2# $.3.24 Gro&+() M,V P = ,.-,++ i!a'ion-;)(n'i5i(r $04 $.3.$ 8!'('S'ring M,V P = ,.-Charging-;)(n'i5i(r $0$ $.3.# 8!'('S'ring M,V P = ,++ i!a'ion-S(r7i!(-Pro7i)(r$32 $.3.29 UT.>S'ring V P M = S+on*or()Conn(!'i7i'" ;)(n'i'" Co)(!-6a'a $24 $.3.7 8!'('S'ring M,V P = . o4-6(*!ri+'ion $07 $.3.> ;P.i '(r%& ( M,V P = . o4-/&9-(r $09 $.3.9 Un*ign()32 M,V P = . o4* $10 $.3.10 Gro&+() M,V P = . o4-S'a'&* $11 $.3.11 En&9(ra'() M,V P = . o4-U*ag( $12 $.3.12 En&9(ra'() M,V P = S(r7i!(-U%/ $2$ $.3.23 8!'('S'ring M,V P = S+(!i5i!-,!'ion $13 $.3.13 En&9(ra'() M,V P = Ma2-%(?&(*'()-@an)4i)'h$1$ $.3.14 Un*ign()32 M,V P = 6L Ma2-%(?&(*'()-@an)4i)'h$1# $.3.1$ Un*ign()32 M,V P = UL M()ia-Co9+on(n'$17 $.3.1# Gro&+() M,V P = 6(*!ri+'ion M()ia-Co9+on(n'-/&9-(r $1> $.3.17 Un*ign()32 M,V P = M()ia-S&--Co9+on(n' $19 $.3.1> Gro&+() M,V P = M()ia-T"+( $20 $.3.19 En&9(ra'() M,V P = MPS-;)(n'i5i(r $2> $.3.30 8!'('S'ring V P M = %( 10 Min-%(?&(*'()-@an)4i)'h-6L $34 $.3.32 Un*ign()32 V P M = %( 10 Min-%(?&(*'()-@an)4i)'h-UL $3$ $.3.33 Un*ign()32 V P M = %( 10 %%-@an)4i)'h $21 $.3.20 Un*ign()32 M,V P = %S-@an)4i)'h $22 $.3.21 Un*ign()32 M,V P = S(r7i!(-;n5o-S'a'&* $27 $.3.2$ En&9(ra'() M,V P = S;P-.or<ing-;n)i!a'ion $23 $.3.22 En&9(ra'() M,V P = S+on*or-;)(n'i'" $31 $.3.2> UT.>S'ring V P M = S+on*or()Conn(!'i7i'" S+on*or()-Conn(!'i7i'"-6a'a $30 $.3.27 Gro&+() V P M = S+on*or()Conn(!'i7i'" ,.-Signa ing-Pro'o!o $29 $.3.2# En&9(ra'() V P M = Pro7,.*igna . o4 %(?&ir()-,!!(**-;n5o $3# $.3.34 En&9(ra'() V P M = /('Lo! %2-%(?&(*'-T"+( $33 $.3.31 En&9(ra'() V P M = ;P-6o9ain-;) $37 $.3.3$ 8!'('S'ring V P M = /8TE 10 Th( ,VP h(a)(r -i' )(no'() a* AMA, in)i!a'(* 4h('h(r *&++or' o5 'h( ,VP i* r(?&ir(). Th( ,VP h(a)(r -i' )(no'() a* AVA, in)i!a'(* 4h('h(r 'h( o+'iona V(n)or-;6 5i( ) i* +r(*(n' in 'h( ,VP h(a)(r. .or 5&r'h(r )('ai *, *(( %.C 3$>> B10C. /8TE 20 Th( 7a &( '"+(* ar( )(5in() in %.C 3$>> B10C. /8TE 30 ,VP* 9ar<() 4i'h DPro7,.*igna . o4E, DS+on*or()Conn(!'i7i'"E, D%( 10E or D/('Lo!E ar( a++ i!a- ( a* )(*!ri-() in ! a&*( $.4.1

/)P Code $00 $01

/)P 0lag rules "note #$ Clause )alue Type 7ust 7ay Should 7ust defined "note %$ not not $.3.1 En&9(ra'() M,V P $.3.2 ,))r(** M,V P

$.3.1 ,-or'-Ca&*( ,VP


The .bort@1ause .?P (.?P code 9++) is of type 2numerated- and determines the cause of an abort session reDuest (."/) or of a /./ indicatin a bearer release. The followin values are definedB 02./2/L/252."2: (+)

3GPP

elease ##

%+

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

This value is used when the bearer has been deactivated as a result from normal si nallin handlin . 7or GP/" the bearer refers to the P:P 1onte(t. &'"377&1&2'TL"2/?2/L/2"O3/12" (,) This value is used to indicate that the server is overloaded and needs to abort the session. &'"377&1&2'TL02./2/L/2"O3/12" (*) This value is used when the bearer has been deactivated due to insufficient bearer resources at a transport ateway (e. . GG"' for GP/"). P"LTOL1"LA.':O?2/ (3) This value is used when the bearer has been deactivated due to P" to 1" handover. "PO'"O/2:L:.T.L1O''21T&?&TML :&".55OG2: (8) This value is used in the ."/ when the P1/7 needs to initiates the .7 session termination due to the operator policy (e. . disallowin the 32 accessin the sponsored data connectivity in the roamin case).

$.3.2 ,!!(**-/('4or<-Charging-,))r(** ,VP


The .ccess@'etwor#@1har in @.ddress .?P (.?P code 9+,) is of type .ddress- and it indicates the &P .ddress of the networ# entity within the access networ# performin char in (e. . the GG"' &P address). The .ccess@'etwor#@1har in @.ddress .?P should not be forwarded over an inter@operator interface.

$.3.3 ,!!(**-/('4or<-Charging-;)(n'i5i(r ,VP


The .ccess@'etwor#@1har in @&dentifier .?P (.?P code 9+*) is of type Grouped- and contains a char in identifier (e. . G1&:) within the .ccess@'etwor#@1har in @&dentifier@?alue .?P alon with information about the flows transported within the correspondin bearer within the 7lows .?P. &f no 7lows .?P is provided- the .ccess@'etwor#@1har in @&dentifier@?alue applies for all flows within the .7 session. The .ccess@'etwor#@1har in @&dentifier .?P can be sent from the P1/7 to the .7. The .7 may use this information for char in correlation with session layer. .?P 7ormatB
Access-Network-Charging-Identifier ::= < AVP Header: 502 > Access-Network-Charging-Identifier-Va!"e# $% &!ows '

$.3.4 ,!!(**-/('4or<-Charging-;)(n'i5i(r-Va &( ,VP


The .ccess@'etwor#@1har in @&dentifier@?alue .?P (.?P code 9+3) is of type Octet"trin - and contains a char in identifier (e. . G1&:).

$.3.$ ,.-,++ i!a'ion-;)(n'i5i(r ,VP


The .7@.pplication@identifier .?P (.?P code 9+8) is of type Octet"trin - and it contains information that identifies the particular service that the .7 service session belon s to. This information may be used by the P1/7 to differentiate Jo" for different application services. 7or e(ample the .7@.pplication@&dentifier may be used as additional information to ether with the Media@Type .?P when the Jo" class for the bearer authori!ation at the G( interface is selected. The .7@.pplication@&dentifier may be used also to complete the Jo" authori!ation with application specific default settin s in the P1/7 if the .7 does not provide full "ession@1omponent@:escription information.

3GPP

elease ##

%#

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

$.3.# ,.-Charging-;)(n'i5i(r ,VP


The .7@1har in @&dentifier .?P (.?P code 9+9) is of type Octet"trin - contains the .7 1har in &dentifier that is sent by the .7. This information may be used for char in correlation with bearer layer.

$.3.7 Co)(!-6a'a ,VP


The 1odec@:ata .?P (.?P code 9*8) is of type Octet"trin . The 1odec@:ata .?P shall contain codec related information #nown at the .7. This information shall be encoded as followsB @ The first line of the value of the 1odec@:ata .?P shall consist of either the word Iuplin#I or the word Idownlin#I (in ."1&&- without Duotes) followed by a new@line character. The semantics of these words are the followin B @ @ Iuplin#I indicates that the ":P was received from the 32 and sent to the networ#. Idownlin#I indicates that the ":P was received from the networ# and sent to the 32. The first line indicates the direction of the source of the ":P used to derive the information. The majority of the information within the 1odec@:ata .?P indicatin Idownlin#I describes properties- for instance receiver capabilities- of the sender of the ":P- the networ# in this case and is therefore applicable for &P flows in the uplin# direction. "imilarly- the majority of the information within the 1odec@:ata .?P indicatin Iuplin#I describes properties- for instance receiver capabilities- of the sender of the ":P- the 32 in this case and is therefore applicable for &P flows in the downlin# direction.

'OT2B

The second line of the value of the 1odec@:ata .?P shall consist of either the word IofferI or the word IanswerI- or the word IdescriptionI (in ."1&&- without Duotes) followed by a new@line character. The semantics of these words are the followin B @ @ @ IofferI indicates that ":P lines from an ":P offer accordin to /71 3*;8 E,=F are bein provisioned in the 1odec@:ata .?PC IanswerI indicates that ":P lines from an ":P answer accordin to /71 3*;8 E,=F are bein provisioned in the 1odec@:ata .?PC IdescriptionI indicates that ":P lines from a ":P session description in a scenario where the offer@answer mechanism of /71 3*;8 E,=F is not bein applied are bein provisioned in the 1odec@:ata .?P. 7or instance- ":P from an /T"P I:escribeI reply may be provisioned.

The rest of the value shall consist of ":P line(s) in ."1&& encodin separated by new@line characters- as specified in &2T7 /71 89;; E,3F. The first of these line(s) shall be an ImI line. The remainin lines shall be any available ":P IaI and IbI lines related to that ImI line. Aowever- to avoid duplication of information- the ":P IaKsendrecvI- IaKrecvonly I- IaKsendonlyI- IaKinactiveI- IbB."I- IbB/"I and IbB//I lines do not need to be included.

$.3.> . o4-6(*!ri+'ion ,VP


The 7low@:escription .?P (.?P code 9+<) is of type &P7ilter/ule- and defines a pac#et filter for an &P flow with the followin informationB @ @ @ @ :irection (in or out). The direction IinI refers to uplin# &P flows- and the direction IoutI refers to downlin# &P flows. "ource and destination &P address (possibly mas#ed). Protocol. "ource and destination port.

The &P7ilter/ule type shall be used over /( interface with the followin restrictionsB

3GPP

elease ##

%%

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

@ @ @ @ @

The "ource Port may be omitted to indicate that any source port is allowed. 5ists or ran es shall not be used. Only the .ction IpermitI shall be used. 'o IoptionsI shall be used. The invert modifier IRI for addresses shall not be used. The #eyword Iassi nedI shall not be used. 7or T1P protocol- destination port can also be omitted.

'OT2B

&f any of these restrictions is not observed by the .7- the server shall send an error response to the .7 containin the 2(perimental@/esult@1ode .?P with value 7&5T2/L/2"T/&1T&O'". 7or the /( interface- the 7low description .?P shall be used to describe a sin le &P flow.

$.3.9 . o4-/&9-(r ,VP


The 7low@'umber .?P (.?P code 9+>) is of type 3nsi ned3*- and it contains the ordinal number of the &P flow(s)assi ned accordin to the rules in .nne( 0.

$.3.10 . o4* ,VP


The 7lows .?P (.?P code 9,+) is of type Grouped- and it indicates &P flows via their flow identifiers. Ghen reportin an out of credit condition- the 7inal@3nit@.ction .?P indicates the termination action applied to the impacted flows. &f no 7low@'umber .?P(s) are supplied- the 7lows .?P refers to all 7lows matchin the media component number. .?P 7ormatB
&!ows::= < AVP Header: 5(0 > )edia-Co*+onent-N"*,er# $%&!ow-N"*,er' %&ina!--nit-Action'

$.3.11 . o4-S'a'&* ,VP


The 7low@"tatus .?P (.?P code 9,,) is of type 2numerated- and describes whether the &P flow(s) are enabled or disabled. The followin values are definedB 2'.052:@3P5&'% (+) This value shall be used to enable associated uplin# &P flow(s) and to disable associated downlin# &P flow(s). 2'.052:@:OG'5&'% (,) This value shall be used to enable associated downlin# &P flow(s) and to disable associated uplin# &P flow(s). 2'.052: (*) This value shall be used to enable all associated &P flow(s) in both directions. :&".052: (3) This value shall be used to disable all associated &P flow(s) in both directions. /2MO?2: (8) This value shall be used to remove all associated &P flow(s). The &P 7ilters for the associated &P flow(s) shall be removed. The associated &P flows shall not be ta#en into account when derivin the authori!ed Jo". 'OT2B The interpretation of values for the /T1P flows in the /( interface is described within the procedures in clause 8.8.3.

3GPP

elease ##

%3

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

$.3.12 . o4-U*ag( ,VP


The 7low@3sa e .?P (.?P code 9,*) is of type 2numerated- and provides information about the usa e of &P 7lows. The followin values are definedB 'OL&'7O/M.T&O' (+) This value is used to indicate that no information about the usa e of the &P flow is bein provided. /T1P (,) This value is used to indicate that an &P flow is used to transport /T1P. .7L"&G'.55&'G (*) This value is used to indicate that the &P flow is used to transport .7 "i nallin Protocols (e. . "&PH":P). 'OL&'7O/M.T&O' is the default value. 'OT2B .n .7 may choose not to identify /T1P flows- e. . in order to avoid that /T1P flows are always enabled by the server.

$.3.13 S+(!i5i!-,!'ion ,VP


The "pecific@.ction .?P (.?P code 9,3) is of type 2numerated. Githin a P1/7 initiated /e@.uthori!ation /eDuest- the "pecific@.ction .?P determines the type of the action. Githin an initial .. reDuest the .7 may use the "pecific@.ction .?P to reDuest specific actions from the server at the bearer events and to limit the contact to such bearer events where specific action is reDuired. &f the "pecific@.ction .?P is omitted within the initial .. reDuest- no notification of any of the events defined below is reDuested. The followin values are definedB ?oid (+) 1A./G&'GL1O//25.T&O'L2O1A.'G2 (,) Githin a /./- this value shall be used when the server reports the access networ# char in identifier to the .7. The .ccess@'etwor#@1har in @&dentifier .?P shall be included within the reDuest. &n the ../- this value indicates that the .7 reDuests the server to provide the access networ# char in identifier to the .7 for each authori!ed flow- when the access networ# char in identifier becomes #nown at the P1/7. &':&1.T&O'LO7L5O""LO7L02./2/ (*) Githin a /./- this value shall be used when the server reports a loss of a bearer (e. . in the case of GP/" P:P conte(t bandwidth modification to + #bit) to the .7. The ":7s that are deactivated as a conseDuence of this loss of bearer shall be provided within the 7lows .?P. &n the ../- this value indicates that the .7 reDuests the server to provide a notification at the loss of a bearer. &':&1.T&O'LO7L/21O?2/MLO7L02./2/ (3) Githin a /./- this value shall be used when the server reports a recovery of a bearer (e. . in the case of GP/"P:P conte(t bandwidth modification from + #bit to another value) to the .7. The ":7s that are re@activated as a conseDuence of the recovery of bearer shall be provided within the 7lows .?P. &n the ../- this value indicates that the .7 reDuests the server to provide a notification at the recovery of a bearer. &':&1.T&O'LO7L/252."2LO7L02./2/ (8) Githin a /./- this value shall be used when the server reports the release of a bearer (e. . P:P conte(t removal for GP/") to the .7. The ":7s that are deactivated as a conseDuence of this release of bearer shall be provided within the 7lows .?P. &n the ../- this value indicates that the .7 reDuests the server to provide a notification at the removal of a bearer. ?oid (9)

3GPP

elease ##

%(

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

&P@1.'L1A.'G2 (;) This value shall be used in /./ command by the P1/7 to indicate a chan e in the &P@1.' type or /.T type (if the &P@1.' type is GP/"). Ghen used in an ../ command- this value indicates that the .7 is reDuestin subscription to &P@1.' chan e and /.T chan e notification. Ghen used in /./ it indicates that the P1/7 enerated the reDuest because of an &P@1.' or /.T chan e. &P@1.'@Type .?P and /.T@Type .?P (in case of 3GPP &P@1.') shall be provided in the same reDuest with the newHvalid value(s). &f an &P@1.' type or /.T type chan e is due to &P flow mobility and a subset of the flows within the .7 session is affected- the affected service data flows shall be provided in the same reDuest. &':&1.T&O'LO7LO3TLO7L1/2:&T (<) Githin a /./- this value shall be used when the P1/7 reports to the .7 that ":7s have run out of credit- and that the termination action indicated by the correspondin 7inal@3nit@.ction .?P applies (3GPP T" 3*.*8+ E*3F and 3GPP T" 3*.*>> E*8). The ":7s that are impacted as a conseDuence of the out of credit condition shall be provided within the 7lows .?P. &n the ../- this value indicates that the .7 reDuests the P1/7 to provide a notification of ":7s for which credit is no lon er available. .pplicable to functionality introduced with the /el= feature as described in clause 9.8.,. &':&1.T&O'LO7L"3112""735L/2"O3/12"L.55O1.T&O' (=) Githin a /./- this value shall be used by the P1/7 to indicate that the resources reDuested for particular service information have been successfully allocated. The ":7s correspondin to the resources successfully allocated shall be provided within the 7lows .?P. &n the ../- this value indicates that the .7 reDuests the P1/7 to provide a notification when the resources associated to the correspondin service information have been allocated. .pplicable to functionality introduced with the /el= feature as described in clause 9.8.,. 'OT2B This value applies to applications for which the successful resource allocation notification is reDuired for their operation since subscription to this value impacts the resource allocation si nallin overhead towards the P127H002/7.

&':&1.T&O'LO7L7.&52:L/2"O3/12"L.55O1.T&O' (>) Githin a /./- this value shall be used by the P1/7 to indicate that the resources reDuested for a particular service information cannot be successfully allocated. The ":7s correspondin to the resources that could not be allocated shall be provided within the 7lows .?P. &n the ../- this value indicates that the .7 reDuests the P1/7 to provide a notification when the resources associated to the correspondin service information cannot be allocated. .pplicable to functionality introduced with the /el= feature as described in clause 9.8.,. 'OT2B This value applies to applications for which the unsuccessful resource allocation notification is reDuired for their operation since subscription to this value impacts the resource allocation si nallin overhead towards the P127H002/7.

&':&1.T&O'LO7L5&M&T2:LP11L:2P5OMM2'T (,+) Githin a /./- this value shall be used when the server reports the limited P11 deployment (i.e. dynamically allocated resources are not applicable) as specified at .nne( 5 in 3GPP T" *3.*+3 E*F to the .7. &n the ../this value indicates that the .7 reDuests the server to provide a notification for the limited P11 deployment. .pplicable to functionality introduced with the /el= feature as described in clause 9.8.,. 3".G2L/2PO/T (,,) &n the /.@/eDuest (/./)- this value shall be used by the P1/7 to report accumulated usa e volume when the usa e threshold provided by the .7 has been reached. &n the ..@/eDuest (../)- this value indicates that the .7 reDuests P1/7 to report accumulated usa e volume when it reaches the threshold. .pplicable to functionality introduced with the "ponsored1onnectivity feature as described in clause 9.8.,.

3GPP

elease ##

%-

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

.112""L'2TGO/%L&'7OL/2PO/T (,*) &n the /.@/eDuest (/./)- this value shall be used by the P1/7 to report access networ# information when the P1/7 receivin an .ccess 'etwor# &nformation report correspondin to the .7 session from the P127H002/7. &n the ..@/eDuest (../)- this value indicates that the .7 reDuests P1/7 to report access networ# information when the P1/7 receivin an .ccess 'etwor# &nformation report correspondin to the .7 session from the P127H002/7.

$.3.14 Ma2-%(?&(*'()-@an)4i)'h-6L ,VP


The Ma(@/eDuested@0andwidth@:5 .?P (.?P code 9,9) is of type 3nsi ned3*- and it indicates the ma(imum bandwidth in bits per second for a downlin# &P flow. The bandwidth contains all the overhead comin from the &P@layer and the layers above- e. . &P- 3:P- /TP and /TP payload. Ghen provided in an ..@/eDuest- it indicates the ma(imum reDuested bandwidth. Ghen provided in an ..@.nswer- it indicates the ma(imum bandwidth acceptable by P1/7.

$.3.1$ Ma2-%(?&(*'()-@an)4i)'h-UL ,VP


The Ma( @0andwidth@35 .?P (.?P code 9,;) is of type 3nsi ned3*- and it indicates the ma(imum reDuested bandwidth in bits per second for an uplin# &P flow. The bandwidth contains all the overhead comin from the &P@layer and the layers above- e. . &P- 3:P- /TP and /TP payload. Ghen provided in an ..@/eDuest- it indicates the ma(imum reDuested bandwidth. Ghen provided in an ..@.nswer- it indicates the ma(imum bandwidth acceptable by P1/7.

$.3.1# M()ia-Co9+on(n'-6(*!ri+'ion ,VP


The Media@1omponent@:escription .?P (.?P code 9,<) is of type Grouped- and it contains service information for a sin le media component within an .7 session or the .7 si nallin information. The service information may be based on the ":& e(chan ed between the .7 and the .7 session client in the 32. The information may be used by the P1/7 to determine authori!ed Jo" and &P flow classifiers for bearer authori!ation and P11 rule selection. Githin one :iameter messa e- a sin le &P flow shall not be described by more than one Media@1omponent@:escription .?P. 0andwidth information and 7low@"tatus information provided within the Media@1omponent@:escription .?P applies to all those &P flows within the media component- for which no correspondin information is bein provided within Media@"ub@1omponent .?P(s). &f a Media@1omponent@:escription .?P is not supplied by the .7- or if optional .?P(s) within a Media@1omponent@ :escription .?P are omitted- but correspondin information has been provided in previous :iameter messa es- the previous information for the correspondin &P flow(s) remains valid. .ll &P flows within a Media@1omponent@:escription .?P are permanently disabled by supplyin a 7low "tatus .?P with value I/2MO?2:I. The server may delete correspondin filters and state information. /eservation@Priority provided within the Media@1omponent@:escription .?P in the reDuest from the .7 applies to all those &P flows within the media component and describes the relative importance of the &P flow as compared to other &P flows. The P1/7 may use this value to implement priority based admission. &f the /eservation@Priority .?P is not specified the &P flow priority is :27.35T (+). 2ach Media@1omponent@:escription .?P shall contain either !ero- or one- or two 1odec@:ata .?Ps. &n the case of conflicts- information contained in other .?Ps either within this Media@1omponent@:escription .?P- or within the correspondin Media@1omponent@:escription .?P in a previous messa e- shall ta#e precedence over information within the 1odec@:ata .?P(s). The .7 shall provision all the available information in other applicable .?Ps in addition to the information in the 1odec@:ata .?P- if such other .?Ps are specified. &f the ":P offer@answer procedures of &2T7 /71 3*;8 E,=F are applicable for the session ne otiation between the two ends ta#in part in the communication (e. . for &M")- the followin appliesB

3GPP

elease ##

%.

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

@ @ @

The .7 shall provision information derived from an ":P answer and shall also provision information derived from the correspondin ":P offer. &f the Media@1omponent@:escription .?P contains two 1odec@:ata .?Ps- one of them shall represent an ":P offer and the other one the correspondin ":P answer. &f the Media@1omponent@:escription .?P contains one 1odec@:ata .?P- and this .?P represents an ":P offer- the .7 shall provision the correspondin ":P answer information in a 1odec@:ata .?P within a subseDuent /( messa e. "ome ":P parameters for the same codec in the ":P offer and answer are independent of each other and refer to &P flows in opposite directions- for instance some M&M2 parameters conveyed within IaKfmtpI ":P lines and the pac#eti!ation time within the IaKptimeI line. Other parameters within the ":P answer ta#e precedence over correspondin parameters within the ":P offer.

'OT2B

&f ":P is applied without usin the offer@answer procedures- !ero or one 1odec@:ata .?P shall be provisioned. The P1/7 may provide the Media@1omponent@:escription .?P(s) within the .cceptable@"ervice@&nfo .?P in the ..@.nswer command if the service information received from the .7 is rejected. 7or this usa e- the Media@ 1omponent@:escription .?P shall only include the appropriate Media@1omponent@'umber .?P and the Ma(@ /eDuested@0andwidth@35 andHor Ma(@/eDuested@0andwidth@:5 .?Ps indicatin the ma(imum acceptable bandwidth. .?P formatB
)edia-Co*+onent-.escri+tion ::= < AVP Header: 5(/ > )edia-Co*+onent-N"*,er # 0 1rdina! n"*,er of the *edia co*+2 $% )edia-3",-Co*+onent ' 0 3et of f!ows for one f!ow identifier % A&-A++!ication-Identifier ' % )edia-45+e ' % )a6-7e8"ested-9andwidth--: ' % )a6-7e8"ested-9andwidth-.: ' % )in-7e8"ested-9andwidth--: ' % )in-7e8"ested-9andwidth-.: ' % &!ow-3tat"s ' % 7eser;ation-Priorit5 ' % 73-9andwidth ' % 77-9andwidth ' $% Codec-.ata '

$.3.17 M()ia-Co9+on(n'-/&9-(r ,VP


The Media@1omponent@'umber .?P (.?P code 9,=) is of type 3nsi ned3*- and it contains the ordinal number of the media component- assi ned accordin to the rules in .nne( 0. Ghen this .?P refers to .7 si nallin - this is indicated by usin the value + accordin to the rules in .nne( 0.

$.3.1> M()ia-S&--Co9+on(n' ,VP


The Media@"ub@1omponent .?P (.?P code 9,>) is of type Grouped- and it contains the reDuested bitrate and filters for the set of &P flows identified by their common 7low@&dentifier. The 7low@&dentifier is defined in .nne( 0. Possible 0andwidth information and 7low@"tatus information provided within the Media@"ub@1omponent .?P ta#es precedence over information within the encapsulatin Media 1omponent :escription .?P. &f a Media@"ub@ 1omponent@ .?P is not supplied- or if optional .?P(s) within a Media@"ub@1omponent .?P are omitted- but correspondin information has been provided in previous :iameter messa es- the previous information for the correspondin &P flow(s) remains valid- unless new information is provided within the encapsulatin Media@1omponent@:escription .?P. &f 7low@:escription .?P(s) are supplied- they replace all previous 7low@:escription .?P(s)- even if a new 7low@:escription .?P has the opposite direction as the previous 7low@:escription .?P. The .7@"i nallin @Protocol .?P may be included only if the 7low@3sa e .?P has a value of $.7L"&G'.55&'G$. .ll &P flows within a Media@"ub@1omponent@ .?P are permanently disabled by supplyin a 7low "tatus .?P with value I/2MO?2:I. The server may delete correspondin filters and state information. .?P formatB

3GPP

elease ##

%*

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

)edia-3",-Co*+onent ::= < AVP Header: 5(< > &!ow-N"*,er # 0 1rdina! n"*,er of the IP f!ow 0$2% &!ow-.escri+tion ' 0 -: and=or .: % &!ow-3tat"s ' % &!ow--sage ' % )a6-7e8"ested-9andwidth--: ' % )a6-7e8"ested-9andwidth-.: ' % A&-3igna!!ing-Protoco! ' $% AVP '

$.3.19 M()ia-T"+( ,VP


The Media@Type .?P (.?P code 9*+) is of type 2numerated- and it determines the media type of a session component. The media types indicate the type of media in the same way as the ":P media types with the same names defined in /71 89;; E,3F. The followin values are definedB @ @ @ @ @ @ @ @ .3:&O (+) ?&:2O (,) :.T. (*) .PP5&1.T&O' (3) 1O'T/O5 (8) T2OT (9) M2"".G2 (;) OTA2/ (+(77777777)

$.3.20 %%-@an)4i)'h ,VP


The //@0andwidth .?P (.?P code 9*,) is of type 3nsi ned3*- and it indicates the ma(imum reDuired bandwidth in bits per second for /T1P receiver reports within the session component- as specified in /71 399; E,,F. The bandwidth contains all the overhead comin from the &P@layer and the layers above- i.e. &P- 3:P and /T1P.

$.3.21 %S-@an)4i)'h ,VP


The /"@0andwidth .?P (.?P code 9**) is of type 3nsi ned3*- and it indicates the ma(imum reDuired bandwidth in bits per second for /T1P sender reports within the session component- as specified in /71 399; E,,F. The bandwidth contains all the overhead comin from the &P@layer and the layers above- i.e. &P- 3:P and /T1P.

$.3.22 S;P-.or<ing-;n)i!a'ion ,VP


The "&P@7or#in @&ndication .?P (.?P code 9*3) is of type 2numerated- and describes if several "&P dialo ues are related to one :iameter sessionB "&'G52L:&.5OG32 (+) This value is used to indicate that the :iameter session relates to a sin le "&P dialo ue. This is the default value applicable if the .?P is omitted. "2?2/.5L:&.5OG32" (,) This value is used to indicate that the :iameter session relates to several "&P dialo ues.

$.3.23 S(r7i!(-U%/ ,VP


The "ervice@3/' .?P (.?P code 9*9) is of type Octet"trin - and it indicates that an .7 session is used for emer ency traffic.

3GPP

elease ##

%5

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

&t contains values of the service 3/' includin subservices- as defined in E*,F or re istered at &.'.. The strin IurnBserviceBI in the be innin of the 3/' shall be omitted in the .?P and all subseDuent te(t shall be included. 2(amples of valid values of the .?P are IsosI- Isos.fireI- Isos.policeI and Isos.ambulanceI.

$.3.24 ,!!(+'a- (-S(r7i!(-;n5o ,VP


The .cceptable@"ervice@&nfo .?P (.?P code 9*;) is of type Grouped- and contains the ma(imum bandwidth for an .7 session andHor for specific media components that will be authori!ed by the P1/7. The Ma(@/eDuested@0andwidth@ :5 .?P and Ma(@/eDuested@0andwidth@35 .?P directly within the .cceptable@"ervice@&nfo .?P indicate the acceptable bandwidth for the entire .7 session. The Ma(@/eDuested@0andwidth@:5 .?P and Ma(@/eDuested@ 0andwidth@35 .?P within a Media@1omponent@:escription .?P included in the .cceptable@"ervice@&nfo .?P indicate the acceptable bandwidth for the correspondin media component. &f the acceptable bandwidth applies to one or more media components- only the Media@1omponent@:escription .?P will be provided. &f the acceptable bandwidth applies to the whole .7 session- only the Ma(@/eDuested@0andwidth@:5 .?P and Ma(@/eDuested@0andwidth@35 .?P will be included.
Acce+ta,!e-3er;ice-Info::= $% % % $% < AVP Header: 52> > )edia-Co*+onent-.escri+tion' )a6-7e8"ested-9andwidth-.: ' )a6-7e8"ested-9andwidth--: ' AVP '

$.3.2$ S(r7i!(-;n5o-S'a'&*-,VP
The "ervice@&nfo@"tatus .?P (.?P code 9*<) is of type 2numerated- and indicates the status of the service information that the .7 is providin to the P1/7. &f the "ervice@&nfo@"tatus .?P is not provided in the .. reDuest- the value 7&'.5 "2/?&12 &'7O/M.T&O' shall be assumed. 7&'.5 "2/?&12 &'7O/M.T&O' (+) This value is used to indicate that the service has been fully ne otiated between the two ends and service information provided is the result of that ne otiation. P/25&M&'./M "2/?&12 &'7O/M.T&O' (,) This value is used to indicate that the service information that the .7 has provided to the P1/7 is preliminary and needs to be further ne otiated between the two ends (e. . for &M" when the service information is sent based on the ":P offer).

$.3.2# ,.-Signa ing-Pro'o!o -,VP


The .7@"i nallin @Protocol .?P (.?P code 9*>) is of type 2numerated- and indicates the protocol used for si nallin between the 32 and the .7. &f the .7@"i nallin @Protocol .?P is not provided in the ..@/eDuest- the value 'OL&'7O/M.T&O' shall be assumed. 'OL&'7O/M.T&O' (+) This value is used to indicate that no information about the .7 si nallin protocol is bein provided. "&P (,) This value is used to indicate that the si nallin protocol is "ession &nitiation Protocol.

$.3.27 S+on*or()-Conn(!'i7i'"-6a'a ,VP


The "ponsored@1onnectivity@:ata .?P (.?P code 93+) is of type Grouped- and indicates the data associated with the sponsored data connectivity that the .7 is providin to the P1/7. The "ponsor@&dentity .?P identifies the sponsor. &t shall be included by the .7 in the "ponsored@1onnectivity@:ata .?P. The .pplication@"ervice@Provider@&dentity .?P identifies the application service provider. &t shall be included by the .7 in the "ponsored@1onnectivity@:ata .?P.

3GPP

elease ##

%&

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The Granted@"ervice@3nit .?P shall be used by the .7 to provide usa e threshold level to the P1/7 if the volume of traffic allowed durin the sponsored data connectivity is to be monitored. The 3sed@"ervice@3nit .?P shall be used by the P1/7 to provide the measured usa e to the P1/7. /eportin shall be done- as reDuested by the .7- in 11@Total@Octets- 11@&nput@Octets or 11@Output@Octets of the 3sed@"ervice@3nit .?P. .?P formatB
3+onsored-Connecti;it5-.ata::= % % % % $% < AVP Header: 5?0 > 3+onsor-Identit5 ' A++!ication-3er;ice-Pro;ider-Identit5 ' @ranted-3er;ice--nit ' -sed-3er;ice--nit ' AVP '

$.3.2> S+on*or-;)(n'i'" ,VP


The "ponsor@&dentity .?P (.?P code 93,) is of type 3T7="trin and is used for sponsored data connectivity purposes as an identifier of the sponsor.

$.3.29 ,++ i!a'ion-S(r7i!(-Pro7i)(r-;)(n'i'" ,VP


The .pplication@"ervice@Provider@&dentity .?P (.?P code 93*) is of type 3T7="trin and is used for sponsored data connectivity purposes as an identifier of the application service provider.

$.3.30 MPS-;)(n'i5i(r ,VP


The MP"@&dentifier .?P (.?P code 9*=) is of type Octet"trin - and it indicates that an .7 session relates to an MP" session. &t contains the national variant for MP" service name (e. .- 'G' G2T").

$.3.31 %2-%(?&(*'-T"+( ,VP


The /(@/eDuest@Type .?P (.?P code 933) is of type 2numerated- and contains the reason for sendin the ..@ /eDuest messa e. The followin values are definedB &'&T&.5L/2J32"T (+) .n initial reDuest is used to initiate an /( session and contains information that is relevant to initiation. 3P:.T2L/2J32"T (,) .n update reDuest is used to update an e(istin /( session.

$.3.32 Min-%(?&(*'()-@an)4i)'h-6L ,VP


The Min@/eDuested@0andwidth@:5 .?P (.?P code 938) is of type 3nsi ned3*- and it indicates the minimum reDuested bandwidth in bits per second for a downlin# &P flow. The bandwidth contains all the overhead comin from the &P@layer and the layers above- e. . &P- T1P- 3:P- ATTP- /TP and /TP payload. Ghen provided in an ..@/eDuest- it indicates the minimum reDuested bandwidth.

$.3.33 Min-%(?&(*'()-@an)4i)'h-UL ,VP


The Min@/eDuested@0andwidth@35 .?P (.?P code 939) is of type 3nsi ned3*- and it indicates the minimum reDuested bandwidth in bits per second for an uplin# &P flow. The bandwidth contains all the overhead comin from the &P@layer and the layers above- e. . &P- T1P- 3:P- ATTP- /TP and /TP payload. Ghen provided in an ..@/eDuest- it indicates the minimum reDuested bandwidth.

3GPP

elease ##

3+

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

$.3.34 %(?&ir()-,!!(**-;n5o ,VP


The /eDuired@.ccess@&nfo .?P (.?P code 93;) is of type 2numerated- and contains the access networ# information reDuired for that .7 session. The followin values are definedB 3"2/L5O1.T&O' (+) &ndicates that the user location information shall be reported- the P1/7 shall report the user location information within the 3GPP@3ser@5ocation@&nfo .?P- if available. Otherwise- it shall provide the servin P5M' identifier within the 3GPP@"G"'@M11@M'1 .?P. M"LT&M2LNO'2 (,) &ndicates that the user time!one information shall be reported- the P1/7 shall report the user time!one information within the 3GPP@M"@TimeNone .?P.

$.3.3$ ;P-6o9ain-;) ,VP


The &P@:omain@&d .?P (.?P code 93<) is of type (Octet"trin )- and indicates the domain information which assists session bindin .

$.4 %2 r(-&*() ,VP*


Table 9.8., lists the :iameter .?Ps re@used by the /( reference point from e(istin :iameter .pplications- includin a reference to their respective specifications and when needed- a short description of their usa e within the /( reference point. Other .?Ps from e(istin :iameter .pplications- e(cept for the .?Ps from :iameter 0ase Protocol- do not need to be supported. The .?Ps from :iameter 0ase Protocol are not included in table 9.8.,- but they are re@used for the /( protocol. 3nless otherwise stated- re@used .?Ps shall maintain their $M$- $P$ and $?$ fla settin s. Ghere 3GPP /adius ?".s are re@used- unless otherwise stated- they shall be translated to :iameter .?Ps as described in /71 8++9 E,*F with the e(ception that the $M$ fla shall be set and the $P$ fla may be set.

3GPP

elease ##

3#

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

Ta1le -'('#4 ! re,used 3iameter /)Ps


/ttri1ute Name 3GPP-MS-Ti9(Fon( eference 3GPP TS 29.0#1 B11C Comments /pplica1ility "notes #9 %$ /('Lo! /('Lo! /('Lo! %( > %( >

;n)i!a'(* 'h( o55*(' -('4((n &ni7(r*a 'i9( an) o!a 'i9( in *'(+* o5 1$ 9in&'(* o5 4h(r( 'h( MS !&rr(n' " r(*i)(*. .or GP%S 'h( MCC an) 'h( M/C o5 'h( SGS/. 3GPP-SGS/-MCC-M/C 3GPP TS 29.0#1 B11C .or 3GPP EPS 'h( MCC an) 'h( M/C +ro7i)() -" 'h( *(r7ing ga'(4a" (SGG). ;n)i!a'(* )('ai * o5 4h(r( 'h( UE i* !&rr(n' " 3GPP-U*(r-Lo!a'ion-;n5o 3GPP TS 29.0#1 B11C o!a'() ((.g. S,; or CG;),Co)ing *ha -( )on( a* )(5in() in 3GPP TS 29.274 B33C Ca ()-S'a'ion-;) %.C 400$ B12C Th( P6/ 'h( &*(r i* !onn(!'() 'o. Th( a!'ion a++ i() -" 'h( PCE. 4h(n 'h( &*(rA* .ina -Uni'-,!'ion %.C 400# B14C a!!o&n' !anno' !o7(r 'h( *(r7i!( !o*'. Th( 7a i) ro&'a- ( ;P74 a))r(** 'ha' i* a++ i!a- ( 5or 'h( ;P . o4* 'o4ar)* 'h( UE a' 'h( PCE.. Th( PC%. *ha &*( 'hi* a))r(** 'o i)(n'i5" 'h( !orr(!' ;P-C,/ *(**ion (*(**ion -in)ing). .or (2a9+ (, .ra9()-;P-,))r(** %.C 400$ B12C 'h( ;P a))r(** 9a" a!'&a " -( 'ha' o5 'h( n('4or< in'(r5a!( o5 a /,T )(7i!( -('4((n 'h( UE an) 'h( GG. Th( 7a &(* 02........ an) 02.......E ar( no' a++ i!a- ( a* )(*!ri-() in %.C 400$ B12C. , 7a i) 5& ;P7# a))r(** 'ha' i* a++ i!a- ( 'o an ;P 5 o4 or ;P 5 o4* 'o4ar)* 'h( UE a' 'h( PCE.. Th( PC%. *ha &*( 'hi* a))r(** 'o i)(n'i5" 'h( !orr(!' ;P-C,/ *(**ion (*(**ion -in)ing, r(5(r 'o 3GPP TS 29.213 B9C). .or (2a9+ (, 'h( ;P a))r(** 9a" a!'&a " -( 'ha' o5 'h( n('4or< in'(r5a!( o5 a /,T .ra9()-;P7#-Pr(5i2 %.C 400$ B12C )(7i!( -('4((n 'h( UE an) 'h( GG. Th( (n!o)ing o5 'h( 7a &( 4i'hin 'hi* 8!'(' S'ring '"+( ,VP *ha -( a* )(5in() in %.C 31#2 B20C, ! a&*( 2.3. Th( H%(*(r7()H, HPr(5i2-L(ng'hH an) HPr(5i2H 5i( )* *ha -( in! &)() in 'hi* or)(r. Th( ,. *ha *(' 'h( DPr(5i2 L(ng'hE 'o 12> an) (n!o)( 'h( ;P7# a))r(** o5 'h( UE 4i'hin 'h( DPr(5i2E 5i( ). Th( 7o &9( 'hr(*ho )* 5or *+on*or() )a'a !onn(!'i7i'". 8n " CC-To'a -8!'('* or on( o5 'h( Gran'()-S(r7i!(-Uni' %.C 400# B14C CC-;n+&'-8!'('* an) CC-8&'+&'-8!'('* ,VP* ar( r(&*(). Thi* ,VP *ha ha7( 'h( AMA -i' ! (ar(). ;P-C,/-T"+( 3GPP TS 29.212 B>C ;P-C,/ '"+( o5 'h( &*(r. ;n)i!a'( 4hi!h %a)io ,!!(** T(!hno og" i* %,T-T"+( 3GPP TS 29.212B>C !&rr(n' " *(r7ing 'h( UE. Th( 7(n)or-i) *ha -( *(' 'o ETS; (13019) B1$C. Th( *&++or' o5 'hi* ,VP *ha -( a)7(r'i*() in 'h( %(*(r7a'ion-Priori'" TS 1>3.017 B1$C !a+a-i i'i(* (2!hang( 9(!hani*9* (CE%3CE,) -" in! &)ing 'h( ETS; +ara9('(r in 'h( S&++or'()V(n)or-;) ,VP. Th( i)(n'i5i!a'ion o5 'h( *&-*!ri+'ion (;MS;, S&-*!ri+'ion-;) %.C 400# B14C MS;S6/, ('!.) ;5 +r(*(n', 'hi* ,VP in5or9* 'h( )(*'ina'ion ho*' S&++or'()-.(a'&r(* 3GPP TS 29.229 B2$C a-o&' 'h( 5(a'&r(* 'ha' 'h( origin ho*' r(?&ir(* 'o *&!!(**5& " !o9+ ('( 'hi* !o99an) (2!hang(. Th( 9(a*&r() 7o &9( 5or *+on*or() )a'a !onn(!'i7i'". 8n " CC-To'a -8!'('* or on( o5 'h( U*()-S(r7i!(-Uni' %.C 400# B14C CC-;n+&'-8!'('* an) CC-8&'+&'-8!'('* ,VP* ar( r(&*(). Thi* ,VP *ha ha7( 'h( AMA -i' ! (ar(). /8TE 10 ,VP* 9ar<() 4i'h H%( >H ar( a++ i!a- ( a* )(*!ri-() in ! a&*( $.4.1. /8TE 20 ,VP* 9ar<() 4i'h HS+on*or()Conn(!'i7i'"H ar( a++ i!a- ( 5or *+on*or() )a'a !onn(!'i7i'".

S+on*or()Co nn(!'i7i'"

%( >

%( > S+on*or()Co nn(!'i7i'"

3GPP

elease ##

3%

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

$.4.1 U*( o5 'h( S&++or'()-.(a'&r(* ,VP on 'h( %2 r(5(r(n!( +oin'


The "upported@7eatures .?P is used durin session establishment to inform the destination host about the reDuired and optional features that the ori in host supports. The client shall- in the first reDuest of a :iameter session indicate the set of supported features. The server shall- in the first answer within the :iameter session indicate the set of features that it has in common with the client and that the server shall support within the same :iameter session. .ny further command messa es shall always be compliant with the list of supported features indicated in the "upported@7eatures .?Ps durin session establishment. 7eatures that are not advertised as supported shall not be used to construct the command messa es for that :iameter session. 3nless otherwise stated- the use of the "upported@7eatures .?P on the /( reference point shall be compliant with the reDuirements for dynamic discovery of supported features and associated error handlin on the 1( reference point as defined in clause <.*., of 3GPP T" *>.**> E*9F. The base functionality for the /( reference point is the 3GPP /el@< standard and a feature is an e(tension to that functionality. &f the ori in host does not support any features beyond the base functionality- the "upported@7eatures .?P may be absent from the /( commands. .s defined in clause <.,., of 3GPP T" *>.**> E*9F- when e(tendin the application by addin new .?Ps for a feature- the new .?Ps shall have the M bit cleared and the .?P shall not be defined mandatory in the command .0'7. .s defined in 3GPP T" *>.**> E*9F- the "upported@7eatures .?P is of type rouped and contains the ?endor@&d7eature@5ist@&: and 7eature@5ist .?Ps. On the /( reference point- the "upported@7eatures .?P is used to identify features that have been defined by 3GPP and hence- for features defined in this document- the ?endor@&d .?P shall contain the vendor &: of 3GPP (,+8,9). &f there are multiple feature lists defined for the /( reference point- the 7eature@5ist@&: .?P shall differentiate those lists from one another. On receivin an initial reDuest application messa e- the destination host shall act as defined in clause <.*., of 3GPP T" *>.**> E*9F. The followin e(ceptions apply to the initial ../H... command pairB @ &f the .7 supportin post@/el@< /( functionality is able to interoperate with a P1/7 supportin /el@<- the ../ shall include the features supported by the .7 within "upported@7eatures .?P(s) with the SMT bit cleared. Otherwise- the ../ shall include the supported features within the "upported@7eatures .?P(s) with the M@bit set.

'OT2 ,B One instance of "upported@7eatures .?P is needed per 7eature@5ist@&:. @ &f the ../ command does not contain any "upported@7eatures .?P(s) and the P1/7 supports /el@< /( functionality- the ... command shall not include the "upported@7eatures .?P. &n this case- both .7 and P1/7 shall behave as specified in the /el@< version of this document. &f the ../ command contains the "upported@7eatures .?P(s)- the P1/7 shall include the "upported@7eatures .?P(s) in the ... command- with the $M$ bit cleared- indicatin only the features that both the P1/7 and .7 support.

'OT2 *B The client will always declare all features that are supported accordin to table 9.8.,.,. Ghen more than one feature identifyin a release is supported by both .7 and P1/7- the .7 will wor# accordin to the latest common supported release. Once the P1/7 and .7 have ne otiated the set of supported features durin session establishment- the set of common features shall be used durin the lifetime of the :iameter session. The table below defines the features applicable to the /( interfaces for the feature list with a 7eature@5ist@&: of ,.

3GPP

elease ##

33

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

Ta1le -'('#'#4 0eatures of 0eature,:ist,;3 # used in !


0eature 1it 0 0eature %( > 7<2 M 3escription

Thi* 5(a'&r( in)i!a'(* 'h( *&++or' o5 'h( -a*( 3GPP %( -> 5&n!'iona i'", in! &)ing 'h( ,VP* an) !orr(*+on)ing +ro!()&r(* *&++or'() -" 'h( -a*( 3GPP %( -7 %2 *'an)ar), -&' (2! &)ing 'ho*( 5(a'&r(* r(+r(*(n'() -" *(+ara'( 5(a'&r( -i'*. ,VP* in'ro)&!() 4i'h 'hi* 5(a'&r( ar( 9ar<() 4i'h H%( >H in Ta- ( $.4.1 1 %( 9 M Thi* 5(a'&r( in)i!a'(* 'h( *&++or' o5 'h( -a*( 3GPP %( -9 5&n!'iona i'", in! &)ing 'h( ,VP* an) !orr(*+on)ing +ro!()&r(* *&++or'() -" 'h( %( > 5(a'&r( -i', -&' (2! &)ing 'ho*( 5(a'&r(* r(+r(*(n'() -" *(+ara'( 5(a'&r( -i'*. 2 Pro7,.*igna . o4 8 Thi* in)i!a'(* *&++or' 5or 'h( 5(a'&r( o5 +ro7i*ioning o5 ,. *igna ing 5 o4 in5or9a'ion a* )(*!ri-() in *&-! a&*( 4.4.$a. ;5 'h( PC%. *&++or'* 'hi* 5(a'&r( 'h( ,. 9a" +ro7i*ion ,. *igna ing 5 o4 in5or9a'ion. /8TE0 Thi* 5(a'&r( i* &*() -" 'h( ;MS %(*'ora'ion Pro!()&r(* 'o +ro7i)( 'o 'h( P6/-Ga'(4a" 'h( a))r(** o5 'h( P-CSC. *( (!'() -" 'h( UE, r(5(r 'o 3GPP TS 23.3>0 B2>C. 3 S+on*or()Conn(!'i7i'" 8 Thi* 5(a'&r( in)i!a'(* *&++or' 5or *+on*or() )a'a !onn(!'i7i'" 5(a'&r(. ;5 'h( PC%. *&++or'* 'hi* 5(a'&r(, 'h( ,. 9a" +ro7i)( *+on*or() )a'a !onn(!'i7i'" 'o 'h( *&-*!ri-(r. 4 %( 10 M Thi* 5(a'&r( in)i!a'(* 'h( *&++or' o5 'h( -a*( 3GPP %( -10 5&n!'iona i'", in! &)ing 'h( ,VP* an) !orr(*+on)ing +ro!()&r(* *&++or'() -" 'h( %( > an) %( 9 5(a'&r( -i', -&' (2! &)ing 'ho*( 5(a'&r(* r(+r(*(n'() -" *(+ara'( 5(a'&r( -i'*. ,VP* in'ro)&!() 4i'h 'hi* 5(a'&r( ar( 9ar<() 4i'h H%( 10H in 'a- ( $.3.1. $ /('Lo! 8 Thi* 5(a'&r( in)i!a'(* 'h( *&++or' o5 'h( ,!!(** /('4or< ;n5or9a'ion %(+or'ing. # E2'(n)().i '(r 8 Thi* 5(a'&r( in)i!a'(* 'h( *&++or' 5or 'h( o!a (i.(. UE) a))r(** an) 9a*< -(ing +r(*(n' in 5i '(r* *igna () -('4((n n('4or< an) UE. .(a'&r( -i'0 Th( or)(r n&9-(r o5 'h( -i' 4i'hin 'h( .(a'&r(-Li*' ,VP 4h(r( 'h( (a*' *igni5i!an' -i' i* a**ign() n&9-(r D0E. .(a'&r(0 , *hor' na9( 'ha' !an -( &*() 'o r(5(r 'o 'h( -i' an) 'o 'h( 5(a'&r(, (.g. HEPSH. M380 6(5in(* i5 'h( i9+ (9(n'a'ion o5 'h( 5(a'&r( i* 9an)a'or" (HMH) or o+'iona (H8H). 6(*!ri+'ion0 , ! (ar '(2'&a )(*!ri+'ion o5 'h( 5(a'&r(.

$.$ %2 *+(!i5i! E2+(ri9(n'a -%(*& '-Co)( ,VP 7a &(*


/71 39== E,+F specifies the 2(perimental@/esult .?P containin ?endor@&: .?P and 2(perimental@/esult@1ode .?P. The 2(perimental@/esult@1ode .?P (.?P 1ode *>=) is of type 3nsi ned3* and contains a vendor@assi ned value representin the result of processin a reDuest. The ?endor@&: .?P shall be set to 3GPP (,+8,9). "pecific values of the /( specific 2(perimental@/esult@1ode .?P areB &'?.5&:L"2/?&12L&'7O/M.T&O' (9+;,) The P1/7 rejects new or modified service information the service information provided by the .7 is invalid or insufficient for the server to perform the reDuested action. 7&5T2/L/2"T/&1T&O'" (9+;*) The P1/7 rejects new or modified service information because the 7low@:escription .?P(s) cannot be handled by the server because restrictions defined in clause 9.3.< are not observed. /2J32"T2:L"2/?&12L'OTL.3TAO/&N2: (9+;3) The P1/7 rejects new or modified service information because the reDuested service- as described by the service information provided by the .7- is not consistent with either the related subscription informationoperator defined policy rules andHor the supported features in the &P@1.' networ#. :3P5&1.T2:L.7L"2""&O' (9+;8)

3GPP

elease ##

3(

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The P1/7 rejects a new /( session setup because the new /( session relates to an .7 session with another related active /( session- e. . if the .7 provided the same .7 char in identifier for this new /( session that is already in use for the other on oin /( session. &P@1.'L"2""&O'L'OTL.?.&5.052 (9+;9) The P1/7 rejects a new /( session setup when it fails to associate the described service &P flows within the session information received from the .7 to an e(istin &P@1.' session. 3'.3TAO/&N2:L'O'L2M2/G2'1ML"2""&O' (9+;;) The P1/7 rejects a new /( session setup because the session bindin function associated a non@2mer ency &M" session to an &P@1.' session established to an 2mer ency .P'. 3'.3TAO/&N2:L"PO'"O/2:L:.T.L1O''21T&?&TM (9+;<) The P1/7 rejects a new /( session setup because the P1/7 canTt authori!e the sponsored data connectivity based on the sponsored data connectivity profile or the operator policy (e. . the sponsored data connectivity not authori!ed in the roamin case).

$.# %2 9(**ag(*
2(istin :iameter command codes from the :iameter base protocol /71 39== E,+F and the '."/2J :iameter application (/71 8++9 E,*F) are used with the /( specific .?Ps. .n /( specific .uth@.pplication id is used to ether with the command code to identify the /( messa es. 'OT2 ,B The notion of '." ('etwor# .ccess "erver) is not used here- '."/2J is just used for protocol purposes- not for its functional meanin . 'OT2 *B "ome of the .?Ps included in the messa es formats below are in bold to hi hli ht that these .?Ps are used by this specific protocol and do not belon to the ori inal :iameter 0ase Protocol /71 39== E,+F. 'OT23B Multiple instances of the "ubscription@&d .?P in the ../ or /./ command correspond to multiple types of identifier for the same subscriber- for e(ample &M"& and M"&":'.

$.#.1 ,,-%(?&(*' (,,%) !o99an)


The ../ command- indicated by the 1ommand@1ode field set to *;9 and the $/$ bit set in the 1ommand 7la s field- is sent by an .7 to the P1/7 in order to provide it with the "ession &nformation. Messa e 7ormatB
<AA-7e8"est> ::= < .ia*eter Header: 2>5A 7BCA PDE > < 3ession-Id > A"th-A++!ication-Id # 1rigin-Host # 1rigin-7ea!* # .estination-7ea!* # % .estination-Host ' % IP-.o*ain-Id ' [ AF-Application-Identifier ] *[ Media-Component-Description ] [ Service-Info-Status ] [ AF-Charging-Identifier ] [ SIP-For ing-Indication ] *[ Specific-Action ] *[ Su!scription-Id ] *[ Supported-Features ] [ "eservation-Priorit# ] [ Framed-IP-Address ] [ Framed-IPv$-Prefi% ] [ Called-Station-Id ] [ Service-&"' ] [ Sponsored-Connectivit#-Data ] [ MPS-Identifier ] [ "%-"e(uest-)#pe ] *[ "e(uired-Access-Info ] % 1rigin-3tate-Id '

3GPP

elease ##
$% Pro65-Info ' $% 7o"te-7ecord ' $% AVP '

3-

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

$.#.2 ,,-,n*4(r (,,,) !o99an)


The ... command- indicated by the 1ommand@1ode field set to *;9 and the $/$ bit cleared in the 1ommand 7la s field- is sent by the P1/7 to the .7 in response to the ../ command. Messa e 7ormatB
<AA-Answer> ::= < .ia*eter Header: 2>5A PDE > < 3ession-Id > A"th-A++!ication-Id # 1rigin-Host # 1rigin-7ea!* # % 7es"!t-Code ' % B6+eri*enta!-7es"!t ' *[ Access-'et*or -Charging-Identifier ] [ Access-'et*or -Charging-Address ] [ Accepta!le-Service-Info ] [ IP-CA'-)#pe ] % 7A4-45+e ' *[ Flo*s ] $% 3"++orted-&eat"res ' $% C!ass ' % Brror-)essage ' % Brror-7e+orting-Host ' $% &ai!ed-AVP ' % 1rigin-3tate-Id ' $% 7edirect-Host ' % 7edirect-Host--sage ' % 7edirect-)a6-Cache-4i*e ' $% Pro65-Info ' $% AVP '

$.#.3 %(-,&'h-%(?&(*' (%,%) !o99an)


The /./ command- indicated by the 1ommand@1ode field set to *9= and the $/$ bit set in the 1ommand 7la s field- is sent by the P1/7 to the .7 in order to indicate an /( specific action. Messa e 7ormatB
<7A-7e8"est> ::= < .ia*eter Header: 25FA 7BCA PDE > < 3ession-Id > 1rigin-Host # 1rigin-7ea!* # .estination-7ea!* # .estination-Host # A"th-A++!ication-Id # $ 3+ecific-Action # *[ Access-'et*or -Charging-Identifier ] [ Access-'et*or -Charging-Address ] *[ Flo*s ] *[ Su!scription-Id ] [ A!ort-Cause ] [ IP-CA'-)#pe ] [ "A)-)#pe ] [ Sponsored-Connectivit#-Data ] [ +,PP-&ser--ocation-Info ] [ +,PP-MS-)ime.one ] [ +,PP-S,S'-MCC-M'C ] % 1rigin-3tate-Id ' $% C!ass ' $% Pro65-Info ' $% 7o"te-7ecord ' $% AVP '

$.#.4 %(-,&'h-,n*4(r (%,,) !o99an)


The /.. command- indicated by the 1ommand@1ode field set to *9= and the $/$ bit cleared in the 1ommand 7la s field- is sent by the .7 to the P1/7 in response to the /./ command. Messa e 7ormatB

3GPP

elease ##
<7A-Answer> ::= < .ia*eter Header: 25FA PDE > < 3ession-Id > 1rigin-Host # 1rigin-7ea!* # % 7es"!t-Code ' % B6+eri*enta!-7es"!t ' *[ Media-Component-Description ] [ Service-&"' ] % 1rigin-3tate-Id ' $% C!ass ' % Brror-)essage ' % Brror-7e+orting-Host ' $% 7edirect-Host ' % 7edirect-Host--sage ' % 7edirect-)a6-Cache-4i*e ' $% &ai!ed-AVP ' $% Pro65-Info ' $% AVP '

3.

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

$.#.$ S(**ion-T(r9ina'ion-%(?&(*' (ST%) !o99an)


The "T/ command- indicated by the 1ommand@1ode field set to *<9 and the $/$ bit set in the 1ommand 7la s field- is sent by the .7 to inform the P1/7 that an established session shall be terminated. Messa e 7ormatB
<34-7e8"est> ::= < .ia*eter Header: 2/5A 7BCA PDE > < 3ession-Id > 1rigin-Host # 1rigin-7ea!* # .estination-7ea!* # A"th-A++!ication-Id # 4er*ination-Ca"se # % .estination-Host ' $% C!ass ' % 1rigin-3tate-Id ' $% Pro65-Info ' $% 7o"te-7ecord ' $% AVP '

$.#.# S(**ion-T(r9ina'ion-,n*4(r (ST,) !o99an)


The "T. command- indicated by the 1ommand@1ode field set to *<9 and the $/$ bit cleared in the 1ommand 7la s field- is sent by the P1/7 to the .7 in response to the "T/ command. Messa e 7ormatB
<34-Answer> ::= < .ia*eter Header: 2/5A PDE > < 3ession-Id > 1rigin-Host # 1rigin-7ea!* # % 7es"!t-Code ' % Brror-)essage ' % Brror-7e+orting-Host ' $ % &ai!ed-AVP ' [ Sponsored-Connectivit#-Data ] % 1rigin-3tate-Id ' $% C!ass ' $% 7edirect-Host ' % 7edirect-Host--sage ' % 7edirect-)a6-Cache-4i*e ' $% Pro65-Info ' $% AVP '

$.#.7 ,-or'-S(**ion-%(?&(*' (,S%) !o99an)


The ."/ command- indicated by the 1ommand@1ode field set to *<8 and the $/$ bit set in the 1ommand 7la s field- is sent by the P1/7 to inform the .7 that bearer for the established session is no lon er available. Messa e 7ormatB
<A3-7e8"est> ::= < .ia*eter Header: 2/GA 7BCA PDE > < 3ession-Id > 1rigin-Host # 1rigin-7ea!* #

3GPP

elease ##
.estination-7ea!* # .estination-Host # A"th-A++!ication-Id # A!ort-Cause 0 1rigin-3tate-Id ' Pro65-Info ' 7o"te-7ecord ' AVP '

3*

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

/ % $% $% $%

$.#.> ,-or'-S(**ion-,n*4(r (,S,) !o99an)


The .". command- indicated by the 1ommand@1ode field set to *<8 and the $/$ bit cleared in the 1ommand 7la s field- is sent by the .7 to the P1/7 in response to the ."/ command. Messa e 7ormatB
<A3-Answer> ::= < .ia*eter Header: 2/GA PDE > < 3ession-Id > 1rigin-Host # 1rigin-7ea!* # % 7es"!t-Code ' % 1rigin-3tate-Id ' % Brror-)essage ' % Brror-7e+orting-Host ' $% &ai!ed-AVP ' $% 7edirect-Host ' % 7edirect-Host--sage ' % 7edirect-)a6-Cache-4i*e ' $% Pro65-Info ' $% AVP '

3GPP

elease ##

35

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

,nn(2 , (nor9a'i7()0 ;MS %( a'() P-CSC. Pro!()&r(* o7(r %2 ,.1 Pro7i*ion o5 S(r7i!( ;n5or9a'ion a' P-CSC.

The P@1"17 shall send service information to the P1/7 upon every "&P messa e that includes an ":P answer payload for the purpose of authori!in the &P flows and the Jo" resources reDuired for a ne otiated &M" session- unless the ":P payload only relates to a circuit@switched bearer (i.e. IcKI line set to IP"T'I and an ImKI line set to IP"T'I- refer to 3GPP T" *8.*>* E*;F). The service information shall be derived both from the ":P offer and the ":P answer. This ensures that the P1/7 receives proper information to perform media authori!ation for all possible &M" session set@up scenarios- and that the P1/7 is also capable of handlin session modifications. The P@1"17 may include the "ervice@ &nfo@"tatus .?P with the value set to 7&'.5L"2/?&12L&'7O/M.T&O'. .dditionally- the P@1"17 may send service information to the P1/7 when receivin a "&P messa e that includes an ":P offer payload for the purpose of performin an early bandwidth authori!ation chec# or for enablin pre@ authori!ation for a 32 terminated &M" session establishment or modification with 32 initiated resource reservation. The P@1"17 shall send service information to the P1/7 when receivin a "&P messa e that includes an ":P offer payload when the &M" session is an MP" session that reDuires priority treatment. 7or a 32 terminated session the P@ 1"17 may send the service information derived from the ":P offer when the ":P offer either does not include any preconditions information or includes preconditions information indicatin that the local preconditions (i.e. the preconditions related to the remote peer) are already met. &n this case- the P@1"17 shall derive the service information only from the ":P offer and shall include the "ervice@&nfo@"tatus .?P with the value set to P/25&M&'./M "2/?&12 &'7O/M.T&O'. 'OT2B 7or a 32 terminated session setup- when the ":P offer either does not include any preconditions information or includes preconditions information indicatin that the local preconditions (i.e. the preconditions related to the remote peer) are already met- the terminatin 32 can reDuest a resource modification prior to sendin the ":P answer. 2ven if the &P address and port information in the session information derived from the ":P offer can be insufficient for P11 rule authori!ation- the policy to handle such 32 initiated reDuests at the P1/7 can ta#e into account the fact that an &M" session establishment is on oin - for instance in decidin whether to authori!e the reDuest and in selectin an appropriate char in #ey and a atin policy.

The P@1"17 shall derive 7low@:escription .?P within the service information from the ":P as followsB @ .n uplin# 7low@:escription .?P shall be formed as followsB The destination address shall be ta#en from the ":P information received by the P@1"17 in downlin# direction- while the source &P address may be formed from the address present in the ":P received by the P@1"17 in uplin# direction (ta#in into account only the ;8 bit prefi( of the &Pv; address) "ource and destination ports shall be derived accordin to rules provided in 3GPP T" *>.*,3 E>F clause ;.*. .ssumin 32 . sends an ":P to 32 0- the P1/7 of 32 0 uses the address present in this ":P for the destination address of 32 0$s uplin# 7low@:escription .?P- while the P1/7 of the 32 . uses the ;8 bit prefi( of the same address for the source address of 32 .$s uplin# 7low@:escription .?P. &f the source address is not formed from the ;8 bit prefi(- the source address shall be wildcarded.

2O.MP52 ,B

. downlin# 7low@:escription .?P shall be formed as followsB The destination address shall be ta#en from the ":P information received by the P@1"17 in uplin# direction- while the source &P address may be formed (in order to reduce the possibilities of bearer misuse) from the destination address in the ":P received by the P@ 1"17 in downlin# direction (ta#in into account only the ;8 bit prefi( of the &Pv; address) "ource and destination ports shall be derived accordin to rules provided in 3GPP T" *>.*,3 E>F clause ;.*.

3GPP

elease ##

3&

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

2O.MP52 *B

.ssumin 32 . sends an ":P to 32 0- the P1/7 of 32 . uses the address present in this ":P for the destination address of 32 .$s downlin# 7low@:escription .?P- while the P1/7 of 32 0 uses the ;8 bit prefi( of the same address for the source address of 32 0$s downlin# 7low@:escription .?P. &f the source address is not formed from the ;8 bit prefi(- the source address shall be wildcarded.

The P@1"17 shall derive the bandwidth information within the service information- from the IbK."I ":P parameteras detailed in 3GPP T" *>.*,3 E>F clause ;.*. 7or the possibly associated /T1P &P flows- the P@1"17 shall use the ":P IbK//I and IbK/"I parameters- if present- as specified in 3GPP T" *>.*,3 E>F clause ;.*. The IbK."I- IbK//I and IbK/"I parameters in the ":P contain all the overhead comin from the &P@layer and the layers above- e. . &P- 3:P/TP and /T1P payload- or &P- 3:P and /T1P. Aowever- if service information is received containin the IbKT&."I ":P parameter that corresponds to an ":P answer payload- and if the P@1"17 supports this parameter- the P@1"17 may derive the bandwidth from this parameter rather than from the IbK."I ":P parameter- as detailed in 3GPP T" *>.*,3 E>F clause ;.*. Ghen available- the P@1"17 shall also indicate to P1/7- as a complement to the "ervice &nformation- the &M" 1ommunication "ervice &dentifier within the .7@.pplication@&dentifier .?P. The ori inatin P@1"17 shall ta#e the &M" 1ommunication "ervice &dentifier value from the "&P response. The terminatin P@1"17 shall ta#e the &M" 1ommunication "ervice &dentifier value from the "&P reDuest. Otherwise- the P@1"17 may not be able to provide an &M" 1ommunication "ervice &dentifier value to the P1/7. The format and specific headers where &M" communication service identifiers are transported within "&P are defined in 3GPP T" *8.**> E,<F. &f the "ervice@3/' .?P does not include an emer ency service 3/'- i.e. a top@level service type of IsosI as specified in &2T7 /71 9+3, E*,F and possibly additional sub@service information on the type of the emer ency service and the P1/7 binds the &M" service session to an &P@1.' session established to an 2mer ency .P'- the P1/7 shall return an ... command with 2(perimental@/esult@1ode .?P set to the value 3'.3TAO/&N2:L'O'L2M2/G2'1ML"2""&O' to the P@1"17. 3pon receivin an ... with 2(perimental@ /esult@1ode .?P set to the value 3'.3TAO/&N2:L'O'L2M2/G2'1ML"2""&O' the P@1"17 shall apply the procedures defined in 3GPP T" *8.**> E,<F. 'OT2B The P1/7 determines whether an &P@1.' session is established to an 2mer ency .P' based on the information received over G( and operator confi uration.

The P1/7 may decide not to authori!e reDuested service information. The P1/7 will indicate it to the P@1"17 by sendin an ..@.nswer with 2(perimental@/esult@1ode .?P set to the value /2J32"T2:L"2/?&12L'OTL.3TAO/&N2:. 3pon receivin an ..@.nswer with 2(perimental@/esult@1ode .?P set to the value /2J32"T2:L"2/?&12L'OTL.3TAO/&N2: the P@1"17 shall apply the procedures defined in 3GPP T" *8.**> E,<F.

,.2

Ena- ing o5 ;P . o4*

Prior to the completion of the "&P session set@up- i.e. until the *++ O% (&'?&T2) or any other *(( response is receivedthe P@1"17 may enable or disable media &P flows dependin on operator policy- thus allowin or forbiddin early media in forward andHor bac#ward direction. Only to disable early media- the P@1"17 may modify the values of the 7low@"tatus .?Ps derived from ":P accordin to 3GPP T" *>.*,3 E>F clause ;.*. &f the P@1"17 chooses to modify the values- the P@1"17 shall store the last received ":P. Ghen a *(( response is received- the P@1"17 shall enable all media &P flows accordin to the direction attribute within the last received ":P- as specified in 3GPP T" *>.*,3 E>F clause ;.*. Ghen a *(( response is received and the P@1"17 previously provided modified values of the 7low@"tatus .?Ps in the session information- the P@1"17 shall provide service information with values of the 7low@"tatus .?Ps correspondin to the last received ":P. 'OT2B &n most cases a *(( response is a *++ O%.

&f the P@1"17 receives ":P answers after the completion of the "&P session set@up- i.e. after the *++ O% (&'?&T2) or any other *(( response is received- the P@1"17 shall provide the 7low@"tatus .?P- based on the last received ":P answer. The 7low@"tatus .?P as derived from the ":P accordin to 3GPP T" *>.*,3 E>F clause ;.*.

3GPP

elease ##

(+

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

,.3

S&++or' 5or S;P 5or<ing

The P@1"17 shall be able to handle for#in when P11 is applied. 7or#in can occur as specified in 3GPP T" *3.**= E,;F. The related 32 procedures are described in 3GPP T" *8.**> E,<F.

,.3.1 PCC r& ( +ro7i*ioning 5or (ar " 9()ia 5or 5or<() r(*+on*(*
Ghen a "&P session has been ori inated by a connected 32- the P@1"17 may receive multiple provisional responses due to for#in before the first final answer is received. Multiple early media session may be established durin this process. The 32 and the P@1"17 become aware of the for#in only when a subseDuent provisional response arrives for a new early dialo ue. .fter the first early media session is established- for each subseDuent provisional response establishin an additional early media session-- the P@1"17 shall use an .. reDuest within the e(istin :iameter session containin the "&P@7or#in @&ndication .?P with value "2?2/.5L:&.5OG32" and include the service information derived from the latest provisional response. The P@1"17 shall also provision the service information derived from any subseDuent ":P offer@answer e(chan e within an early dialo ue (e. . in P/.1% and O%(P/.1%)- or 3P:.T2 and O%(3P:.T2) ) usin an .. reDuest within the e(istin :iameter session containin the "&P@7or#in @&ndication .?P with value "2?2/.5L:&.5OG32" and the derived service information. Ghen receivin an .. reDuest containin the "&P@7or#in @&ndication .?P with value "2?2/.5L:&.5OG32"- the P1/7 shall identify the e(istin authori!ation information for that .7 session. The P1/7 shall send additional P11 /ules or individual service data flow filters to already provide P11 rules as reDuired by the 7low :escription .?Ps within the session information to the P127. The P1/7 shall authori!e any additional media components and any increased Jo" reDuirements for the previously authori!ed media components- as reDuested within the service information. The P1/7 shall authori!e the ma(imum bandwidth reDuired by any of the dialo ues- but not the sum of the bandwidths reDuired by all dialo ues. Thus- the Jo" authori!ed for a media component is eDual to the hi hest Jo" reDuested for that media component by any of the for#ed responses. The P1/7 shall open or close the ates for service flows dependin on the flow status that is bein provisioned. Aowever- if a flow &: has been enabled in uplin# or downlin# direction or both way within previous service information- it shall remain enabled even if the P1/7 receives service information that disable this flow &: within an .. reDuest containin the "&P@7or#in @&ndication .?P with value "2?2/.5L:&.5OG32".

,.3.2 U+)a'ing 'h( +ro7i*ion() PCC r& (* a' 'h( 5ina an*4(r
The P@1"17 shall store the ":P information for each early dialo ue separately till the first final "&P answer is received. Then the related early dialo ue is pro ressed to an established dialo ue to establish the final "&P session. .ll the other early dialo ues are terminated. The service information for the "&P session is updated to match the reDuirements of the remainin early dialo ue only. Ghen receivin the first final "&P response- the P@1"17 shall send an .. reDuest without the "&P@7or#in @&ndication .?P and include the service information derived from the ":P correspondin to the dialo ue of the final response. The P@1"17 shall provision the full service information includin the applicable 7low@:escription .?P(s) and 7low@"tatus .?P(s). Ghen receivin an .. reDuest with no "&P@7or#in @&ndication .?P or with a "&P@7or#in @&ndication .?P with value "&'G52L:&.5OG32- the P1/7 shall update installed P11 /ules information and .uthori!ed@Jo" information to match only the reDuirements of the service information within this .. reDuest. The P1/7 should immediately remove P11 /ule(s) or individual service data flow filters not matchin &P flow(s) in the updated "ervice &nformation- to reduce the ris# for initial clippin of the media stream- and to minimi!e possible misuse of resources. The P1/7 shall also open or close the ates for service flows accordin to the flow status in the received service information.

3GPP

elease ##

(#

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

,.4

/o'i5i!a'ion o5 ,. Signa ing Tran*9i**ion Pa'h S'a'&*

Ghen the P@1"17 receives an initial /2G&"T2/ "&P messa e from an attached 32- the P@1"17 may subscribe to notifications of the status of the .7 "i nallin transmission path usin the procedures specified in clause 8.8.9. Once the P@1"17 has subscribed- the P@1"17 may receive notifications from the P1/7 accordin to clause 8.8.;.3. The P@1"17 shall cancel the subscription to notification of the status of the .7 "i nallin transmission path when the .7 "i nallin to that particular user is terminated (i.e. when the user is de@/2G&"T2/2: from the &M 1' subsystem). Ghen the P@1"17 receives a notification of loss of si nallin connectivity from the P1/7- the P@1"17 shall behave as defined in 3GPP T" *8.**> E,<F.

,.$

;n)i!a'ion o5 E9(rg(n!" S(**ion

. "&P &'?&T2 reDuest can contain a service 3/' as defined in &2T7 /71 9+3, E*,F within the reDuest 3/&. &f the service within this 3/' is IsosI- possibly with additional sub@service information- the P@1"17 shall provision this service and sub@service information within the "ervice@3/' .?P towards the P1/7. The P@1"17 may also provision possible information about other services received within the service 3/'.

,.#

/o'i5i!a'ion ;P-C,/ T"+( Chang(

Ghen the P@1"17 receives an initial /2G&"T2/ "&P messa e from an attached 32- the P@1"17 shall reDuest from the P1/7 the information about the type of &P@1.' the 32 is attached to usin the procedure specified in subclause 8.8.,. The P@1"17 shall also subscribe within the same ../ command operation to notifications for chan es of the &P@1.' type used by the 32. The P@1"17 shall include a "pecific@.ction .?P in the ../ that is set to the value of &P@ 1.'L1A.'G2. Ghen the P@1"17 receives the ..@.nswer from the P1/7- the P@1"17 stores the &P@1.' type information and the /.T type information (if also provided by the P1/7) and behaves as defined in 3GPP T" *8.**> E,<F. The P@1"17 may receive notifications for chan es of the &P@1.' type from the P1/7 accordin to clause 8.8.;.8. Ghen the P@1"17 receives a notification of the chan e of the &P@1.' used by the 32- the P@1"17 stores the new &P@ 1.' type information and behaves as defined in 3GPP T" *8.**> E,<F. The P@1"17 shall cancel the subscription to notification for chan es of the &P@1.' type used by the 32 when the user is de@/2G&"T2/2: from the &M 1' subsystem.

,.7

S&++or' 5or Ear " S(**ion )i*+o*i'ion S6P

,.7.1 G(n(ra
.s a networ# option- the P@1"17 may support the P11 procedures in the present 1lause to handle Iearly sessionI disposition type ":P- as standardised in &2T7 /71 3>9> E*<F.

,.7.2 S(r7i!( ;n5or9a'ion Pro7i*ioning 5or Ear " M()ia


The P@1"17 can receive Iearly sessionI disposition ":P in addition to IsessionI disposition ":P in "&P early dialo ues. The P@1"17 shall then provision service information derived both from the Iearly sessionI disposition ":P and IsessionI disposition ":P applyin the procedures in 1lauses ..,- ..*- and ..3- and in the present 1lause.

3GPP

elease ##

(%

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The P@1"17 shall apply the mappin rules in .nne( 0.,.*.*.* to derive the flow identifiers from Iearly sessionI disposition ":P. &f a sin le media line with one media type (e. . IaudioI or IvideoI) is contained in Iearly sessionI disposition ":P and a sin le media line with the same media type is contained in the IsessionI disposition ":P of the same "&P dialo ueand both media lines describe service flows of the same directionality (uplin#- downlin#- or bidirectional)- the P@1"17 should describe those ":P media lines in the same session information media component (with the same flow &:). The Iearly sessionI disposition ":P can also contain media lines of a type not included in the IsessionI disposition ":P- or several media lines of the same type. "uch media components shall be described in own media components in the service information. &f the P@1"17 desires to invo#e special policies or separate event notifications for an Iearly sessionI disposition media line- it may choose to provision a separate session information media component even if a media line with the same media type and directionality is contained in IsessionI disposition ":P. 'OT2 ,B . P1/7 is then li#ely to supply separate P11 rules for early media and the correspondin final media. This may lead to an over provisionin of resources durin call establishment and a subseDuent reconfi uration of the radio bearer- or even to a call failure if the e(tra resources are not authori!ed or available. &f the P@1"17 receives Iearly sessionI disposition ":P before any IsessionI disposition ":P and supplies service information derived from the Iearly sessionI disposition ":P at this point of time- it shall use dedicated media components relatin only to the Iearly sessionI disposition ":P in the service information. 'OT2 *B The IsessionI disposition ":P offer will freDuently occur before the Iearly sessionI disposition ":P offer- but can also occur in parallel or in e(ceptional cases afterwards. The IsessionI disposition ":P answer can be contained in the same "&P messa e as the Iearly sessionI disposition ":P offer- or can be sent in a *++ O% (&'?&T2)- i.e. after the Iearly sessionI disposition ":P answer. &f the P@1"17 includes any media component relatin both to Iearly sessionI disposition ":P and IsessionI disposition ":P in the service information- the P@1"17 shallB @ provision the service information derived from Iearly sessionI disposition ":P and the service information derived from IsessionI disposition ":P in separate /( ..@/eDuests- and shall send a new /( ..@/eDuest only after any previous /( ..@/eDuest has been ac#nowled edC and provision the first service information (either derived from Iearly sessionI disposition ":P or IsessionI disposition ":P) without the "&P@7or#in @&ndication .?P- or with the "&P@7or#in @&ndication .?P with value "&'G52L:&.5OG32C and provision all subseDuent service information durin on oin call establishment with the "&P@7or#in @&ndication .?P with value "2?2/.5L:&.5OG32"C and if an ":P answer has been received and 1odec@:ata .?Ps are provisioned within a Media@1omponent@ :escription .?P- provision a 1odec@:ata .?P derived from the correspondin offer to ether with a 1odec@ :ata .?P derived from the ":P answer.

@ @

'OT2 3B The P@1"17 needs to provision the service information derived from Iearly sessionI disposition ":P and the service information derived from IsessionI disposition ":P in separate /( ..@/eDuests because the encodin of the media@component does not allow for the simultaneous provisionin of two correspondin filters. 'OT2 8B The P1/7 will treat service information containin the "&P@7or#in @&ndication .?P as described in 1lause ..3.

,.7.3 U+)a'ing 'h( Pro7i*ion() S(r7i!( ;n5or9a'ion 4h(n 6ia og&( i* (*'a- i*h()
The P@1"17 shall store the ":P information for the IsessionI disposition type until the first final "&P answer is received. Then the early media described in the Iearly sessionI disposition type ":P are terminated.

3GPP

elease ##

(3

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The P@1"17 shall then update the service information to match the reDuirements of the media described in the IsessionI disposition type ":P onlyB @ &f the P@1"17 included any media component relatin both to Iearly sessionI disposition ":P and IsessionI disposition ":P in the service information- the P@1"17 shall send an .. reDuest without the "&P@7or#in @ &ndication .?P or with a "&P@7or#in @&ndication .?P with value "&'G52L:&.5OG32 and shall include the service information derived from the IsessionI disposition ":P. The P@1"17 shall provision the full service information includin the applicable 7low@:escription .?P(s) and 7low@"tatus .?P(s). The P@1"17 shall disable any media component(s) in the service information that relate to early media only by settin their flow status to IremovedI.

,.> Pro7i*ion o5 Signa ing . o4 ;n5or9a'ion a' P-CSC.


Ghen the P@1"17 has successfully concluded the initial re istration of an attached 32- i.e.- when the P@1"17 has sent to the 32 a "&P *++ (O%) response to the "&P /2G&"T2/ reDuest- the P@1"17 shall provision information about the "&P si nallin flows between the 32 and itself usin the procedure specified in subclause 8.8.9a. &f the P@1"17 already has an open /( :iameter session with the P1/7 related to the si nallin with the 32- e. . one that has been opened accordin to the procedure described in subclause ..; andHor in subclause ..8- the P@1"17 shall reuse the already open session to provision the "&P "i nallin &P 7low information. The P@1"17 shall ensure that for each si nallin &P flow information it provides- the 7low@:escription .?P shall accurately reflect the &P flow information as seen in the &P header Son the wireT. The P@1"17 shall set the value of the .7@"i nallin @Protocol .?P to $"&P$. Ghen the P@1"17 de@re isters the 32 and terminates "&P "i nallin to the 32- the P@1"17 shall de@provision the "&P "i nallin &P flow information from the P1/7 as described in subclause 8.8.9a.

,.9

Ian) ing o5 MPS S(**ion

Ghen the P@1"17 receives an authorised /esource@Priority header field or a temporarily authorised /esource@Priority header field containin an appropriate namespace and priority value in "&P si nalin - and reco ni!es the need for priority treatment as specified in 3GPP T" *8.**> E,<F- the P@1"17 shall include the MP"@&dentifier .?P and /eservation@Priority .?P in the ../ command towards the P1/7. The MP"@&dentifier .?P shall contain the national variant for MP" service name indicatin an MP" session. The /eservation@Priority .?P shall include the priority value of the related priority service. The /eservation@Priority .?P shall be populated with a default value if the priority value is un#nown. 'OT2 ,B ?arious mechanisms can be applied to reco ni!e the need for priority treatment in the P@1"17 (e. .based on the dialled di its)- accordin to national re ulation and networ# confi uration- as stated in 3GPP T" *8.**> E,<F. 'OT2 *B 5owest user priority value shall be mapped in the correspondin lowest enumerated value of the /eservation@Priority .?P. 3pon reception of a reDuest that reDuires MP" treatment- the P1/7 shall derive the P11HJo" /ules correspondin to the MP" session- as appropriate. The P1/7 shall ta#e specific actions on the correspondin &P@1.' to ensure that the MP" session is prioriti!ed- as described in 3GPP T" *>.*,* E=F- clause 8.9.,>.,.3. Ghen the P@1"17 terminates the MP" session- the P1/7 shall delete the P11HJo" /ules correspondin to the MP" session. The P1/7 shall revo#e the actions related to the prioriti!ation of the MP" session in the correspondin &P@ 1.'- as described in 3GPP T" *>.*,* E=F- clause 8.9.,>.,.3.

3GPP

elease ##

((

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

,nn(2 @ (nor9a'i7()0 . o4 i)(n'i5i(r*0 .or9a' )(5ini'ion an) (2a9+ (* @.1 .or9a' o5 a 5 o4 i)(n'i5i(r

@.1.1 G(n(ra
. flow identifier is e(pressed as a *@tuple as followsB UThe ordinal number of the position of the media component description in the ":& - The ordinal number of the &P flow(s) within the media component description assi ned in the order of increasin downlin# port numbers as detailed below V where both are numbered startin from ,. The encodin of the flow identifier is as indicated in 3GPP T" *8.++= E,*F. &f 32 and .7 share an al orithm for a iven application- which uarantees that 32 and .7 assi n the same ordinal number to each media component- the ordinal numbers of the &P 7lows within a media component shall be assi ned accordin to the followin rulesB @ .ll &P flow(s) or bidirectional combinations of two &P flow(s) within the media component- for which a downlin# destination port number is available- shall be assi ned ordinal numbers in the order of downlin# destination port numbers. .ll &P flows- where no downlin# destination port number is available- shall be assi ned the ne(t hi her ordinal numbers in the order of uplin# destination port numbers.

The ordinal number of a media component shall not be chan ed when the session description information is modified. &f no ":& with fi(ed and uniDue positions for media components is e(chan ed between 32 and .7- the 32 and .7 may assi n the ordinal numbers of the media components in another application@dependent al orithm which uarantees that 32 and .7 assi n the same ordinal number to each media component. &f 32 and .7 do not share an al orithm for a iven application- which uarantees that 32 and .7 assi n the same ordinal number to each media component- the ordinal number of the media component shall be set to !ero and the ordinal number of the &P flows shall be assi ned accordin to the followin rulesB ,. &f ordinal numbers for several &P flows are assi ned at the same time- all uplin# &P flows shall be assi ned lower ordinal number than all downlin# &P flows. *. &f ordinal numbers for several &P flows are assi ned at the same time- all uplin# and all downlin# &P flows shall separately be assi ned ordinal numbers accordin to increasin internet protocol number assi ned by &.'. (e. . ; for T1P and ,< for 3:P) 3. &f ordinal numbers for several &P flows are assi ned at the same time- for each internet protocol with a port concept- all uplin# and all downlin# &P flows of this internet protocol shall separately be assi ned ordinal numbers accordin to increasin port numbers. 8. &f &P flows are removed from an e(istin session- the previously assi ned bindin info shall remain unmodified for the remainin &P flows. 9. &f &P flows are added to an e(istin session- the previously assi ned bindin info shall remain unmodified and the new &P flows shall be assi ned ordinal numbers followin the rules ,. to 3.- startin with the first previously unused ordinal number. The numbers freed in step 8. shall not be reused. &f the &P flows correspond to .7 si nallin (e. . "&P si nallin &P 7lows)- and no &P flow information is provided both the ordinal number of the media component and the &P flows shall be set to !ero. &n the case when the &P flow information of the .7 si nallin is provided- the ordinal number of the media component will be set to !ero- and the ordinal number(s) of the &P flows shall follow the rules set above for the case when the 32 and .7 do not share an al orithm for a iven application.

3GPP

elease ##

(-

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

@.1.2 6(ri7a'ion o5 . o4 ;)(n'i5i(r* 5ro9 S6P


@.1.2.1 S'an)ar) Pro!()&r(

The procedure in Table 0.,.*.,., shall be applied for ":P of IsessionI disposition type within "&P and for all ":P outside "&P. Ta1le ='#'%'#'#4 Standard Procedure to derive 0low ;dentifiers from S3P
The ordinal num1er of the position of the media component Th( or)ina n&9-(r o5 'h( +o*i'ion o5 'h( H9JH in( in 'h( S6P The ordinal num1er of the ;P flow"s$ within the media component description Th( or)ina n&9-(r o5 'h( ;P 5 o4(*) 4i'hin 'h( D9JE in( a**ign() in 'h( or)(r o5 in!r(a*ing )o4n in< )(*'ina'ion +or' n&9-(r*, i5 )o4n in< )(*'ina'ion +or' n&9-(r* ar( a7ai a- (. .or &+ in< or ina!'i7( &ni!a*' 9()ia ;P 5 o4*, a )o4n in< )(*'ina'ion +or' n&9-(r i* n(7(r'h( (** a7ai a- (, i5 S6P o55(r-an*4(r a!!or)ing 'o %.C 32#4 i* &*(). Th( or)ina n&9-(r o5 'h( ;P 5 o4(*) 4i'hin 'h( D9JE in( a**ign() in 'h( or)(r o5 in!r(a*ing &+ in< )(*'ina'ion +or' n&9-(r*, i5 no )o4n in< )(*'ina'ion +or' n&9-(r* ar( a7ai a- (.

@.1.2.2

S6P 4i'h H(ar " *(**ionH )i*+o*i'ion '"+(

The procedure in Table 0.,.*.*., shall be applied for ":P of Iearly sessionI disposition type within "&P. The Iearly sessionI disposition type is specified within &2T7 /71 3>9> E*<F. Ta1le ='#'%'%'#4 Procedure to derive 0low ;dentifiers from >early session> disposition S3P
The ordinal num1er of the position of the media component The ordinal num1er of the ;P flow"s$ within the media component description ,* in 'a- ( @.1.2.1.1.

&f a sin le media component with one media type (e. . IaudioI or IvideoI) is contained in Iearly sessionI disposition ":P and a sin le media component with the same media type is contained in the IsessionI disposition ":P of the same "&P dialo ue- and if both ":P media components are described in a sin le /( service information media component- that /( service information media component shall obtain the media component number derived from IsessionI disposition ":P followin the rules in table 0.,.*.,.,. Otherwise each media component shall obtain the ordinal number of the position of the ImKI line in the Iearly sessionI disposition ":P plus ,+++ as media component ordinal number.

@.2

E2a9+ ( 1

.n 32- as the offerer- sends a ":P session description- as shown in table 0.*.,- to an application server (only relevant ":P parameters are shown)B Ta1le ='%'#4 The values of the S3P parameters sent 1y the 68 in e!ample #' ?K+ oKecsreid 3*;*8;8=;9 3*;*8;8=;= &' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. sKMM+, iKOne unidirectional audio media and one unidirectional video media and one bidirectional application

3GPP

elease ##

(.

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

media tK3*;*3<<;++ 3*;*=+>;++ mKvideo 9+*3+ /TPH.?P 3, cK&' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. aKrecvonly mKaudio 9+33+ /TPH.?P + cK&' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. aKsendonly mKapplication 9+83+ udp wb cK&' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. aKsendrecv

and receives the ":P parameters- as shown in table 0.*.*- from the application serverB Ta1le ='%'%4 The values of the S3P parameters sent 1y the application server in e!ample #' ?K+ oKecsreid 3*;*8;8=;9 3*;*8;8=;= &' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. sKMM+, iKOne unidirectional audio media and one unidirectional video media and one bidirectional application media tK3*;*3<<;++ 3*;*=+>;++ mKvideo 9,3<* /TPH.?P 3, cK&' &P; *++,B+;8;B+++.B+3.<B+*:+B9>77B728+B*+,8 aKsendonly mKaudio 8>,<+ /TPH.?P + cK&' &P; *++,B+;8;B+++.B+3.<B+*:+B9>77B728+B*+,8 aKrecvonly mKapplication 3*8,; udp wb cK&' &P; *++,B+;8;B+++.B+3.<B+*9+B:.77B72+2B1;7* aKsendrecv

7rom this offerWanswer e(chan e of ":P parameters the 32 and the P1/7 each creates a list of flow identifiers comprisin the &P flows as shown in table 0.*.3B Ta1le ='%'34 0low identifiers in e!ample #'
2rder of ?m@?,line 1 1 1 2 2 2 3 3 Type of ;P flows %TP (Vi)(o) 6L %TCP 6L %TCP UL %TP (,&)io) UL %TCP 6L %TCP UL U6P (a++ i!a'ion) 6L U6P (a++ i!a'ion) UL 3estination ;P address < Port num1er of the ;P flows 200100#4#000.10004$002600$9..0.E140.33, 3 $0230 200100#4#000.10004$002600$9..0.E140.33, 3 $0231 200100#4#0000,003,7002600$9..0.E4002014 3 $1373 200100#4#0000,003,7002600$9..0.E4002014 3 49170 200100#4#000.10004$002600$9..0.E140.33, 3 $0331 200100#4#0000,003,7002600$9..0.E4002014 3 49171 200100#4#000.10004$002600$9..0.E140.33, 3 $0430 200100#4#0000,003M7002$006,..0.E0E0C#.2 3 3241# 0low identifier K1,1L K1,2L K1,2L K2,1L K2,2L K2,2L K3,1L K3,1L

@.3

E2a9+ ( 2
mKUmediaV UportVHUnumber of portsV UtransportV Ufmt listV

&n the eneral case- multiple ports may be specified with a Inumber of portsI Dualifier as follows- /71 *3*< E,<FB

.n 32- as the offerer- sends a ":P session description- as shown in table 0.3.,- to an application server (only relevant ":P parameters are shown)B

3GPP

elease ##

(*

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

Ta1le ='3'#4 The values of the S3P parameters sent 1y the 68 in e!ample %' vK+ oKecsreid 3*;*8;83*, 3*;*8;83*9 &' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. sKMM+* iKOne unidirectional audio media consistin of two media &P flows described by one media component tK3*;*3<<;++ 3*;*=+>;++ mKaudio 9+33+H* /TPH.?P + cK&' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. aKrecvonly

and receives the ":P parameters- as shown in table 0.3.*- from the application serverB Ta1le ='3'%4 The values of the S3P parameters sent 1y the application server in e!ample %' vK+ oKecsreid 3*;*8;83*, 3*;*8;83*9 &' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. sKMM+* iKOne unidirectional audio media consistin of two media &P flows described by one media component tK3*;*3<<;++ 3*;*=+>;++ mKaudio 8>,<+H* /TPH.?P + cK&' &P; *++,B+;8;B+++.B+3.<B+*:+B9>77B728+B*+,8 aKsendonly

7rom this offerWanswer e(chan e of ":P parameters the 32 and the P1/7 each creates a list of flow identifiers comprisin the &P flows as shown in table 0.3.3B Ta1le ='3'34 0low identifiers in e!ample %'
2rder of ?m@?,line 1 1 1 1 1 1 Type of ;P flows %TP (a&)io) 6L %TCP 6L %TCP UL %TP (a&)io) 6L %TCP 6L %TCP UL 3estination ;P address < Port num1er of the ;P flows 200100#4#000.10004$002600$9..0.E140.33, 3 $0330 200100#4#000.10004$002600$9..0.E140.33, 3 $0331 200100#4#0000,003,7002600$9..0.E4002014 3 49171 200100#4#000.10004$002600$9..0.E140.33, 3 $0332 200100#4#000.10004$002600$9..0.E140.33, 3 $0333 200100#4#0000,003,7002600$9..0.E4002014 3 49173 0low identifier K1,1L K1,2L K1,2L K1,3L K1,4L K1,4L

@.4

E2a9+ ( 3 4i'ho&' 9()ia !o9+on(n'*.

The 32 and .7 do not e(chan e ":P for an application and do not share an al orithm- which uarantees that 32 and .7 assi n the same ordinal number to each media component. .t the .7 session initiation- the 32 and .7 a ree to set up the followin &P flowsB @ @ @ @ @ 3plin# 3:P flow with destination port ,++. :ownlin# 3:P flow with destination port ,++. :ownlin# T1P flow with destination port ,++. 3plin# T1P flow with destination port ,++. 3plin# 3:P flow with destination port *++.

3GPP

elease ##

(5

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

The followin bindin info is assi ned to these &P flows. @ @ @ @ @ 3plin# 3:P flow with destination port ,++B :ownlin# 3:P flow with destination port ,++B :ownlin# T1P flow with destination port ,++B 3plin# T1P flow with destination port ,++B 3plin# 3:P flow with destination port *++B (+- *) (+- 9) (+- 8) (+- ,) (+- 3)

.t a later sta e in the session- the T1P &P flows are removed and the followin &P flows are addedB @ @ 3plin# 3:P flow with destination port ,9+. :ownlin# 3:P flow with destination port 9+.

The followin bindin info is assi ned to the &P flows e(istin at this sta eB @ @ @ @ @ 3plin# 3:P flow with destination port ,++B :ownlin# 3:P flow with destination port ,++B 3plin# 3:P flow with destination port *++B 3plin# 3:P flow with destination port ,9+B :ownlin# 3:P flow with destination port 9+B (+- *) (+- 9) (+- 3) (+- ;) (+- <)

@.$

E2a9+ ( 4

&n this e(ample- the ":P PaKrtcpQ attribute defined in &2T7 /71 3;+9 is used. .n 32- as the offerer- sends a ":P session description- as shown in table 0.9.,- to an application server (only relevant ":P parameters are shown)B Ta1le ='-'#4 The values of the S3P parameters sent 1y the 68 in e!ample #' ?K+ oKecsreid 3*;*8;8=;9 3*;*8;8=;= &' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. sKMM+, iKOne unidirectional video media tK3*;*3<<;++ 3*;*=+>;++ mKvideo 9+*3+ /TPH.?P 3, cK&' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. aKrecvonly aKrtcpB 8>3*+

and receives the ":P parameters- as shown in table 0.9.*- from the application serverB Ta1le C'-'%4 The values of the S3P parameters sent 1y the application server in e!ample #' ?K+ oKecsreid 3*;*8;8=;9 3*;*8;8=;= &' &P; *++,B+;8;B++7,B++89B+*:+B9>77B72,8B733. sKMM+, iKOne unidirectional video media tK3*;*3<<;++ 3*;*=+>;++ mKvideo 9,3<* /TPH.?P 3, cK&' &P; *++,B+;8;B+++.B+3.<B+*:+B9>77B728+B*+,8 aKsendonly

3GPP

elease ##

(&

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

aKrtcpB93+*+

7rom this offerWanswer e(chan e of ":P parameters the 32 and the P1/7 each creates a list of flow identifiers comprisin the &P flows as shown in table 0.9.3B Ta1le ='-'34 0low identifiers in e!ample ('
2rder of ?m@?,line 1 1 1 Type of ;P flows %TP (Vi)(o) 6L %TCP 6L %TCP UL 3estination ;P address < Port num1er of the ;P flows 200100#4#000.10004$002600$9..0.E140.33, 3 $0230 200100#4#000.10004$002600$9..0.E140.33, 3 49320 200100#4#0000,003,7002600$9..0.E4002014 3 $3020 0low identifier K1,2L K1,1L K1,1L

,nn(2 C 0 Voi)

3GPP

elease ##

-+

3GPP TS %&'%#( )##'*'+ "%+#%,#%$

,nn(2 6 (in5or9a'i7()0 Chang( hi*'or"


3ate 113113200$ 173023200# 133093200# 1$3093200# 113113200# TSG A TSG 3oc' C ev Su1ject<Comment ;n! &)(* 'h( 5o o4ing T68C* agr(() a' CT3N3>0 C3-0$0#93, C3-0$0>37, C3-0$0>3>, C3-0$0>44, C3-0$0>4$ ;n! &)(* 'h( 5o o4ing T68C* agr(() a' CT3N390 C3-0#0101, C3-0#0102, C3-0#012$, C3-0#0112, C3-0#0133, C3-0#0114, C3-0#013#, C3-0#011# ;n! &)(* 'h( 5o o4ing T68C* agr(() a' CT3N410 C3-0#044#, C3-0#0447, C3-0#0$$#, C3-0#0$3>, C3-0#04$1, C3-C3-0#04$3, C3-0#0$40, C3-0#049#, C3-0#0$44 ;9+ (9(n'a'ion o5 C3-0#0$39 9i**ing in 5or9(r 7(r*ion an) !orr(!'ion o5 an ()i'oria (rror in C3-0#049# i9+ (9(n'a'ion. ;n! &)(* 'h( 5o o4ing T68C* agr(() a' CT3N420 C3-0#0#0$, C3-0#0#39, , C3-0#0#43, C3-0#0#$$, C3-0#07>0, C3-0#07>3, C3-0#07>4, C3-0#0>2#, C3-0#0>27, C3-0#0>$2, C3-0#0>$3 E)i'oria &+)a'( -" MCC 5or +r(*(n'a'ion 'o TSG CT 5or in5or9a'ion Th( 9i*i9+ (9(n'() *'" ( o5 ()i'orA* no'(* in ! a&*( 4.3.2 4a* !orr(!'() 'o nor9a -" MCC. ;n! &)(* 'h( 5o o4ing T68C* agr(() a' CT3N430 C3-0700#3, C3-0700>#, C3-07011>, C3-070139, C3-0701$1, C30701>9, C3-070217, C3-07021>, C3-070221, C3-07023#, C30702$4 E)i'oria &+)a'( -" MCC 5or +r(*(n'a'ion 'o TSG CT 5or a++ro7a %(5(r(n!(* 'o ann(2 @ in !ha+'(r $ 4(r( r(+ a!() -" Dann(2 '-)E -" %agnar I&* (n)( (CT3 Chair9an), a* agr(() -" CTN3$ MCC &+)a'( 'o 7(r*ion 7.0.0 a5'(r a++ro7a a' TSG CTN3$ 2 PC%. a**&r( (9(rg(n!" -(ar(r 5or (9(rg(n!" *(r7i!( 7 Signa ing Pa'h S'a'&* )('(!'() ,.-,++ i!a'ion ;)(n'i5i(r a' ,. *(**ion (7( 2 , ign9(n' o5 PC%. ,!<no4 ()g9(n' 'o ,. 2 ,))i'ion o5 . o4 i)(n'i5i(r ann(2 3 %o&'(ing o5 6ia9('(r !o99an)* - %2 1 Vario&* Minor Corr(!'ion* 2 Ian) ing o5 )i*a- () 5 o4* 5or 5or<ing 6ia9('(r a++ i!a'ion ;6 1 Th( in+&' 5or PCC )(!i*ion* 1 S(**ion @in)ing Error 2 S(r7i!( ;n5or9a'ion a!!(+'() -" PC%. TS C (an-U+ 1 8rigin-S'a'(-;) ,VP 9i**ing in ,, !o99an)* 2 C ari5i!a'ion o5 PC%. Pro!()&r(* 1 Corr(!'ion o5 i9+ (9(n'a'ion (rror o5 C%0013 $ Pro7i)ing U*(rO* ;P-C,/ T"+( an) *&-*!ri+'ion 5or ;P-C,/ T"+( !hang( no'i5i!a'ion 'o ,. 1 Pro7i*ioning o5 S(r7i!( ;n5or9a'ion a' P-CSC. 3 C ari5i!a'ion on ;MS Co99&ni!a'ion S(r7i!( ;)(n'i5i(r o7(r %2 %(9o7a o5 E9(rg(n!" S(r7i!(* 1 ,))ing 6(*'ina'ion-Io*' 'o ,,% 1 ,))ing 9i**ing ,VP* 'o %2 !o99an)* ,@/. 1 C ari5i!a'ion on /o'i5i!a'ion in %2 ;n'(r5a!( 3 ,VP an) Co99an) Co)( &+)a'(* 5or Co99on ;MS 1 S&++or'ing 'hir) +ar'" a++ i!a'ion *(r7(r 5or ,. 1 S&++or' o5 TCP--a*() 9()ia in PCC 3 ;P-C,/ T"+( 7(ri5i!a'ion 1 /o'i5i!a'ion o5 %( a*( o5 Signa ing @(ar(r 2 ;P C,/ *(**ion )(5ini'ion &+)a'( 2 %,T '"+( ,VP 3 P6/ in5or9a'ion in %2 in'(r5a!( U+)a'( o5 ;ET. r(5(r(n!(* 1 8&' o5 !r()i' in)i!a'ion, 8.. on " 1 U+)a'( %(5(r(n!( Mo)( /('4or<-on " -(ar(r !on'ro 9o)( S(r7i!( in5or9a'ion r(?&(*' 2ld 0.0.0 0.1.0 0.2.0 0.3.0 0.4.0 New 0.1.0 0.2.0 0.3.0 0.4.0 0.$.0

013123200# 1030132007 1$30232007 2>30232007 0930332007 03-2007 0#-2007 0#-2007 0#-2007 0#-2007 0#-2007 0#-2007 0#-2007 0#-2007 0#-2007 09-2007 09-2007 09-2007 09-2007 09-2007 09-2007 09-2007 12-2007 12-2007 12-2007 12-2007 12-2007 03-200> 03-200> 0$-200> 0$-200> 0$-200> 0$-200> 0$-200> 0$-200> 0$-200> 09-200> 12-200> 12-200> 12-200> 12-200> 12-200>

TSGN33 TSGN33

CP-0#0#37

0.$.0 1.0.0 1.0.1

1.0.0 1.0.1 1.1.0

TSGN3$ TSGN3$

CP-070099

1.1.0 2.0.0 2.1.0 7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.0.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.2.0 7.2.0 7.2.0 7.2.0 7.2.0 7.3.0 7.4.0 >.0.0 >.0.0 >.0.0 >.0.0 >.0.0 >.0.0 >.0.0 >.1.0 >.2.0 >.2.0 >.2.0 >.2.0 >.2.0

2.0.0 2.1.0 7.0.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.1.0 7.2.0 7.2.0 7.2.0 7.2.0 7.2.0 7.2.0 7.2.0 7.3.0 7.3.0 7.3.0 7.3.0 7.3.0 7.4.0 >.0.0 >.1.0 >.1.0 >.1.0 >.1.0 >.1.0 >.1.0 >.1.0 >.2.0 >.3.0 >.3.0 >.3.0 >.3.0 >.3.0

TSGN3# TSGN3# TSGN3# TSGN3# TSGN3# TSGN3# TSGN3# TSGN3# TSGN3# TSGN37 TSGN37 TSGN37 TSGN37 TSGN37 TSGN37 TSGN37 TSGN3> TSGN3> TSGN3> TSGN3> TSGN3> TSGN39 TSGN39 TSGN40 TSGN40 TSGN40 TSGN40 TSGN40 TSGN40 TSGN40 TSGN41 TSGN42 TSGN42 TSGN42 TSGN42 TSGN42

CP-070423 CP-070423 CP-070423 CP-070423 CP-070423 CP-070494 CP-070423 CP-070423 CP-070423 CP-070$$> CP-070$$> CP-070$$9 CP-070$$> CP-070$$> CP-070$$> CP-070$$> CP-07072> CP-07072> CP-07072> CP-07072> CP-07072> CP-0>0040 CP-0>004# CP-0>029> CP-0>029# CP-0>0292 CP-0>0299 CP-0>0292 CP-0>0299 CP-0>0299 CP-0>04>7 CP-0>07$1 CP-0>07#> CP-0>07#0 CP-0>07$1 CP-0>07$1

001 002 003 00$ 007 00> 013 017 020 022 023 02$ 02# 02> 030 033 032 037 03> 039 041 042 044 04> 049 0$1 0$2 0$4 0$$ 0$7 0#> 072 07# 0>1 0>$ 0>7

3GPP

elease ##
12-200> 03-2009 03-2009 03-2009 03-2009 0$-2009 0$-2009 0$-2009 0$-2009 0$-2009 0$-2009 09-2009 12-2009 12-2009 12-2009 12-2009 12-2009 12-2009 03-2010 03-2010 03-2010 03-2010 03-2010 09-2010 09-2010 09-2010 12-2010 12-2010 12-2010 03-2011 03-2011 03-2011 03-2011 03-2011 03-2011 03-2011 03-2011 03-2011 03-2011 0#-2011 0#-2011 0#-2011 0#-2011 0#-2011 0#-2011 0#-2011 09-2011 09-2011 12-2011 12-2011 12-2011 03-2012 03-2012 03-2012 0#-2012 0#-2012 0#-2012 09-2012 09-2012 09-2012 09-2012 09-2012 12-2012 12-2012 12-2012 12-2012 TSGN42 TSGN43 TSGN43 TSGN43 TSGN43 TSGN44 TSGN44 TSGN44 TSGN44 TSGN44 TSGN44 TSGN4$ TSGN4# TSGN4# TSGN4# TSGN4# TSGN4# TSGN4# TSGN47 TSGN47 TSGN47 TSGN47 TSGN47 TSGN49 TSGN49 TSGN49 TSGN$0 TSGN$0 TSGN$0 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$1 TSGN$2 TSGN$2 TSGN$2 TSGN$2 TSGN$2 TSGN$2 TSGN$2 TSGN$3 TSGN$3 TSGN$4 TSGN$4 TSGN$4 TSGN$$ TSGN$$ TSGN$$ TSGN$# TSGN$# TSGN$# TSGN$7 TSGN$7 TSGN$7 TSGN$7 TSGN$7 TSGN$> TSGN$> TSGN$> TSGN$> CP-0>0923 CP-090074 CP-0900>2 CP-09009# CP-09009# CP-090339 CP-09034# CP-090339 CP-090334 CP-090339 CP-0903$3 CP-090$73 CP-090>42 CP-090>$7 CP-090>3> CP-090>42 CP-090>$7 CP-090>3> CP-100070 CP-10007# CP-1000># CP-100070 CP-10007# CP-100#2# CP-100$#1 CP-100791 CP-100771 CP-100791 CP-11012$ CP-11012$ CP-11012$ CP-110114 CP-11012$ CP-11012$ CP-110121 CP-11012$ CP-11012$ CP-110133 CP-11040$ CP-110413 CP-110409 CP-110411 CP-110413 CP-11042$ CP-110424 CP-110#0> CP-110#0> CP-11093$ CP-110>27 CP-110>3$ CP-120077 CP-1200## CP-120077 CP-1203$4 CP-12034$ CP-1203$> CP-120$11 CP-120#4# CP-120$14 CP-120$3# CP-120#$$ CP-120>43 CP-120>24 CP-120>43 CP-12091# 0>> 091 093 09$ 09# 09> 100 101 103 104 099 112 11# 117 120 122 127 130 137 139 140 143 14$ 147 14> 1$0 1$3 1$4 1$9 1#1 1#2 1#$ 1#7 1#> 171 172 173 170 1>0 1>2 1 1 1 2 2 3 1 1 2 3 1 2 3 2 1 3 4 1 1 2 3 1 2 1 2 3 1 2 3 4 2 1 1 $ 1 2 1 1

-#

3GPP TS %&'%#( )##'*'+ "%+#%,#%$


>.2.0 >.3.0 >.3.0 >.3.0 >.3.0 >.4.0 >.4.0 >.4.0 >.4.0 >.4.0 >.$.0 9.0.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.1.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.3.0 9.4.0 10.0.0 10.0.1 10.0.1 10.0.1 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.1.0 10.2.0 11.0.0 11.0.0 11.0.0 11.0.0 11.0.0 11.0.0 11.0.0 11.1.0 11.1.0 11.2.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.4.0 11.4.0 11.4.0 11.$.0 11.$.0 11.$.0 11.$.0 11.$.0 11.#.0 11.#.0 11.#.0 11.#.0 >.3.0 >.4.0 >.4.0 >.4.0 >.4.0 >.$.0 >.$.0 >.$.0 >.$.0 >.$.0 9.0.0 9.1.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.2.0 9.3.0 9.3.0 9.3.0 9.3.0 9.3.0 9.4.0 10.0.0 10.0.1 10.1.0 10.1.0 10.1.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 10.2.0 11.0.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0 11.1.0 11.2.0 11.2.0 11.3.0 11.3.0 11.3.0 11.4.0 11.4.0 11.4.0 11.$.0 11.$.0 11.$.0 11.#.0 11.#.0 11.#.0 11.#.0 11.#.0 11.7.0 11.7.0 11.7.0 11.7.0

1>$ 2 1>7 1>9 1 190 1 191 19$ 199 204 20> 210 212 214 21$ 223 224 22> 233 23> 242 24$ 24# 247 2$1 2$3 2$$ 2 2

1 1 1 2 2 1 1 1 2 2 1 2 1 1 4

S&++or' o5 T;,S +ara9('(r E2+(ri9(n'a -%(*& ' ,VP &*ag( on %2 ,))ing S&++or'()-.(a'&r(* ,VP 'o %2 !o99an)* %2 6ia9('(r S(**ion* ;MS *(**ion *('&+ 4i'h UE ini'ia'() r(*o&r!( r(*(r7a'ion %(*o&r!( a o!a'ion *&-*!ri+'ion in %2 ;CS i9+a!' on PCC Corr(!'ion 'o 5(a'&r( -i' )(5ini'ion 6( ('ing ;/6;C,T;8/P8.PL8SSP8.P@E,%E% E7(n' Li9i'() PCC 6(+ o"9(n' Pr(7(n'ing 'h( &*( o5 an E9(rg(n!" ,P/ 5or /on-(9(rg(n!" !a * Li9i'() PCC )(+ o"9(n' ,!!(** /('4or< Charging ;)(n'i5i(r han) ing in %2 PCC han) ing o5 S6P o5 (ar " *(**ion )i*+o*i'ion '"+( U*( o5 ;P7# Pr(5i2 Corr(!'ion* 5or PCC3QoS r& ( 9o)i5i!a'ion 5ai &r( S&++or'() .(a'&r(* 5or %( -9 %2 %2 r(?&(*' han) ing Corr(!'ing 'h( r(5(r(n!( o5 ,nn(2 $ Corr(!'ion o5 . o4-6(*!ri+'ion ,VP )(*!ri+'ion ;MS %(*'ora'ion +ro!()&r( o7(r %2 /o'i5i!a'ion a-o&' %,T-'"+( !hang( S&++or'()-.(a'&r( 5(a'&r( -i' )(5ini'ion* 3GPP %(5(r(n!(* 'o T;SP,/ *+(!i5i!a'ion* ;9+a!'* o5 ;.8M on %2 in'(r5a!( E)i'oria !orr(!'ion -" MCC ,))i'ion* 'o *&++or' *+on*or() !onn(!'i7i'" S+(!i5i!-,!'ion ,VP 'o r(+or' *+(!i5i! a!'ion* U6% an) U) in PCC ,r!hi'(!'&r( ,&'hori:a'ion o5 'h( *+on*or() )a'a !onn(!'i7i'" ,SP o+(ra'or* in5or9a'ion 5or *+on*or() )a'a !onn(!'i7i'" U*ag( 5or *+on*or() !onn(!'i7i'" .i2ing S&++or'()-.(a'&r( 5(a'&r( -i' )(5ini'ion* Corr(!'ion 'o 5(a'&r( -i' 5or *+on*or() )a'a !onn(!'i7i'" Corr(!'ion 'o 'h( %(+or'ing U*ag( 5or S+on*or() 6a'a Conn(!'i7i'" S&++or' o5 MPS o7(r %2 So9( ()i'oria !orr(!'ion* 5or *+on*or() )a'a !onn(!'i7i'" %(?&(*'ing U*ag( Moni'oring Con'ro 5or *+on*or() !onn(!'i7i'" S) r(5(r(n!( +oin' in PCC ,r!hi'(!'&r( PS-'o-CS I8 in)i!a'or in %2 S+on*or-;)(n'i'" ,VP Q ,++ i!a'ion-S(r7i!(-Pro7i)(r-;)(n'i'" ,VP 5or9a'. So9( !orr(!'ion* 5or ;.8M S&++or'()-.(a'&r(* -i' 5or (MPS Li9i' 'h( *+on*or() )a'a !onn(!'i7i'" in 'h( roa9ing !a*( S&-*!ri-(r S+(n)ing Li9i'* -a*() on S" r(5(r(n!( +oin' (%11 29.214) %(?&(*' T"+( in %2 ,,% UE ;P7# +r(5i2 a o!a'ion ! (an-&+ Corr(!'ion 'o 'h( ar!hi'(!'&r( 5ig&r((%( -11) , ign9(n' o5 PCC r(5(r(n!( ar!hi'(!'&r( 4i'h S'ag( 2 *+(!i5i!a'ion Corr(!'ion in ,VP na9(* . o4* ,VP in ,,, !o99an) M& 'i+ ( in*'an!(* o5 'h( S&-*!ri+'ion ;) (%11 29.214) QoS *&++or' 5or 3GP-6,SI S(r7i!(* ,**(r'() ;CS; o7(r %2 S&++or' n('4or< o!a'ion r(+or'ing 5or ;MS 5&n!'iona i'" o7(r %2 in'(r5a!( (%11 29214) S&++or' 5or o!a a))r(** in T.T 5i '(r* ,VP (TS 29.214) Corr(!'ion 'o 'h( r(5(r(n!( o5 TS 29.214 (%11) Corr(!'ion o5 a**ign() in'(rn(' +ro'o!o n&9-(r ,))i'ion o5 PLM/ ;6 5or /ETL8C in TS 29.214 ,++ i!a- ( ;P-C,/ T"+( %(+or'ing 9& 'i+ ( (7(n'* 'o ,. %(5(r(n!( i*' !orr(!'ion 'o a ign 4i'h 'h( !orr(!'() TS 29.212 'i' ( C ari5i!a'ion o5 S&++or'()-.(a'&r(* ,VP PCC +ro!()&r(* 5or %2 *(**ion* 4i'h no *(r7i!( in5or9a'ion C (an &+ o5 E)i'orA* /o'(* Corr(!'ion o5 %2 r(5(r(n!( +oin' 5or PC%. a))r(**ing

3GPP