UPCC V300R006C10 Gx Interface Specification

Doc. Code

UPCC V300R006C10

Gx Interface Specification

Issue

1.42

Date

201432!

"U#$%I &%C"'()(GI%S C(.* )&D.

Cop+ri,-t  "ua/ei &ec-noo,ies Co.* )td. 2014. # ri,-ts resered. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

&radears and Perissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

'otice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. nless otherwise specified in the contract, all statements, information, and recommendations in this document are provided !A" #"! without warranties, guarantees or representations of any kind, either e$press or implied. The information in this document is sub%ect to change without notice. &very effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, e$press or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 5181! "eo#le$s %e#u&lic o' China

(e&site:

htt#:))www.huawei.co*

+*ail:

su##orthuawei.co*

#ssue '.() *)+'(-)/

Huawei 0roprietary and Confidential Copyright 1 Huawei Technologies Co., Ltd

i

%e-ision %ecord Date

Revision Version

Change Description

/080

1.

Initial

!0!0

1.1

Add the 20H(03onitoring04e 'or usage

!0110/

1.

collection into rule de'inition. 1. Add the 67"" %8 %e-alidation0Ti*e related A" . Add #ri-ate "roto0Classi'ier09a*e A" to Charging0%ule0e'inition to su##ort dna*ic rule o' Laer/. 10;0!

1.6

1. Add the 67"" %!
1080;

1.

1.Add the %AT0T#eA" in the CC% *essage and the de'ination 'or this A". .Add the e'ault0+"S0Bearer0=oS A" in the CCA)%A% and the de'ination 'or e'ault0+"S0 Bearer0=oS, "re0e*#tion0Ca#a&ilit and "re0 e*#tion0ulnera&ilit. 6.Add the A"90Aggregate03a>0Bitrate0L and A"90Aggregate03a>0Bitrate0
#ssue '.() *)+'(-)/


ii

Date

Revision Version

Change Description Charging0%ule0e'inition A". Add the de'ination 'or 20H(0Su&scri&er0Ser-ice0e'inition, 20H(0Su&scri&er0Ser-ice09a*e, 20H(0Su&scri&er0Ser-ice0
1010

1.5

@iangguilan0

1.Add +-ent0Trigger@s: 2&"32C&4536#7#CAT#3N42&8&"T *)-/

oLT+

CHA29#N94C322&LAT#3N4&:CHAN9& *);/

.Add the A"@s: ?low0In'or*ation A" "acet0?ilter0Content A" "acet0?ilter0Identi'ier A" "acet0?ilter0In'or*ation A" "acet0?ilter0D#eration A" Charging0Correlation0Indicator A" 1010

1.;

AddtheA"@s:

@iangguilan0

ser&
1010 @wangEing

1./

1.Add +-ent0Trigger@s: <+FTI3+FGD9+FCHA97+ @5 TAIFCHA97+ @5 +C7IFCHA97+ @5 .3odi' the A"@s: =oS09egotiation =oS0<#grade 67""0
CCTime . 3odi' 7> 3essage: 110!0/ @wanguhui

1.8

Credit0Control0%eEuest @CC% 1. Add+-ent0Trigger: A""LICATID9FSTA%T@6! A""LICATID9FSTD"@ . Add A": A##lication0etection0In'or*ation A" T?0A##lication0Identi'ier A"

#ssue '.() *)+'(-)/


iii

Date

Revision Version

Change Description

110!01

1.!

1. Add+-ent0Trigger:

@ang*ing

C+LLFCD97+ST+@16 C+LLF CL+A%@1 . Add A": 20H(0Cell0Congestion0Le-el A"

110!01

1.1

@wangEing 110!01

1. Add 20H(0Session0%estoration A" . 3odi' Charging0%ule0e'inition A"

1.11

@liu>ianghui

AddA": 1. 7>0T3D0%edirect0Ser-er A" . 7>0T3D0%edirect0Address0T#e 6. 7>0T3D0%edirect0Ser-er0Address . 7>0T3D0A##end0Driginal0<%L 5. 7>0T3D0eacti-ate0B0%edirect ;. 7>0T3D0A##end03SIS9 /. 7>0T3D0A##end0I3SI 8. 7>0T3D0A##end0I3+I !. 7>0T3D0A##end03SI"

110!06

1.1

@>uezhen

11011011

1.16

AddA": 1.

20H(0
. 6.

20H(0Ser-ice0T#e 20H(03S07rou#09a*e

.

20H(0ACL07rou#09a*e

5.

20H(0Interi*0Inter-al

;.

I"0CA90T#e

1. elete+-ent0Trigger: A""LICATID9FSTA%T@6! A""LICATID9FSTD"@ . elete A": A##lication0etection0In'or*ation A" T?0A##lication0Identi'ier A"

1101106

1.1

@ang*ing

AddA": 1. ?low0irection . "acet0?ilter0
1001/ @ang*ing

1.15

Baseline 'or <"CC 6%5C1

106011

1.1;

Baseline 'or <"CC 6%5C1 'ro* "CC

@u&in)6!;/ 10601/ @wangEing5!!

#ssue '.() *)+'(-)/

6%5C1 1.1;

AddA" ： 1.

20H(0Content0?ilter

.

20H(0Content0?ilter0In'or*ation


iv

Date

Revision Version

1060/

1.1/

（shi>ian

Change Description 6.

20H(0Content0?ilter0Categor0Basena*e

1.

Add+-ent0Trigger ：TetheringF%e#ort@11

.

Add A" ：20H(0Tethering0Status

111/61） 10018

1.18

@wanglin 6!1

Add e-ent trigger: S
1050;

1.1!

（>u&in 688）

108015

1.

@wanglin 6!1 10!01

1.

Add A": 20H(0 %edirect0Ti*es

.

Add A": 20H(0%edirect0%e#ort

6.

Add +-ent0Trigger: %edirection@1

AddA": %esource0Allocation09oti'ication

1.1

@iangzhihua

Baseline 'or <"CC 6%5C1 'ro* "CC 6%5C1

5818! 160108

1.

@iangzhihua

Baseline 'or <"CC 6%5C15 'ro* "CC 6%5C16

5818! 160108 @liuhongan

1.

168/;1

1.

Adde-ent trigger: ACC+SSF9+T(D%4FI9?DF%+"D%T @5

.

Add %eEuired0Access0In'o A" included in Charging0%ule0e'inition A".

16010!

1.6

1.

@iangguilan

Add 20H(0alidit0Ti*e A" included in Charging0%ule0Install A". Add A" ：

;/!

.

16060

20H(0alidit0Ti*e, 20H(0Acti-ation0Ti*e, 20H(0eacti-ation0Ti*e, 20H(0Acti-ation0a, 20H(0eacti-ation0a, 20H(0Acti-it0Ti*er AddA":

1.

@ianzhihua 5818!

S90Ser-ice0?low0etection Add Trigger: S+%IC+F?LD(F+T+CTID9 @1

16060 @iangguilan ;/!

1.5

According to TS1661//: 1. Add +-ent0Trigger: A""LICATID9FSTA%T@6! . Add A": A##lication0etection0In'or*ation

#ssue '.() *)+'(-)/


v

Date

Revision Version

Change Description T?0A##lication0Identi'ier AC0%ule0Install AC0%ule0%e*o-e AC0%ule09a*e AC0%ule0%e#ort

1600!

1.;

elete the ?ollowA": 1.

20H(0alidit0Ti*e A" included in Charging0%ule0Install A".

. 20H(0alidit0Ti*e, 20H(0Acti-ation0Ti*e, 20H(0eacti-ation0Ti*e, 20H(0Acti-ation0a, 20H(0eacti-ation0a, 20H(0Acti-it0Ti*er

16050

1./

According to TS16565! : 1.

Add A": A?0Signalling0"rotocol, +-ent0%e#ort0Indication A"

.

Add A?0Signalling0"rotocol A" included in Charging0%ule0e'inition A".

6.

Add +-ent0%e#ort0Indication A" included in %e0Auth0%eEuest @%A%

16050!

1.8

160;0

1.!

Baseline 'or <"CC 6%5C1; 'ro* <"CC 6%5C15 3odi'A": CC0In#ut0Dctets CC0Dut#ut0Dctets

160;0;

1.6

AddTrigger A"90A3B%F3DI?ICATID9F?AIL<%+ @! +?A
160/0;

1.61

Baseline 'or <"CC 6%;C1 'ro* <"CC 6%5C1; and 6%;C

160!0

1.6

16010

1.66

16010!

1.6

Add 6 A" 'or su&scri&er #ro'ile 'ucntion:  20Header0+nrich*ent 

20Header0+nrich*ent0I



20Header0+nrich*ent0ata

Add "riorit0Le-el A" under Allocation0 %etention0"riorit A"

#ssue '.() *)+'(-)/

Baseline 'or <"CC 6%;C 'ro* <"CC Huawei 0roprietary and Confidential Copyright 1 Huawei Technologies Co., Ltd

vi

Date

Revision Version

16010

1.65

Change Description 6%;C1 AddTrigger: 

D


%+ALLDCATID9FD?FC%+IT @1;

Add A":

16010

1.6;

160101

1.6/

160106

1.68



?inal0


?inal0


%estriction0?ilter0%ule



?ilter0Id



%edirect0Ser-er



%edirect0Address0T#e



%edirect0Ser-er0Address

AddA": 

CT0+>tension



Su&net0Identi'ier

Snchronize changes 'ro* 6%;C1 &etween 16)1)! and 16)1)1 Baseline 'or <"CC 6%;C1 'ro* "CC 6%;C

160106 10108

1.6! 1.

Add %edirect0Host A" in CCA *essage. Add T?0In'or*ation A" in CC% *essage.

106016

1.1

AddTrigger:

10606

1.

Add %ule0?ailure0Code A" introduction.

105016

1.6

Add

S


T?0A##lication0Identi'ier A"



%edirect0In'or*ation A"



3ute09oti'ication A"

within Charging0%ule0e'inition A". Add 

?low0In'or*ation A"

within A##lication0etection0In'or*ation A". Add 

A""LICATID9FSTD" @

within +-ent0Trigger A".

#ssue '.() *)+'(-)/


vii

0CC 9$ #nterface "pecification

Catalog

Catalog 1 Reference............................................................................................................................ ......... 1-1 2 Introduction and scope.................................................................................................. ........... 2-1 3 Terminology................................................................................................................................3-1  !rotocol "vervie#......................................................................................................................-1 (.' 6iameter.........................................................................................................................................................(' (.) 6iameter >ase 0rotocol..................................................................................................................................() (.- 9$ Application................................................................................................................................................() (.( #nterface Authentication mechanism..............................................................................................................()

$ Transport......................................................................................................................................$-1 % Constraints...................................................................................................................................%-1 ?.' >earer Control 5ode......................................................................................................................................?' ?.) 8o" negotiation..............................................................................................................................................?' ?.- Limitations......................................................................................................................................................?'

& 'essages......................................................................................................................................&-1 .' 5essage 7ormat..............................................................................................................................................' .) >ase 5essages................................................................................................................................................' .).' Capabilities&$change2e
#ssue '.() *)+'(-)/


viii


Catalog

( !rocedures.......................................................................................................................... ......... (-1 B.' Capability Negotiation for -900 2 9$ Application.....................................................................................B' B.) #0CAN "ession &stablishment......................................................................................................................BB.- & "ide #nitiated #0CAN >earer 5odification............................................................................................B( B.( & "ide #nitiated #0CAN "ession Termination............................................................................................B@ B.@ 0C27 #nitiated #0CAN "ession 5odification...............................................................................................B? B.? 0C27 #nitiated #0CAN "ession Termination................................................................................................B B. sage 2eport..................................................................................................................................................BB B.B Audit.............................................................................................................................................................B'+

) *V!s Definition.........................................................................................................................)-1 ;.' "ession#d.......................................................................................................................................................;' ;.) AuthApplication#d.......................................................................................................................................;' ;.- =endor#d........................................................................................................................................................;' ;.( 0roductName.................................................................................................................................................;) ;.@ "upported=endor#d......................................................................................................................................;) ;.? 7irmware2evision.........................................................................................................................................;) ;. =endor"pecificApplication#d.....................................................................................................................;) ;.B 3riginHost.....................................................................................................................................................;;.; 3rigin2ealm..................................................................................................................................................;;.'+ 6estinationHost...........................................................................................................................................;;.'' 6estination2ealm........................................................................................................................................;;.') TerminationCause........................................................................................................................................;( ;.'- 6isconnectCause.........................................................................................................................................;( ;.'( 3rigin"tate#d..............................................................................................................................................;@ ;.'@ 2esultCode..................................................................................................................................................;@ ;.'? &$perimental2esult.....................................................................................................................................;@ ;.' &rror5essage..............................................................................................................................................;? ;.'B 7ailedA=0...................................................................................................................................................;? ;.'; 2eAuth2e

i$


Catalog

;.-) -900"9"N5CC5NC.............................................................................................................................;; ;.-- -900serLocation#nfo..........................................................................................................................;'+ ;.-( 2A#.............................................................................................................................................................;'+ ;.-@ Access NetworkChargingAddress............................................................................................................;'' ;.-? Access NetworkCharging#dentifier=alue...............................................................................................;'' ;.- A7Charging#dentifier...............................................................................................................................;'' ;.-B 7low6escription........................................................................................................................................;'' ;.-; 7lows..........................................................................................................................................................;') ;.(+ 7low"tatus.................................................................................................................................................;') ;.(' 5a$2eandwidthL.................................................................................................................;') ;.() 5a$2eandwidth6L.................................................................................................................;') ;.(- Charging#nformation.................................................................................................................................;';.(( AccessNetworkCharging#dentifier9$...................................................................................................;';.(@ >earerControl5ode.................................................................................................................................;'( ;.(? >earer#dentifier.........................................................................................................................................;'( ;.( >earer3peration........................................................................................................................................;'( ;.(B >earersage..............................................................................................................................................;'@ ;.(; Charging2ule#nstall.................................................................................................................................;'@ ;.@+ Charging2ule2emove..............................................................................................................................;'? ;.@' Charging2ule6efinition...........................................................................................................................;'? ;.@) Charging2ule>aseName........................................................................................................................;'B ;.@- Charging2uleName..................................................................................................................................;'B ;.@( Charging2ule2eport................................................................................................................................;'B ;.@@ &ventTrigger..............................................................................................................................................;'; ;.@? #0CANType..............................................................................................................................................;)@ ;.@?.) 9uaranteed>itrate6L......................................................................................................................;)@ ;.@?.- 9uaranteed>itrateL......................................................................................................................;)? ;.@?.( 5etering5ethod..............................................................................................................................;)? ;.@ Network2e

$


Catalog

;.?; :H"essionsage.................................................................................................................................;-;.+ :H"ervicesage.................................................................................................................................;-;.' CC#nput3ctets.........................................................................................................................................;-;.) CC3utput3ctets.......................................................................................................................................;-( ;.- 2edirect"erver...........................................................................................................................................;-( ;.( 2edirectAddressType...............................................................................................................................;-( ;.@ 2edirect"erverAddress............................................................................................................................;-@ ;.? Append3riginal2L................................................................................................................................;-@ ;. 6eactivate>y2edirect..............................................................................................................................;-@ ;.B :H5onitoringey..............................................................................................................................;-@ ;.; 0rotoClassifierName................................................................................................................................;-? ;.B+ sage5onitoring#nformation..................................................................................................................;-? ;.B' sage5onitoringLevel............................................................................................................................;- ;.B) sage5onitoring2eport..........................................................................................................................;- ;.B- sage5onitoring"upport.........................................................................................................................;- ;.B( 5onitoringey..........................................................................................................................................;-B ;.B@ CCTotal3ctets..........................................................................................................................................;-B ;.B? 9ranted"ervicenit.................................................................................................................................;-B ;.B sed"ervicenit......................................................................................................................................;-; ;.BB 2evalidationTime......................................................................................................................................;-; ;.B; "ession2eleaseCause...............................................................................................................................;-; ;.;+ 2ATType....................................................................................................................................................;(+ ;.;' 6efault&0">earer8o"............................................................................................................................;(' ;.;) Allocation2etention0riority A=0.............................................................................................................;(' ;.;- 0riorityLevel A=0 *All access types/........................................................................................................;(' ;.;( 0reemptionCapability..............................................................................................................................;() ;.;@ 0reemption=ulnerability..........................................................................................................................;() ;.;? A0NAggregate5a$>itrate6L...............................................................................................................;() ;.; A0NAggregate5a$>itrateL...............................................................................................................;() ;.;B AN9Address A=0................................................................................................................................;(;.;; "upported7eatures A=0.............................................................................................................................;(;.'++ 7eatureList#6 A=0.................................................................................................................................;(;.'+' 7eatureList A=0......................................................................................................................................;(;.'+) 2uleActivationTime...............................................................................................................................;(( ;.'+- 2ule6eactivationTime...........................................................................................................................;(( ;.'+( :H"ubscriber"ervice6efinition......................................................................................................;(( ;.'+@ :H"ubscriber"erviceName.............................................................................................................;(@ ;.'+? :H"ubscriber"ervicesername......................................................................................................;(@ ;.'+ :H"ubscriber"ervice0assword.......................................................................................................;(@ ;.'+B 7low#nformation *All access types/.......................................................................................................;(@ ;.'+; 0acket7ilterContent................................................................................................................................;(? ;.''+ 0acket7ilter#dentifier.............................................................................................................................;(? #ssue '.() *)+'(-)/


$i


Catalog

;.''' 0acket7ilter#nformation.........................................................................................................................;( ;.'') 0acket7ilter3peration............................................................................................................................;( ;.''- ChargingCorrelation#ndicator *All access types/..................................................................................;(B ;.''( -9005"TimeDone................................................................................................................................;(B ;.''@ CCTime...................................................................................................................................................;(B ;.''? ser&y2edirect............................................................................................................;@' ;.')? 9$T53Append5"#"6N.....................................................................................................................;@' ;.') 9$T53Append#5"#...........................................................................................................................;@) ;.')B 9$T53Append#5&#...........................................................................................................................;@) ;.'); 9$T53Append5"#0..........................................................................................................................;@) ;.'-+ :H5"9roupName..........................................................................................................................;@;.'-' :HACL9roupName........................................................................................................................;@;.'-) :H#nterim#nterval.............................................................................................................................;@;.'-- :H"erviceType.................................................................................................................................;@;.'-( :Hser0hysical#nfo=alue.............................................................................................................;@( ;.'-@ 7low6irection.........................................................................................................................................;@( ;.'-? 0acket7iltersage..................................................................................................................................;@( ;.'- :HContent7ilter...............................................................................................................................;@( ;.'-B :HContent7ilter#nformation...........................................................................................................;@@ ;.'-; :HContent7ilterCategory>asename..............................................................................................;@@ ;.'(+ :HTethering"tatus............................................................................................................................;@? ;.'(' :H2edirectTimes.............................................................................................................................;@? ;.'() :H2edirect2eport............................................................................................................................;@? ;.'(- -900)>"#6............................................................................................................................................;@ ;.'(( 2esourceAllocationNotification............................................................................................................;@ ;.'(@ "N"ervice7low6etection.....................................................................................................................;@ ;.'(? 2e

$ii


Catalog

;.'@- 2edirect"erverAddress..........................................................................................................................;?+ ;.'@( A6C2ule#nstall......................................................................................................................................;?+ ;.'@@ A6C2ule2emove..................................................................................................................................;?+ ;.'@? A6C2uleName......................................................................................................................................;?' ;.'@ A6C2ule2eport.....................................................................................................................................;?' ;.'@B A7"ignalling0rotocol.............................................................................................................................;?' ;.'@; &vent2eport#ndication *All access types/.............................................................................................;?) ;.'?+ :Header&nrichment..............................................................................................................................;?) ;.'?' :Header&nrichment#6.........................................................................................................................;?;.'?) :Header&nrichment6ata......................................................................................................................;?;.'?- 7inalnit#ndication A=0........................................................................................................................;?;.'?( 7inalnitAction A=0.............................................................................................................................;?( ;.'?@ 2estriction7ilter2ule A=0......................................................................................................................;?( ;.'?? 7ilter#d A=0.............................................................................................................................................;?( ;.'? 2edirect"erver A=0.................................................................................................................................;?@ ;.'?B 2edirectAddressType A=0.....................................................................................................................;?@ ;.'?; 2edirect"erverAddress A=0..................................................................................................................;?@ ;.'+ CT&$tension............................................................................................................................................;?@ ;.'' "ubnet#dentifier.......................................................................................................................................;?? ;.') 8o"9roup2ule#nstall...........................................................................................................................;?? ;.'- 8o"9roup2ule2emove........................................................................................................................;? ;.'( 8o"9roup2ule6efinition.....................................................................................................................;? ;.'@ 8o"9roup2uleName............................................................................................................................;? ;.'? 2edirectHost............................................................................................................................................;? ;.' T67#nformation A=0..............................................................................................................................;?B ;.'B T676estinationHost A=0......................................................................................................................;?B ;.'; T67#0Address A=0...............................................................................................................................;?B ;.'B+ 2ule7ailureCode A=0 *All access types/...............................................................................................;?B

#ssue '.() *)+'(-)/


$iii


Catalog

+ist of a,,reviations (C3A

(ideCodei-ision3ulti#le>Access

7"%S

7eneral"acet%adioSer-ice

"CC

"olicandChargingControl

?BC

?lowedBasedCharging

SBL"

Ser-iceBasedLocal"olic

77S9

7atewa7"%SSu##ort9ode

S7S9

Ser-ing7"%SSu##ort9ode

"C%?

"olicandCharging%ule?unction

"C+?

"olicandCharging+n'orce*ent?unction

DCS

DnlineChargingSste*

D?CS

D''lineChargingSste*

A?

A##lication ?unction

S"%

Su&sci&er"ro'ile%e#ositor

I"9

Intelligent"acet9etwor

BC3

BearerControl3ode

9%S"CA

9etwor %eEuested Secondar "" Conte>tActi-ation

S?

Ser-ice ata ?low

=oS

=ualit o' Ser-ice

=CI

=oSClassIdenti'ier

AAA

Authentication, Authorization and Accounting

%AI
%e*oteAuthenticationial0In
?BC

?lowBasedCharging

CD"S

Co**onD#en"olicSer-ice

9SA"I

9etworSer-iceAccess"ointIdenti'ier

TI

TransactionIdenti'ier

T?T

Tra''ic?ilteringTe*#late

I3S

I"3ulti*ediaSu&sste*

S"

Sessionescri#tion"rotocol

CSC?

CallSessionControl?unction

"0CSC?

"ro>CallSessionControl?unction

ICI

I3SChargingIdenti'ier

#ssue '.() *)+'(-)/


$iv


Catalog

S"%

Su&scri#tion"ro'ile%e#ositor

A"9

Access "oint 9a*e

B%AS

Broad&and%e*oteAccessSer-er

#ssue '.() *)+'(-)/


$v

0CC9$#nterface"pecification

2eference2eference

1

Reference



#&T7 27C )B?@E !2emote Authentication 6ial #n ser "ervice *2A6#"/ !.



#&T7 27C -'?)E !2A6#" and #0v?!.



#&T7 27C -@BBE !6iameter >ase 0rotocol!.



#&T7 27C (++?E !6iameter Credit Control Application!.



-900 T2 )'.;+@E !=ocabulary for -900 "pecifications!.



-900 T" );.)+BE !&ndtoend 8uality of "ervice *8o"/ signalling flows!.



-900 T" )-.)+-E !0olicy Control and Charging architecture!.



-900 T" );.)')E !0olicy and Charging Control over 9$ reference point!.



-900 T" );.)'-E !0olicy and charging control signalling flows and 8uality of "ervice *8o"/ parameter mapping!.



-900 T" );.)'(E !0olicy and Charging Control over 2$ reference point!.



-900 T" )-.+?+E !9eneral 0acket 2adio "ervice *902"/F "ervice descriptionF "tage )!.



-900 T" );.+?+E !9eneral 0acket 2adio "ervice *902"/F 902" Tunnelling 0rotocol *9T0/ across the 9n and 9p interface!.



-900 T" );.+?'E !#nterworking between the 0ublic Land 5obile Network *0L5N/ supporting packet based services and 0acket 6ata Networks *06N/!.



-900 T" )(.++BE !5obile radio interface Layer - specification!.



-900 T" );.)-+E !6iameter applicationsF-900 specific codes and identifiers!.



-900 T" -).)(+E !Telecommunication managementF Charging managementF Charging architecture and principles!.



-900 T" -).)@'E !Telecommunication managementFCharging managementF0acket "witched *0"/ domain charging!.



-900 T" -).)?+E !Telecommunication managementF Charging managementF #0



5ultimedia "ubsystem *#5"/ charging!. -900 T" -).);BE !Telecommunication managementF Charging managementF Charging 6ata 2ecord *C62/ encoding rules description!.



#ssue '.() *)+'(-)/

-900 T" -).);;E !Telecommunication managementF Charging managementF 6iameter charging applications!.


'


#ntroductionandscope#ntroductionandscope

2

Introduction and scope

#n 0CC architecture, there are si$ main components listed as followsE 0C&7, 0C27, A7, 3C", 37C" and "02. The 0C27 encompasses policy control decision and flow based charging control functionalities. The 0C&7 encompasses service data flow detection, policy enforcement and flow based charging functionalities. The reference point between 0C27 and 0C&7 is 9$ which is used for provisioning and removal of 0CC rules from the 0C27 to the 0C&7 and the transmission of traffic plane events from the 0C&7 to the 0C27. 7igure '.' 7igure '.'shows the reference model for 9$.

#ssue '.() *)+'(-)/


'


#ntroductionandscope#ntroductionandscope

Figure 1.19$ 2eference 5odel

Su4scription Profi0e Repositor+ 5SPR6

S# (n0ine C-ar,in, S+ste2 5(CS6 C#9%) SCP

Ser1ice Data 70o/ 8ased Credit Contro0

Sco#e o' this docu*ent

75

#7 Rx

Po0ic+ and C-ar,in, Ru0es 7unction 5PCR76

7>

PC%7

G$ 7z

(ff0ine C-ar,in, S+ste2 5(7CS6

#ssue '.() *)+'(-)/


)


TerminologyTerminology

3

Terminology

PDP Session: for 902", 060 session is a uniearer Control 5ode determines which side can initiate the secondary 060 conte$t activation procedure, network or &. #f the negotiation result is J& 3nlyK, only the & side can initiate the secondary 060 conte$t activation procedure. #f the negotiation result is JN 3nlyK, only the network side can initiate the secondary 060 conte$t activation procedure. #f the negotiation result is J5i$edK, both & side and Network side can initiate the secondary 060 conte$t activation procedure. PCC Ru"e: 0CC rule is a set of information enabling the detection of a service data flow and providing parameters for policy control andor charging control. &ach 0CC rule has a uni

'


TerminologyTerminology

filter of a 0CC rule that is predefined in the 0C&7 may use parameters that e$tend the packet inspection beyond the #0 @tuple. Ser!ice Data F"ow &e$'"ate: "ervice data flow template is the collection of service data flow filters in a 0CC rule, reearer binding means the association between a service data flow and the #0CAN bearer transporting that service data flow. Bearer Binding #ec(anis$:>earer >inding 5echanism refers to the method for creating, modifying and deleting bearer bindings. #t can be classified into two typesE 0C27based bearer binding and 0C&7>ased bearer binding. 7or 0C27>ased bearer binding, the association between "67 and #0CAN bearer is determined solely by 0C27. 7or 0C&7>ased bearer binding, "67 is associated with #0CAN bearer mainly by 0C&7. The output of 0C&7 >ased bearer binding is recogniGed as the input of N2"0CA procedure. )oS C"ass Identi%ier: 8o" class identifier is an identifier representing 8o" parameters, such as TransportClass, Transport0riority, e$cluding the bitrates. Aut(ori*ed )oS: AuthoriGed 8o" is the ma$imum 8o" that is authoriGed by 0C27. Three types of authoriGed 8o" are identified over 9$ reference pointE 8o" per #0CAN >earer, 8o" per 8C# and 8o" per 0CC rule. 7or 8o" per #0CAN >earer, it applies to all service data flows with an #0CAN >earer. 7or 8o" per 8C#, it is similar to 8o" per #0CAN >earer, while it is used with 0C&7>ased bearer binding. 7or 8o" per 0CC rule, it applies to all service data flows within a rule and it is usually used within dynamic 0CC rule. Rating-+rou': 2ating9roup is the charging key used by the online and offline charging system for rating purposes. Ser!ice-Identi%ier: "ervice#dentifier provides the most detailed identification, specified for flow based charging, of a service data flow.

#ssue '.() *)+'(-)/


)


0rotocol3verview0rotocol3verview



!rotocol "vervie#

#nformation is e$changed over 9$ reference point through messages specified by 6iameter >ase 0rotocol, 6iameter Credit Control Application and 9$ Application. 6iameter is the newest AAA protocol developed in )++' from the older AAA protocol 2A6#". 6iameter >ase 0rotocol provides a framework for AAA, and it is e$pected to be e$tended to support new applications. 6iameter Credit Control Application is developed to provide a general solution to realtime cost and credit control. 9$ application provides e$tended authoriGation for policy and charging control and it is based on both 6iameter >ase 0rotocol and 6iameter Credit Control Application. 7igure '.) shows the layout of 9$ #nterface protocol stack is depicted as followsE Figure 1.,9$ #nterface 0rotocol "tack

.1 Diameter 6iameter is an AAA protocol and it was derived from the 2adius protocol with many improvements in different aspects. 6iameter was chosen by the -900 as the foundation for all AAA functionalities including policy and charging control. Currently, the 6iameter specification consists of a base specification 6iameter >ase 0rotocolI, a Transport 0rofile AAAT2AN"I and some e$teneded applications such as 6iameter Credit Control Application, 9$ Application, etc.

#ssue '.() *)+'(-)/


'


0rotocol3verview0rotocol3verview

.2 Diameter ase !rotocol The 6iameter >ase 0rotocol defines the base specification for AAA, which includes support for accounting. The 6iameter >ase 0rotocol may be used by itself for accounting applications, but for use in authentication and authoriGation it is always e$tended for a particular application. The 6iameter >ase 0rotocol concerns itself with capabilities negotiation, how messages are sent and how peers may eventually be abandoned, etc. The base protocol also defines certain rules that apply to all e$changes of messages between 6iameter nodes. 0lease refer to 27C-@@B for details.

.3 / *pplication #t is wellknown that 0CC is an evolution of 7>C and ">L0. 7>C is defined in -900 release ?, and for which an new 6iameter application is incorporated to provide charging control functionalities and is named as 9$. ">L0 is defined in -900 release @, and an C30" based application is incorporated to provide policy control functionalities and is named as 9o. #n -900 release , 0CC merged 2elease ? 9$ application and 2elease @ 9o application into a new application which is also named as 9$. 3f course, 2elease  9$ application is an fire new one, and it can provides policy control functionalities and charging control functionalities at the same time. Also, there are some 9$ variants, most of which are vendor specific and are entended on the basis of -900 2elease ? 9$ application. #n this version, only 2elease  9$ application is implemented, but it is e$tensible to add adaption for 2elease ? 9$ application and other vendor specific variants. 7or -900 2elease  9$ application, 0lease refer to T");.)') for details.

. Interface *uthentication mechanism This interface is using 6iameter protocol. This interface can use #0 address for authentication.

#ssue '.() *)+'(-)/


)


TransportTransport

$

Transport

The 6iameter >ase 0rotocol mandates that the diameter server must support TC0 and "CT0, and mandates that the client must support either TC0 or "CT0. 0lease refer to 27C-@BB for details.

#ssue '.() *)+'(-)/


'


ConstraintsConstraints

%

Constraints

%.1 earer Control 'ode #n -900 release , the concept of bearer control mode is incorporated to support network initiated 8o" control, and 0CC framework also provides support for this. HuaweiMs 0CC supports &#nitiated >earer &stablishment mode based on primary 060 conte$t activation procedure, as defined in -900 2el.

Huawei currently does not foresee any commercial demand for & initialled 8o" control, and the & #nitiated secondary 060 conte$t activation procedure is to comple$ for the & and not widely supported in commercially available terminals. #n the future 0CC will focus on the network centric 8o" control mechanism where dedicated bearers *i.e. secondary 060 conte$ts/ are always established, modified, and released by the network, and default bearers *i.e. primary 060 conte$ts/ are only modified by the network.

%.2 0o negotiation #n -900 2elease  there have been some additions in relation with the 8o" capabilities that the "9"N could support. According to "tage - 902" specifications, "9"N may indicate the 99"NE 

hether it supports 8o" upgrading from the 99"N.



hether it is possible to negotiate the 8o" provided in the 060 pdate 060 Conte$t.

The "9"N limitations have to be provided to 0C27 so that it can act accordingly when authoriGing the received 8o" information in the cases where the 0C27 makes the bearer binding. Two new A=0s has been created for this purpose, 8o"Negotiation A=0 and 8o" pgrade A=0, so that the 0C&7 can inform 0C27 about the 8o" limitations *8o" upgrading not supported  8o" negotiation not supported/ of the #0CAN.

%.3 +imitations 

#ssue '.() *)+'(-)/

Huawei 0CC can only accept '+ service level
'

0CC9$#nterface"pecification 

#ssue '.() *)+'(-)/

ConstraintsConstraints

Huawei 0CC can only send '+ service level

)


5essages5essages

&

'essages

&.1 'essage ormat 7igure '.- shows the diameter message format. Figure 1.6iameter 5essage 7ormat

6iameter Header

A=0

A=0Header

A=0

A=0

A=06ata

0lease refer to 27C-@BB for details.

&.2 ase 'essages &.2.1 Capa,ilities-/change-Re4uest 5CR6 The Capabilities&$change2e

'


5essages5essages

S =endor#d  S 0roductName   3rigin"tate#d I U  "upported=endor#d I U  AuthApplication#d I U  #nband"ecurity#d I U  AcctApplication#d I U  =endor"pecificApplication#d I  7irmware2evision I U  A=0 I

&.2.2 Capa,ilities-/change-*ns#er 5C*6 The Capabilities&$changeAnswer *C&A/, indicated by the CommandCode set to )@ and the Command 7lagsO O2O bit cleared, is sent in response to a C&2 message. 5essage "ynta$E PC&AQEER P 6iameter HeaderE )@ Q S 2esultCode  S 3riginHost  S 3rigin2ealm  'U S Host#0Address  S =endor#d  S 0roductName   3rigin"tate#d I  &rror5essage I U  7ailedA=0 I U  "upported=endor#d I U  AuthApplication#d I U  #nband"ecurity#d I U  AcctApplication#d I U  =endor"pecificApplication#d I  7irmware2evision I U  A=0 I

#ssue '.() *)+'(-)/


)


5essages5essages

&.2.3 Disconnect-!eer-Re4uest5D!R6 The 6isconnect0eer2e
&.2. Disconnect-!eer-*ns#er5D!*6 The 6isconnect0eerAnswer *60A/, indicated by the CommandCode set to )B) and the Command 7lagsO O2O bit cleared, is sent as a response to the 6isconnect0eer2e
&.2.$ Device-7atchdog-Re4uest5D7R6 The 6eviceatchdog2e
&.2.% Device-7atchdog-*ns#er5D7*6 The 6eviceatchdogAnswer *6A/, indicated by the CommandCode set to )B+ and the Command 7lagsO O2O bit cleared, is sent as a response to the 6eviceatchdog2e

-


5essages5essages

S 2esultCode  S 3riginHost  S 3rigin2ealm   &rror5essage I U  7ailedA=0 I  3riginal"tate#d I

&.2.& *,ort-ession-Re4uest5*R6 The Abort"ession2e
&.2.( *,ort-ession-*ns#er 5**6 The Abort"essionAnswer *A"A/, indicated by the CommandCode set to )( and the message flagsO O2O bit clear, is sent in response to the A"2. 5essage synta$E PA"AQEER P 6iameter HeaderE )(, 0:V Q P "ession#d Q S 2esultCode  S 3riginHost  S 3rigin2ealm   3rigin"tate#d I  &rror5essage I  &rror2eportingHost I #ssue '.() *)+'(-)/


(


5essages5essages

U  7ailedA=0 I U  2edirectHost I  2edirectHostsage I  2edirect5a$CacheTime I U  0ro$y#nfo I U  A=0 I

&.3 / 'essages &.3.1 Credit-Control-Re4uest 5CCR6 The CC2 command, indicated by the CommandCode field set to )) and the O2O bit set in the Command 7lags field, is sent by the 0C&7 to the 0C27 in order to reearerControl5ode I  Network2eearer#dentifier I  >earer3peration I  7ramed#0Address I #ssue '.() *)+'(-)/


@


5essages5essages

 7ramed#0v?0refi$ I  #0CANType I -9002ATTypeI 2ATTypeI  TerminationCause I  ser&earersage I  3nline I  3ffline I U T7T0acket7ilter#nformation I U Charging2ule2eportI U &ventTriggerI [X-HW-Tethering-Status]

 AccessNetworkChargingAddress I U AccessNetworkCharging#dentifier9$ I :Hsage2eportI U sage5onitoring#nformation I U 0ro$y#nfo I U 2oute2ecord I :HCellCongestionLevelI UApplication6etection#nformationI :Hser0hysical#nfo=alueI

#ssue '.() *)+'(-)/


?


5essages5essages

U A6C2ule2eport I U A=0 I

&.3.2 Credit-Control-*ns#er 5CC*6 The CCA command, indicated by the CommandCode field set to )) and the O2O bit cleared in the Command 7lags field, is sent by the 0C27 to the 0C&7 in response to the CC2 command. #t is used to provision 0CC rules and event triggers for the bearersession and to provide the selected bearer control mode for the #0CAN session. 5essage synta$E PCCAnswerQ EER P 6iameter HeaderE )), 0:V Q P "ession#d Q S AuthApplication#d  S 3riginHost  S 3rigin2ealm   2esultCode I  &$perimental2esult I S CC2eearerControl5ode I U &ventTrigger I  3rigin"tate#d I U 2edirectHost I U Charging2ule2emove I U Charging2ule#nstall I U 8o"9roup2ule2emove I U 8o"9roup2ule#nstall I  Charging#nformation I  3nline I  3ffline I U 8o"#nformation I  2evalidationTime I  6efault&0">earer8o" I :Hsage2eportI "ession2eleaseCauseI

#ssue '.() *)+'(-)/





5essages5essages

U sage5onitoring#nformation I U :H"ubscriber"ervice6efinition I :H"ession2estorationI :HContent7ilterI :HContent7ilter#nformationI  &rror5essage I  &rror2eportingHost I U 7ailedA=0 I U 0ro$y#nfo I U 2oute2ecord I U A6C2ule#nstallI U A6C2ule2emoveI :Header&nrichmentI U A=0 I

&.3.3 Re-*uth-Re4uest 5R*R6 The 2A2 command, indicated by the CommandCode field set to )@B and the O2O bit set in the Command 7lags field, is sent by the 0C27 to the >>&270C&7 in order to provision 8o"0CC rules using the 0"H procedure initiate the provision of unsolicited 8o"0CC rules. #t is used to provision 8o"0CC rules, event triggers and event report indications for the session. 5essage synta$E ::=< Diameter Header: 25! R"#! $X% >

P "ession#d Q S AuthApplication#d  S 3riginHost  S 3rigin2ealm  S 6estination2ealm  S 6estinationHost  S 2eAuth2e

B


5essages5essages

U Charging2ule#nstall I U 8o"9roup2ule2emove I U 8o"9roup2ule#nstall I  6efault&0">earer8o" I U 8o"#nformation I  :Hsage2eport I 2evalidationTimeI U sage5onitoring#nformation I U :H"ubscriber"ervice6efinition I :HContent7ilterI :HContent7ilter#nformationI U 0ro$y#nfo I U 2oute2ecord I U A6C2ule#nstallI U A6C2ule2emoveI U A=0I

&.3. Re-*uth-*ns#er 5R**6 The 2AA command, indicated by the CommandCode field set to )@B and the O2O bit cleared in the Command 7lags field, is sent by the 0C&7 to the 0C27 in response to the 2A2 command. 5essage synta$E P2AAnswerQEER P 6iameter HeaderE )@B, 0:V Q P "ession#d Q S 3riginHost  S 3rigin2ealm   2esultCode I  &$perimental2esult I  3rigin"tate#d I  &ventTrigger I U Charging2ule2eportI  AccessNetworkChargingAddress I U AccessNetworkCharging#dentifier9$ I  >earer#dentifier I  &rror5essage I #ssue '.() *)+'(-)/


;


5essages5essages

 &rror2eportingHost I U 7ailedA=0 I U 0ro$y#nfo I U A6C2ule2eport I U A=0 I

#ssue '.() *)+'(-)/


'+


0rocedures0rocedures

(

!rocedures

All signaling flows in this section are only for illustration purpose, so subtle difference between description here and real implementation is allowed as long as it does not affect interoperability.

(.1 Capa,ility 8egotiation for 3!! R& / *pplication Capability negotiation allows 0C&7 and 0C27 to discovery its peerMs identify and capabilities such as supported applications. 7igure '.( e$emplified the signaling flows for this procedure from the point of view of 0CC.

#ssue '.() *)+'(-)/


'



Figure 1.Capability Negotiation for -900 2 9$ Application

#ssue '.() *)+'(-)/


)



'.

The 0C&7 establishes transport connection with the 0C27.

).

The 0C&7 sends Capability&$change2ease 0rotocol and a =endor"pecific Application#d A=0 is included in the message body, indicating the support of -900 2 9$ application.

-.

The 0C27 acknowledges and ret urns a Capability&$changeAnswer message to the 0C&7. Application #d in diameter header is also to +, indicating the 6iameter >ase 0rotocol, and also a =endor"pecificApplication#d A=0 is included in the message body, indicating the support of -900 2 9$ application.

(.

After the capability e$change of both is succeeded, -900 2 9$ application peers is enabled forsides 0C&7 and 0C27.interaction 7or eachbetween 9$ transaction, Application #d in diameter header will be set to '?)-B, indicating the -900 2 9$ application, and AuthApplication#d A=0 is included in the message body, also indicating the -900 2 9$ application.

(.2 I!-C*8 ession sta,lishment The activation of a primary 060 conte$t causes a new #0CAN session to be established. 7igure (.' e$emplifies the signaling flows for this procedure. Figure .1#0CAN "ession &stablishment

'.

The & attaches to 902" network.

).

The & sen ds an Act ivate 060 Co nte$t 2e
-.

The "9"N validates the Activate 060 Conte$t 2e
#ssue '.() *)+'(-)/


-



(.

The 99"N validates the Create 060 Conte$t 2e
@.

The 0C27 makes a multidimensional authoriGation decision for this #0C AN session, based on all available information such as subscription, time, location, service, dynamic A7 session parameters, etc. And then, the 0C27 returns the authoriGation result in CreditControlAnswer message to the 99"N.

?.

The 99"N installs 0CC rul es and en forces authoriGed 8o" ac cording to the 0C2 7Ms reC5/ message to the "9"N.

.

The "9"N verifies the Cre ate 060 Conte$t 2esponse message and saves all ne cessary information in its own conte$t. #n the end, the 2A6 is setup and the "9"N returns a Activate 060 Conte$t Accept *060 Type, 060 Address, T#, 8o" Negotiated, 2adio 0riority, 0acket 7low #d, 0rotocol Configuration 3ptions/ message to the &.

(.3 9 ide Initiated I!-C*8 earer 'odification The update of a 060 conte$t causes the corresponding #0CAN bearer to be modified. 7igure .' e$emplifies the signaling flows for this procedure. Figure /.1& "ide #nitiated #0CAN >earer 5odification

'.

#ssue '.() *)+'(-)/

The 5" sen ds a 5odif y 060 Conte$t 2e
(



).

The "9"N validates the 5odify 060 Co nte$t 2e
-.

The 99"N validates the p date 060 Conte$t 2e
(.

The 0C27 recalculate authoriGation according to reported updates and returns the result in CreditControlAnswer message to the 99"N.

@.

The 99"Ntoinstalls, modifies, or rem 0CC replies rule s and enf orces aut horiGed 8o" according 0C27Ms indication. Theoves 99"N pdate 060the Conte$t 2esponse message to the "9"N.

?.

The "9"N verifies the pdate 060 Conte$t 2esponse message and saves all necessary information in its own conte$t. After the 2A> modified the "9"N returns a 5odify 060 Conte$t Accept *T#, 8o" Negotiated, 2adio 0riority, 0acket 7low #d, and 0rotocol Configuration 3ptions/ message to the &.

(. 9 ide Initiated I!-C*8 ession Termination The deactivation of 060 conte$t causes the corresponding #0CAN bearer to be terminated. #f the removed 060 conte$t is the last one in #0CAN session, #0CAN session will be terminated. 7igure ?.' e$emplifies the signaling flows for this procedure. Figure 0.1& "ide #nitiated #0CAN "ession Termination

'.

The 5" sends a 6eactivate 060 Conte$t 2e
).

The "9"N validates the 6e activate 060 Conte$t 2e
-.

The 99"N loc ates the cor responding 060 co nte$t and #0CAN ses sion. #f 0CC is enabled for this #0CAN session and thatMs the last 060 conte$t of the #0CAN session,

#ssue '.() *)+'(-)/


@



the 99"N will send a CreditControl2e
The 0C27 revoke authoriGation for this #0CAN sess ion, and returns a confirming CreditControlAnswer message to the 99"N.

@.

The 99"N removes all 0CC rul es bind wit h the #0C AN session, release resources and reply the "9"N with a 6elete 060 Conte$t 2esponse message.

?.

The "9"N release corresponding resources and send s back a 6eactivate 060 Conte$t Accept message to the &.

(.$ !CR Initiated I!-C*8 ession 'odification 2eauthoriGation pushed from 0C27 causes corresponding #0CAN session to be modified. 7igure ?.' e$emplifies the signaling flows for this procedure. Figure 0.10C27 #nitiated #0CAN "ession 5odification

'.

The 0C27 receives an internal *e.g. special hour of day/ or e$ternal trigger *A7 session established/ to reevaluate policy decision for an #0CAN "ession. #f policy update is needed the 0C27 sends a 2eAuth 2e
).

The 99"N validates the 2e Auth 2e
-.

#f authoriGed 8o" is upda ted 99"N will initial 8o" re servation process. The 99"N sends an pdate 060 Conte$t 2e
(.

#n case of any err or occur during the 8o" res ervation process, correlated rules will be deactivated and 99"N shall create and send a CC2e
#ssue '.() *)+'(-)/


?



Type set to be JpdateK and contains one or more Charging2ule2eport A=0 to report the infected rules. @.

pon receiving a CC2e
(.% !CR Initiated I!-C*8 ession Termination 7orced removal of authoriGation initiated by 0C27 causes corresponding #0CAN session to be terminated. 7igure @.' e$emplifies the signaling flows for this procedure. Figure .10C27 #nitiated #0CAN "ession Termination

'.

hen the 0C27 detects that th e termination of an #0 CAN "ession is re
).

The 99"N validates the Ab ort"ession2e
#ssue '.() *)+'(-)/

W

The 99"N s ends a 6elete 060 Conte$t 2e
W

The "9"N sends a 6eactivate 060 Conte$t 2e
W

The 5" removes the 060 conte$t and returns a 6eactivate 060 Conte$t Accept message to the "9"N. At the same time, 2A> for this 060 conte$t is scheduled to release.

W

The "9"N returns a 6elete 060 Conte$t 2esponse *T/ message to the 99"N. Huawei 0roprietary and Confidential Copyright 1 Huawei Technologies Co., Ltd



0CC9$#nterface"pecification W


The 99"N continues the processing steps for 060 deactivation, and on completion, releases the 060 conte$t table entry.

-.

pon completion, the 99"N release the #0CAN session table entry, and sends a Credit Control2e
(.

The 0C27 simply acknowledges and re turns a CreditControlAnswer message to the 99"N.

(.& 9sage Report Accumulated usage information of subscriber can be used for policy decision. To support the usage accumulation in 0C27 the 0C&7 shall report usage information to 0C27 as re
3n initial policy authoriGation, 0C27 can indicate 0C&7 to report traffic usage information for specified
?.

3n rea ching
.

3n receiving traffic usage report from 0C&7, 0C27 recalculates the accumulated usage, and updates policy accordingly. At the same time, the
7igure .' is an illustration of this procedure.

#ssue '.() *)+'(-)/


B



Figure /.1#llustration of 0olicy Control >ased 3n Accumulated sage

#n this release, only volume based threshold can be supported, and service is identified by the combination of 2ating9roup and "ervice#dentifier.

#ssue '.() *)+'(-)/



7rom the release of 0CC =-++2++)C+@, the "ervice#dentifier will not be used to identify usage combination, and the 0CC will not given "ervice#dentifier A=0 in the :H"ervicesage.



7rom the release of 0CC =-++2++)C+@, the 2ating9roup used for usage combination will be replaced by the concept of 5onitoringey, but same A=0 will be used. That means, in the :H "ervicesage the 2ating9roup shall be treated as the :H5onitoringey.



hen usage monitoring and reporting is enabled, the 0C&7 shall report accumulated usage to the 0C27 in the following conditionsE W

hen a usage threshold is reached.

W

hen all 0CC rules for which usage monitoring and reporting is enabled for a particular usage monitoring key are removed or deactivated. Huawei 0roprietary and Confidential Copyright 1 Huawei Technologies Co., Ltd

;



W

hen usage monitoring and reporting is disabled.

W

hen a 0CC revalidation timeout occurs.

W

hen an #0CAN session is terminated.

(.( *udit 0eriodical audit is a fre
0C27 #nitiated #0CAN "ession Audit

To make sure every #0CAN session table entry in use is aligned with 0C&7, the 0C27 can periodically check with the 0C&7 by e$changing audit messages using 2eAuth2e
'.

hen periodical audit timer is e$pired, one or more #0CAN sessions in use is selected by 0C27 for audit purpose. 7or each of these #0CAN sessions, the 0C27 sends an empty 2eAuth2e
).

The 0C&7 checks whether the #0CAN session is still active *base on sessionid/ or not. The 0C&7 negatively acknowledges by returning a 2eAuthAnswer message to the 0C27 with 2esultCode set to J6#A5&T&24NN3N4"&""#3N4#6K if the session is not e$ists on 0C&7, otherwise the 2esultCode set to J"uccessK if this session still live.

-.

pon the rec eipt of 2eA uthAnswer message from th e 0C&7, the 0C27 ch ecks the 2esultCode. #f it is J6#A5&T&24NN3N4"&""#3N4#6K, #0CAN session will be removed by 0C27 locally.



0C&7 #nitiated #0CAN "ession Audit

To make sure every #0CAN session table entry in use is aligned with 0C27, the 0C&7 can periodically check with the 0C27 by e$changing audit messages. 7igure -.' e$emplifies the signaling flows for this procedure.

#ssue '.() *)+'(-)/


'+



Figure .10C&7 #nitiated #0CAN "ession Audit

'.

hen periodical audit timer is e$pired, one or more #0CAN sessions in use is selected by 0C&7 for audit purpose. 7or each of these #0CAN sessions, the 0C&7 sends a CreditControl2e
).

The 0C27 checks whether the authoriGation of this #0CAN session is still valid, and if it is not, the 0C27 negatively acknowledges by returning a CreditControlAnswer message to the 0C&7, with 2esultCode set to J6#A5&T&24NN3N4"&""#3N4#6K.

-.

pon the rece ipt of Cred itControlAnswer message from the 0C27, the 0C&7 checks the 2esultCode. #f it is J6#A5&T&24NN3N4"&""#3N4#6K, #0CAN session will be removed by 0C&7 locally.

#ssue '.() *)+'(-)/


''


A=0s6efinitionA=0s6efinition

)

*V!s Definition

).1 ession-Id The "ession#d A=0 *A=0 Code )?-/ is of type T7B"tring is generated by 0C&7 to identify a specific #0CAN session. All messages pertaining to a specific #0CAN session include only one "ession#d A=0 and the same value is used throughout the life of #0CAN session. hen present, the "ession#d appears immediately following the 6iameter Header. The "ession#d includes a mandatory portion and an implementation  defined portion, and the protocol recommended format is followedE

;;[;] 7or details, please refer to #&T7 27C -@BB.



The ma$imum length of "ession#d is ?( bytes.



6iameter#dentity is encoded as the 0C&7Ms host identifier, and the remainder can be any se
).2 *uth-*pplication-Id The AuthApplication#d A=0 *A=0 Code )@B/ is of type nsigned-) and is used here to advertise support of the 9$, 9$$ application. Now, only -900 9$ and 9$$ application is supported, so this A=0 will be encoded fi$edly as the value of J'?)-BK and J'?)??K. 7or details, please refer to #&T7 27C -@BB, -900 T" );.)') and -900 T" );.)-+.

).3 Vendor-Id The =endor#d A=0 *A=0 Code )??/ is of type nsigned-) and contains the #ANA !"5# Network 5anagement 0rivate &nterprise Codes! value assigned to the vendor of the 6iameter application. #n combination with the "upported=endor#d A=0, this may be used in to know which vendor specific attributes may be sent to the peer. #t is also envisioned that the #ssue '.() *)+'(-)/


'



combination of the =endor#d, 0roductName and the 7irmware2evision A=0s may provide very useful debugging information. A =endor#d value of Gero in the C&2 or C&A messages is reserved and indicates that this field is ignored. 7or details, please refer to #&T7 27C -@BB, -900 T" );.)') and -900 T" );.)-+.

#n this version, only the value J'+('@K assigned to -900 is supported.

). !roduct-8ame The 0roductName A=0 *A=0 Code )?;/ is of type T7B"tring, and contains the vendor assigned name for the product. 7or details, please refer to #&T7 27C -@BB.

).$ upported-Vendor-Id The "upported=endor#d A=0 *A=0 Code )?@/ is of type nsigned-) and contains the #ANA !"5# Network 5anagement 0rivate &nterprise Codes! A""#9NN3I value assigned to a vendor other than the device vendor. This is used in the C&2 and C&A messages in order to inform the peer that the sender supports *a subset of/ the vendorspecific A=0s defined by the vendor identified in this A=0. 7or details, please refer to #&T7 27C -@BB, -900 T" );.)') and -900 T" );.)-+. #n this version of 9$ and 9$$ application, -900 *'+('@/ and -900) *@@-@/ can be advertised in this A=0 between peers.

).% irm#are-Revision The 7irmware2evision A=0 *A=0 Code )?/ is of type nsigned-) and is used to inform a 6iameter peer of the firmware revision of the issuing device. 7or details, please refer to #&T7 27C -@BB.

).& Vendor-pecific-*pplication-Id The =endor"pecificApplication#d A=0 *A=0 Code )?+/ is of type 9rouped and is used to in capability e$change procedure to advertise support of a vendorspecific 6iameter Application. #ts 6ata field has the following A>N7 grammarE P=endor"pecificApplication#dQ EER P A=0 HeaderE )?+ Q 'U  =endor#d I +U'S AuthApplication#d  +U'S AcctApplication#d 

#ssue '.() *)+'(-)/


)



#n this version, =erdor#d A=0 is set to -900 *'+('@/, one AuthApplication#d is included and is set -900 2elease  9$ application*'?)-B/, and AcctApplication#d A=0 is not used. 7or details, please refer to #&T7 27C -@BB and -900 T" );.)').

).( "rigin-:ost The 3riginHost A=0 *A=0 Code )?(/ is of type 6iameter#dentity, and is present in all 6iameter messages to identify the endpoint that srcinated the 6iameter message. 7or messages generated by 99"N, it is encoded as the 0C&7Ms host identifier. 7or messages generated by 0C27, it is encoded as the 0C27Ms host identifier. 7or details, please refer to #&T7 27C -@BB.

The ma$imum length of 3riginHost is ?( >ytes.

).) "rigin-Realm The 3rigin2ealm A=0 *A=0 Code );?/ is of type 6iameter#dentity and is present in all messages to identify the realm of the srcinator. 7or details, please refer to #&T7 27C -@BB.

5a$imum length is ?( >ytes.

).1; Destination-:ost The 6estinationHost A=0 *A=0 Code );-/ is of type 6iameter#dentity. This A=0 is always presented in all unsolicited agent initiated messages, may be presented in re

).11 Destination-Realm The 6estination2ealm A=0 *A=0 Code )B-/ is of type 6iameter#dentity, and contains the realm the message is to be routed to. 7or details, please refer to #&T7 27C -@BB.

#ssue '.() *)+'(-)/


-





The 6estination2ealm A=0 is always absent from answer messages.




).12 Termination-Cause The TerminationCause A=0 *A=0 Code );@/ is of type &numerated, and is used to indicate the reason why a #0CAN session was terminated. The TerminationCause A=0 can only be presented in CreditControl2e
6#A5&T&24L393T*'/ The user initiated a disconnect.

@.

6#A5&T&24"&2=#C&4N3T4023=#6&6*)/ This value is used when the user disconnected prior to the receipt of the authoriGation answer message.

?.

6#A5&T&24>A64AN"&2*-/ This value indicates that the authoriGation answer received by the access device was not processed successfully.

.

6#A5&T&24A65#N#"T2AT#=&*(/ The user was not granted access, or was disconnected, due to administrative reasons, such as the receipt of a Abort"ession2e
B.

6#A5&T&24L#N4>23&N*@/ The communication to the user was abruptly disconnected.

;.

6#A5&T&24ATH4&:0#2&6*?/ The userOs access was terminated since its authoriGed session time has e$pired.

'+. 6#A5&T&24"&2453=&6*/ The user is receiving services from another access device. ''. 6#A5&T&24"&""#3N4T#5&3T*B/ The userOs session has timed out, and service has been terminated. 7or details, please refer to #&T7 27C -@BB.

).13 Disconnect-Cause The 6isconnectCause A=0 *A=0 Code )-/ is of type &numerated and is included in the 6isconnect0eer2e33T#N9*+/ A scheduled reboot is imminent. '-. >"V*'/ The peerOs internal resources are constrained, and it has determined that the transport connection needs to be closed. '(. 634N3T4ANT4T34TAL4T34V3*)/

#ssue '.() *)+'(-)/


(



The peer has determined that it does not see a need for the transport connection to e$ist, since it does not e$pect any messages to be e$changed in the near future. 7or details, please refer to #&T7 27C -@BB.

).1 "rigin-tate-Id The 3rigin"tate#d A=0 *A=0 Code )B/, of type nsigned-) and is used to allow rapid detection of termination of sessions due to unanticipated shutdown of an access device. #n this version, it is not used, i.e., for messages srcinated from 0C&7 3rigin"tate#d A=0 is always absent, and for messages from 0C27, 3rigin"tate#d A=0 is always ignored. 7or details, please refer to #&T7 27C -@BB.

).1$ Result-Code The 2esultCode A=0 *A=0 Code )?B/ is of type nsigned-) and indicates whether a particular re
).1% /perimental-Result The &$perimental2esult A=0 *A=0 Code );/ is of type 9rouped, and indicates whether a particular vendorspecific reN7 grammarE &$perimental2esult EER P A=0 HeaderE ); Q S =endor#d  S &$perimental2esultCode  7or 9$ application, The =endor#6 A=0 is set to -900 *'+('@/, and &$perimental2esult Code is set to a vendor assigned value. 7or details, please refer to #&T7 27C -@BB and -900 T" );.)').

#ssue '.() *)+'(-)/


@



).1& rror-'essage The &rror5essage A=0 *A=0 Code )B'/ is of type T7B"tring and it is optionally used to accompany a 2esultCode A=0 or &$perimental2esult A=0 as a human readable error message. 7or details, please refer to #&T7 27C -@BB.

#n this version, &rror5essage A=0 is ignored.

).1( ailed-*V! The 7ailedA=0 A=0 *A=0 Code );/ is of type 9rouped and is optionally used to accompany a 2esultCode A=0 or &$perimental2esult A=0 to provide debugging information about erroneous details of a specific A=0. 7or details, please refer to #&T7 27C -@BB.

#n this version, 7ailedA=0A=0 is ignored.

).1) Re-*uth-Re4uest-Type The 2eAuth2e
).2; Called-tation-ID The Called"tation#d A=0 *A=0 Code -+/ is of type T7B"tring and is used to describe the address the user is connected to. 7or 902", it is encoded as the A0N. 7or details, please refer to #&T7 27C (++@ and -900 T" );.)').

5a$imum length supported is ?( >ytes.

).21 ramed-I!-*ddress The 7ramed#0Address A=0 *A=0 Code B/ 2A6#"I is of type 3ctet"tring and contains an #0v( address allocated for the user. 7or details, please refer to #&T7 27C (++@ and -900 T" );.)').

#ssue '.() *)+'(-)/


?



).22 ramed-I!v%-!refi/ The 7ramed#0v?0refi$ A=0 *A=0 Code ;/ is of type 3ctet"tring and contains the #0v? prefi$ allocated for the user. The encoding of the value shall be as defined in #&T7 27C -'?), Clause ).-. The !2eserved!, !0refi$Length! and !0refi$! fields shall be included in this order. 7or details, please refer to #&T7 27C -'?), #&T7 27C (++@ and -900 T" );.)').

).23 CC-Re4uest-Type The CC2e
).2 CC-Re4uest-8um,er The CC2e
).2$ Rating-roup The 2ating9roup A=0 is of type nsigned-) *A=0 Code (-)/ and contains the identifier of a rating group. All the services sub%ect to the same rating type are part of the same rating group. 7or details, please refer to #&T7 27C (++?.

#ssue '.() *)+'(-)/






).2% ervice-Identifier The "ervice#dentifier A=0 is of type nsigned-) *A=0 Code (-;/ and contains the identifier of a service. 7or details, please refer to #&T7 27C (++?.

).2& u,scription-Id The "ubscription#d A=0 *A=0 Code ((-/ is used to identify the end userOs subscription *#5"#, 5"#"6N, etc/ and is of type 9rouped. The "ubscription#d A=0 includes a "ubscription#d6ata A=0 that holds the identifier and a "ubscription#dType A=0 that defines the identifier type. #t is defined as followsE "ubscription#d EER P A=0 HeaderE ((- Q S "ubscription#dType  S "ubscription#d6ata  7or details, please refer to #&T7 27C (++?.

).2( 9ser-4uipment-Info The ser&
).2) 3!!-R*T-Type -9002ATType A=0 is defined as an e$tension to 2A6#" attribute J=endor"pecificK and is used to indicate which 2adio Access Technology is currently serving the &. 7or this A=0, the value field of J=endor"pecificK attribute is encoded as followsE >its (ctets 1

:

!

6

;4

3

2

1

67"" t#e 1 



67"" Length 6

6

%AT @octet string

7or details, please refer to #&T7 27C )B?@ and -900 T" );.+?'.

#ssue '.() *)+'(-)/


B



).3; 3!!-8-*ddress -900"9"NAddress A=0 is defined as an e$tension to 2A6#" attribute J=endor"pecificK and is used to indicate the "9"N #0=( address that is used by the 9T0 control plane. #t may be used to identify the 0L5N to which the user is attached. 7or this A=0, the value field of J=endor"pecificK attribute is encoded as followsE >its (ctets

:

!

6

1

;

4

3

2

1

67"" t#e ;



67"" Length ;

6

S7S9 addr Dctet 1



S7S9 addr Dctet 

5

S7S9 addr Dctet 6

;

S7S9 addr Dctet 


).31 3!!-8-I!v%-*ddress -900"9"N#0v?Address A=0 is defined as an e$tension to 2A6#" attribute J=endor "pecificK and is used to indicate the "9"N #0=? address that is used by the 9T0 control plane. #t may be used to identify the 0L5N to which the user is attached. 7or this A=0, the value field of J=endor"pecificK attribute is encoded as followsE >its (ctets

:

!

6

1

;

4



67"" Length 18

6

S7S9I"-;addrDctet1

 5018

3

2

1

67"" t#e 15 

S7S9I"-;addrDctet S7S9I"-;addrDctet601;


).32 3!!-8-'CC-'8C -900"9"N5CC5NC A=0 is defined as an e$tension to 2A6#" attribute J=endor "pecificK and is used to indicate the 5CC and 5NC of the "9"N. #t is e$tracted from the 2A# within the Create 060 Conte$t 2eits

#ssue '.() *)+'(-)/


;



(ctets

:

!

6

1

;

4

3

2

1

67"" t#e 18 



67"" Length n

6

3CCdigit1 @


3CCdigit @
5

3CCdigit6 @
;

39Cdigit1 @
/

39Cdigit @
8

39C digit6 i' #resent @

).33 3!!-9ser-+ocation-Info -900serLocation#nfo A=0 is defined as an e$tension to 2A6#" attribute J=endor "pecificK and is used to indicate details of where the & is currently located *e.g. "A# or C9#/. 7or this A=0, the value field of J=endor"pecificK attribute is encoded as followsE >its (ctets

:

1

!

6

;4

3

2

1

67"" t#e  



67"" Length *

6

7eogra#hicLocationT#e

0*

7eogra#hic Location@octet string

7or details, please refer to #&T7 27C )B?@ and -900 T" );.+?'. The supported 9eographic Location Type is as follow, which is defined in -900 T" );.)(. + ' ) ')B '); '-+

C9# "A# 2A# TA# &C9# TA# and &C9#

).3 R*I The 2A# A=0 *A=0 Code ;+;/ is of type T7B"tring, and contains the 2outing Area #dentity of the "9"N where the & is registered. 7or details, please refer to -900 T" );.+?' and -900 T" )-.++-.

#ssue '.() *)+'(-)/


'+



).3$ *ccess 8et#or<-Charging-*ddress The AccessNetworkChargingAddress A=0 *A=0 code @+'/ is of type Address, and contains the 99"N #0 address. 7or details, please refer to -900 T" );.)'(.

).3% *ccess 8et#or<-Charging-Identifier-Value The AccessNetworkCharging#dentifier=alue A=0 *A=0 code @+-/ is of type 3ctet"tring, and contains the 9C#6. 7or details, please refer to -900 T");.)'(.

).3& *-Charging-Identifier The A7Applicationidentifier A=0 *A=0 code @+(/ is of type 3ctet"tring, and it contains information that may be used in charging correlation, 7or #5" the #C#6. 7or details, please refer to -900 T");.)'(.

).3( lo#-Description The 7low6escription A=0 *A=0 code @+/ is of type #07ilter2ule, and defines a packet filter for an #0 flow with the following informationE 

6irection *in or out/.



"ource and destination #0 address *possibly masked/.



0rotocol.



"ource and destination port *The "ource 0ort may be omitted to indicate that any source port is allowed./.

The #07ilter2ule type shall be used with the following restrictionsE 

3nly the Action !permit! shall be used.



No !options! shall be used.



The invert modifier !X! for addresses shall not be used.



The keyword !assigned! shall not be used.

The direction !in! refers to uplink #0 flows, and the direction !out! refers to downlink #0 flows. 7or details, please refer to #&T7 27C -@BB and -900 T" );.)'(.

#ssue '.() *)+'(-)/


''



).3) lo#s The 7lows A=0 *A=0 code @'+/ is of type 9rouped, and it indicates the flow identifiers of the #0 flows related to a 0CC rule as provided by the A7. #t may be only used in charging correlation together with A7Charging#dentifier A=0. A=0 7ormat is defined as followsE 7lowsEER P A=0 HeaderE $ Q S 5ediaComponentNumber U 7lowNumberI 7or details, please refer to -900 T" );.)') and -900 T" );.)'(.

).; lo#-tatus The 7low"tatus A=0 *A=0 code @''/ is of type &numerated, and describes whether the #0 flow*s/ are enabled or disabled. The following values are definedE )-. &NA>L&60L#N *+/ This value shall be used to enable associated uplink #0 flow*s/ and to disable associated downlink #0 flow*s/. )(. &NA>L&663NL#N *'/ This value shall be used to enable associated downlink #0 flow*s/ and to disable associated uplink #0 flow*s/. )@. &NA>L&6 *)/ This value shall be used to enable all associated #0 flow*s/ in both directions. )?. 6#"A>L&6 *-/ This value shall be used to disable all associated #0 flow*s/ in both directions. 7or details, please refer to -900 T" );.)') and -900 T" );.)'(.

).1 'a/-Re4uested-and#idth-9+ The 5a$ >andwidthL A=0 *A=0 code @'?/ is of type nsigned-), and it indicates the ma$imum re
).2 'a/-Re4uested-and#idth-D+ The 5a$2eandwidth6L A=0 *A=0 code @'@/ is of type nsigned-), and it indicates the ma$imum bandwidth in bits per second for a downlink #0 flow. The bandwidth contains all the overhead coming from the #0layer and the layers above, e.g. #0, 60, 2T0 and 2T0 payload. 7or details, please refer to -900 T");.)') and -900 T" );.)'(. #ssue '.() *)+'(-)/


')



).3 Charging-Information The Charging#nformation A=0 *A=0 Code ?'B/ is of type 9rouped, and contains the addresses of the charging functions. A=0 format is depicted as followsE Charging#nformation EE R P A=0 Header E ?'B '+('@ Q  0rimary&ventCharging7unctionName I  "econdary&ventCharging7unctionName I  0rimaryChargingCollection7unctionName I  "econdaryChargingCollection7unctionName I U A=0I ). 0rimary&ventCharging7unctionName is of type 6iameter2# and defines the address of the primary online charging system. The protocol definition in the 6iameter2# shall be either omitted or supplied with value !6iameter!. )B. "econdary&ventCharging7unctionName is of type 6iameter2# and defines the address of the secondary online charging system for the bearer. The protocol definition in the 6iameter2# shall be either omitted or supplied with value !6iameter!. );. 0rimaryChargingCollection7unctionName is of type 6iameter2# and defines the address of the primary offline charging system for the bearer. #f the 9T0O protocol is applied on the 9G interface as specified in -900 T" -).);@ '?I, the protocol definition in the 6iameter2# shall be omitted. #f 6iameter is applied on the 9G interface, the protocol definition in 6iameter2# shall be either omitted or supplied with value !6iameter!. The choice of the applied protocol on the 9G interface depends upon configuration in the 0C&7. -+. "econdaryChargingCollection7unctionName is of type 6iameter2# and defines the address of the secondary offline charging system for the bearer. #f the 9T0O protocol is applied on the 9G interface as specified in -900 T" -).);@ '?I, the protocol definition in the 6iameter2# shall be omitted. #f 6iameter is applied on the 9G interface, the protocol definition in 6iameter2# shall be either omitted or supplied with value !6iameter!. The choice of the applied protocol on the 9G interface depends upon configuration in the 0C&7. 7or details, please refer to -900 T");.)') and -900 T" );.));.

). *ccess-8et#or<-Charging-Identifier-/ The AccessNetworkCharging#dentifier9$ A=0 *A=0 code '+))/ is of type 9rouped. #t contains a charging identifier *e.g. 9C#6/ within the AccessNetworkCharging#dentifier =alue A=0 and the related 0CC rule name*s/ within the Charging2uleName A=0*s/. The A=0 format is depicted as followsE AccessNetworkCharging#dentifier9$ EERP A=0 HeaderE '+)) Q S AccessNetworkCharging#dentifier=alue U Charging2ule>aseName I U Charging2uleName I

#ssue '.() *)+'(-)/


'-



#n this version, only 9C#6 will be reported to 0C27, i.e., neither Charging2uleName nor Charging2ule>aseName is reported to 0C27. 7or details, please refer to -900 T" );.)').

5a$imum length of AccessNetworkCharging#dentifier=alue is '? >ytes.

).$ eare r-Control-'ode The >earerControl5ode A=0 *A=0 code '+)-/ is of type of &numerated. hen sent from 0C&7 to 0C27, it indicates the & preferred bearer control mode. hen sent from 0C27 to 0C&7, it indicates the 0C27 selected bearer control mode. #f the >earerControl5ode A=0 has not been previously provided by the 0C&7, its absence shall indicate the value &43NLV. #f the >earerControl A=0 has been provided, its value shall remain valid until it is provided the ne$t time. The following values are definedE -'. &43NLV *+/ This value is used to indicate that the & shall re
).% earer-Identifier The >earer#dentifier A=0 *A=0 code '+)+/ is of type 3ctet"tring, and it indicates the bearer to which specific information refers. #t is selected solely by the 0C&7 and its encoding is transparent to the 0C27. hen present within a CC2e
5a$imum supported length is '? >ytes.

).& earer-"peration The >earer3peration A=0 *A=0 code '+)'/ is of type of &numerated, and it indicates the bearer event that causes a reL#"H5&NT *'/ #ssue '.() *)+'(-)/


'(



This value is used to indicate that a new bearer is being established. -?. 536#7#CAT#3N *)/ This value is used to indicate that an e$isting bearer is being modified. 7or details, please refer to -900 T" );.)').

).( earer-9sage The >earersage A=0 *A=0 code '+++/ is of type &numerated, and it shall indicate how the bearer is being used. #f the >earersage A=0 has not been previously provided, its absence shall indicate that no specific information is available. #f the >earersage A=0 has been provided, its value shall remain valid until it is provided the ne$t time. The following values are definedE -. 9&N&2AL *+/ This value shall indicate no specific bearer usage information is available. -B. #5"4"#9NALL#N9 *'/ This value shall indicate that the bearer is used for #5" signaling only. 7or details, please refer to -900 T" );.)').

).) Charging-Rule-Install The Charging2ule#nstall A=0 *A=0 code '++'/ is of type 9rouped, and it is used to activate, install or modify 0CC rules as instructed from the 0C27 to the 0C&7. 7or installing a new 0CC rule or modifying a 0CC rule already installed, Charging2ule6efinition A=0 shall be used. 7or activating a specific 0CC rule predefined at the 0C&7, Charging2ule Name A=0 shall be used as a reference for that 0CC rule. The Charging2ule>aseName A=0 is a reference that may be used for activating a group of 0CC rules predefined at the 0C&7. 7or 902" scenarios where the bearer binding is performed by the 0C27, the >earer #dentifier A=0 shall be included as part of Charging2ule#nstall A=0. #f present within Charging2ule #nstall A=0, the >earer#dentifier A=0 indicates that the 0CC rules within this Charging2ule #nstall A=0 shall be installed or activated within the #0 CAN bearer identified by the >earer #dentifier A=0. #f no >earer#dentifier A=0 is included within the Charging2ule#nstall A=0, the 0C&7 shall select an #0 CAN bearer for each of the 0CC rules within this Charging2ule #nstall A=0, were the 0CC rule is installed or activated. #f 2esourceAllocationNotification A=0 is included then it applies to all the rules within the Charging2ule#nstall A=0. #f a Charging2ule#nstall A=0 does not include the 2esource AllocationNotification A=0, the resource allocation shall not be notified by the 0C&7 even if this A=0 was present in previous installations of the same rule. A=0 7ormat is depicted as followsE Charging2ule#nstall EER P A=0 HeaderE '++' Q U Charging2ule6efinition I U Charging2uleName I U Charging2ule>aseName I #ssue '.() *)+'(-)/


'@



 >earer#dentifier I  2uleActivationTime I  2ule6eactivationTime I  2esourceAllocationNotification I  ChargingCorrelation#ndicator I  "N"ervice7low6etectionI U A=0 I 7or details, please refer to -900 T" );.)').

).$; Charging-Rule-Remove The Charging2ule2emove A=0 *A=0 code '++)/ is of type 9rouped, and it is used to deactivate or remove 0CC rules from an #0 CAN session. Charging2uleName A=0 is a reference for a specific 0CC rule at the 0C&7 to be removed or for a specific 0CC rule predefined at the 0C&7 to be deactivated. The Charging2ule>aseName A=0 is a reference for a group of 0CC rules predefined at the 0C&7 to be deactivated. A=0 7ormat is depicted as followsE Charging2ule2emove EER P A=0 HeaderE '++) Q U Charging2uleName I U Charging2ule>aseName I U A=0 I

hen 0C27 indicates to remove a rule not e$isting on 0C&7, the 0C&7 shall ignore the remove indication with no error occurs and reply success.

).$1 Charging-Rule-Definition The Charging2ule6efinition A=0 *A=0 code '++-/ is of type 9rouped, and it defines the 0CC rule for a service flow sent by the 0C27 to the 0C&7. The Charging2uleName A=0 uni

'?



 2ating9roup I U 7low6escription I U  7low#nformation I  T67Application#dentifier I  7low"tatus I  8o"#nformation I A7"ignalling0rotocolI  2eportingLevel I  3nline I  3ffline I  5etering5ethod I  0recedence I  A7Charging#dentifier I U 7lows I 2edirect"erverI 0rotoClassifierNameI :H5onitoringeyI 5onitoringeyI  2edirect#nformation I  5uteNotification I U:H"ubscriber"erviceNameI U9$T532edirect"erverI :H"erviceTypeI :H5"9roupNameI :HACL9roupNameI :H#nterim#ntervalI U2e
#ssue '.() *)+'(-)/


'





The :H5onitoringey A=0 is used for Huawei private usage monitoring and cannot be used with -900 5onitoringey simultaneously.



The 0rotoClassifierName A=0 is Huawei private e$tension used for dynamic layer rulesM definition.

).$2 Charging-Rule-ase-8ame The Charging2ule>aseName A=0 *A=0 code '++(/ is of type T7B"tring, and it indicates the name of a predefined group of 0CC rules residing at the 0C&7. 7or details, please refer to -900 T" );.)').

The ma$imum length of Charging2ule>aseName is )+ >ytes.

).$3 Charging-Rule-8ame The Charging2uleName A=0 *A=0 code '++@/ is of type 3ctet"tring, and it defines a name for 0CC rule. 7or 0CC rules provided by the 0C27 it uni
The ma$imum length of Charging2uleName is )+ >ytes.

).$ Charging-Rule-Report The Charging2ule2eport A=0 *A=0 code '+'B/ is of types 9rouped, and it is used to report the status of 0CC rules. Charging2uleName A=0 is a reference for a specific 0CC rule at the 0C&7 that has been successfully installed, modified or removed *for dynamic 0CC rules/, or activated or deactivated *for predefined 0CC rules/ because of trigger from the 5". Charging2ule>ase Name A=0 is a reference for a group of 0CC rules predefined at the 0C&7 that has been successfully activated or deactivated because of trigger from the 5". The Charging2ule2eport A=0 can also be used to report the status of the 0CC rules which cannot be installedactivated at the 0C&7. #n this condition, the Charging2uleName A=0 is used to indicate a specific 0CC rule which cannot be installedactivated, and the Charging 2ule>aseName A=0 is used to indicate a group of 0CC rules which cannot be activated. 5ultiple instances of Charging2ule2eport A=0s shall be used in the case it is re
#ssue '.() *)+'(-)/


'B



UCharging2uleNameI UCharging2ule>aseNameI 0CC2ule"tatusI 2ule7ailureCodeI 7inalnit#ndicationI UA=0I 7or details, please refer to -900 T" );.)').

).$$ vent-Trigger The &ventTrigger A=0 *A=0 code '++?/ is of type &numerated. hen sent from the 0C27 to the 0C&7 the &ventTrigger A=0 indicates an event that shall cause a rereearer#dentifier A=0 shall be provided to indicate the affected bearer. 8o"#nformation A=0 is reearer#dentifier A=0 shall be provided to indicate the affected bearer. The new T7T values shall be provided in T7T0acket7ilter#nformation A=0. (-. 0L5N4CHAN9& *(/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that upon a 0L5N change 0CC rules shall be re

';



0L5N. -900"9"N5CC5NC A=0 shall be provided in the same re&A2&2 *@/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that upon loss of bearer, 9 should inform 0C27. hen used in a CC2 command, this value indicates that the 0C&7 generated the reit 2ate *5>2/ in 8o" profile changed to + kbps. hen the 0C27 performs the bearer binding, the 0C&7 shall provide the >earer #dentifier A=0 to indicate the bearer that has been lost. (@. 2&C3=&2V4374>&A2&2 *?/ This value shall be in CCA and 2A2 commands by the 0C27 used to indicate that upon recovery of bearer, 9 should inform 0C27. hen used in a CC2 command, this value indicates that the 0C&7 generated the reit 2ate *5>2/ in 8o" profile changed from + kbps to a valid value. hen the 0C27 performs the bearer binding, the 0C&7 shall provide the >earer #dentifier A=0 to indicate the bearer that has been recovered. (?. #0CAN4CHAN9& */ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that upon acommand, change inthis the value #0CAN type 0CC shall generated be reearer#dentifier A=0 for the affected bearer and should provide the Charging2ule 2eport A=0 to indicate what 0CC rules are affected within that bearer. #n this case, absence of the Charging2ule2eport A=0 means that all provided 0CC rules for that specific bearer are affected. hen the 0C&7 performs the bearer binding, the 0C&7 should provide the Charging2ule2eport A=0 to indicate the 0CC rules that are affected. #n this case, absence of Charging2ule2eport A=0 means that all the 0CC rules for the corresponding #0CAN session are affected. (B. 2&"32C&"4L#5#TAT#3N *;/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that upon a failure to provide the reearer #ssue '.() *)+'(-)/


)+



#dentifier for the affected bearer. #n this case, absence of the Charging2ule2eport A=0 means that all provided 0CC rules for that specific bearer are affected. 3therwise, only the 0CC rules included in Charging2ule2eport A=0 are affected. (;. 5A:4N24>&A2&2"42&ACH&6 *'+/ This value shall be used in CCA and 2A2 commands by the 0C27 to subscribe to this event. #f the 0C27 subscribes to this event, the 0C&7 shall inform the 0C27 whenever a failure in the enforcement of 0CC rules occurs due to the ma$imum number of bearer have been reached for the #0CAN session, 0C&7 shall inform 0C27. hen used in a CC2 or 2AA command, this value indicates that the 0C&7 generated the reearer#dentifier A=0 shall be provided to indicate the affected bearer. 8o"#nformation A=0 is re
#ssue '.() *)+'(-)/


)'



This value shall be used in a CCA and 2A2 commands by the 0C27 when re
#ssue '.() *)+'(-)/


))



The 0C27 shall use this value in CCA and 2A2 commands to indicate that the 0C&7 shall report the access network charging identifier associated to one or more dynamic 0CC 2ules within the AccessNetworkCharging#dentifier9$ A=0. The Charging Correlation#ndicator A=0 with value CHA29#N94#6&NT#7#&242&8#2&6 shall be provided. hen used in a CC2 command, this value indicates that an access network charging identifier has been assigned. The actual value shall be reported with the AccessNetwork Charging#dentifier9$ A=0. Applicable to functionality introduced with the 2elB feature as described in clause @.(.'. ?). 2&6#2&CT#3N*'++/ This value shall be used in a CCA and 2A2 commands by the 0C27 when re&A2&2483"4CHAN9& *)+/ This value indicates that the 0C27 allows the 0C&7 to report the event, but the 0C27 does not process it. ?;. AN494CHAN9& *)'/ This value is used by the 0C27 to indicate that upon the change in the #0 address of the serving Access Node 9ateway *including the -900 "9 and non-900 A9/, 0CC rules are re
#ssue '.() *)+'(-)/


)-



-. ACC&""4N&T324#N7342&032T *(@/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that upon completion of an #0CAN bearer establishment, modification or termination procedure, or upon termination of the #0CAN session, and if the A7 re24536#7#CAT#3N47A#L2& *);, -900 );)'); +/ The 0C&7 shall use this value to indicate to the 0C27 that A0NA5>2 modifications have failed. The 0C&7 shall use this value in a new CC2 command that indicates the failure of either a 0"H initiated modification or a 0LL initiated modification. This event trigger needs no subscription. Applicable to functionality introduced with the 2elB feature as described in clause @.(.'. . 6&7ALT&0">&A2&283"4536#7#CAT#3N47A#L2& *-(/ The 0C&7 shall use this value to indicate to the 0C27 that 6efault &0" >earer 8o" modifications have failed. The 0C&7 shall use this value in a new CC2 command that indicates the failure of either a 0"H initiated modification or a 0LL initiated modification. This event trigger needs no subscription. Applicable to functionality introduced with the 2elB feature as described in clause @.(.'. B. 3T4374C2&6#T *'@/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that the 0C&7 shall inform the 0C27 about the 0CC rules for which credit is no longer available, together with the applied termination action. hen used in a CC2 command, this value indicates that the 0C&7 generated the re

)(



termination action indicated by the corresponding 7inalnit#ndication A=0 applies *-900 T" -).)(+ )'I and -900 T" -).);; ';I/. ;. 2&ALL3CAT#3N4374C2&6#T *'?/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that the 0C&7 shall inform the 0C27 about the 0CC rules for which credit has been reallocated after the former out of credit indication. hen used in a CC2 command, this value indicates that the 0C&7 generated the reN&T4CHAN9& *)+++/ This value shall be used in CCA and 2A2 commands by the 0C27 to indicate that the 0C&7 shall inform the 0C27 when "ubnet#dentifier is changed. The new "ubnet #dentifier value shall be provided in the CT&$tension A=0.

).$% I!-C*8-Type The #0CANType A=0 *A=0 code '+)/ is of type &numerated, and it shall indicate the type of Connectivity Access Network in which the user is connected. The #0CANType A=0 shall always be present during the #0CAN session establishment. 6uring an #0CAN session modification, this A=0 shall be present when there has been a change in the #0CAN type and the 0C27 re>LAN*'+@+/ This value shall be used to indicate that the #0CAN is associated with a LAN access. This value is used by 5&?+.

#ssue '.() *)+'(-)/


)@



).$%.1 uaranteed-itrate-D+ The 9uaranteed>itrate6L A=0 *A=0 code '+)@/ is of type nsigned-), and it indicates the guaranteed bitrate in bits per second for a downlink service data flow. The bandwidth contains all the overhead coming from the #0layer and the layers above, e.g. #0, 60, 2T0 and 2T0 payload. 7or details, please refer to -900 T" );.)').

).$%.2 uaranteed-itrate-9+ The 9uaranteed Y>itrateL A=0 *A=0 code '+)?/ is of type nsigned-), and it indicates the guaranteed bitrate in bits per second for an uplink service data flow. The bandwidth contains all the overhead coming from the #0layer and the layers above, e.g. #0, 60, 2T0 and 2T0 payload. 7or details, please refer to -900 T" );.)').

).$%.3 'etering-'ethod The 5etering5ethod A=0 *A=0 code '++/ is of type &numerated, and it defines what parameters shall be metered for offline charging. #f the 5etering5ethod A=0 is omitted but has been supplied previously, the previous information remains valid. #f the 5etering5ethod A=0 is omitted and hasasnot beenmetering supplied method. previously, the metering method preconfigured at the 0C&7 is applicable default The following values are definedE B;. 62AT#3N *+/ This value shall be used to indicate that the duration of the service flow shall be metered. ;+. =3L5& *'/ This value shall be used to indicate that volume of the service flow traffic shall be metered. ;'. 62AT#3N4=3L5& *)/ This value shall be used to indicate that the duration and the volume of the service flow traffic shall be metered. ;). N34CHA29#N9 *')B/ This value shall use to indicate that the service flow identified by this rule will not be charged. 7or details, please refer to -900 T" );.)').

).$& 8et#or<-Re4uest-upport The Network2e

)?



N&T3242&8&"T N3T "0032T&6. #f the Network 2e


#n this version, only J& 3nlyK bearer control mode is supported, and so 8o" per 8C# is not supported.



& initialed secondary 060 is not supported.

).$( "ffline The 3ffline A=0 *A=0 code '++B/ is of type &numerated. #f the 3ffline A=0 is embedded within a Charging2ule6efinition A=0 it defines whether the offline charging interface from the 0C&7 for the associated 0CC rule shall be enabled. The absence of this A=0 within the first provisioning of the Charging2uledefinition A=0 of a new 0CC rule indicates that the default charging method for offline shall be used. #f the 3ffline A=0 is embedded within the initial CC2 on command level, it indicates the default charging method for offline preconfigured at the 0C&7 is applicable as default charging method for offline. The absence of this A=0 within the initial CC2 indicates that the charging method for offline preconfigured at the 0C&7 is not available. #f the 3ffline A=0 is embedded within the initial CCA on command level, it indicates the default charging method for offline. The absence of this A=0 within the initial CCA indicates that the charging method for offline preconfigured at the 0C&7 is applicable as default charging method for offline. The default charging method provided by the 0C27 shall take precedence over any pre configured default charging method at the 0C&7. The following values are definedE ;@. 6#"A>L&4377L#N& *+/ This value shall be used to indicate that the offline charging interface for the associated 0CC rule shall be disabled. ;?. &NA>L&4377L#N& *'/ This value shall be used to indicate that the offline charging interface for the associated 0CC rule shall be enabled. 7or details, please refer to -900 T" );.)').

#ssue '.() *)+'(-)/


)



).$) "nline The 3nline A=0 *A=0 code '++;/ is of type &numerated. #f the 3nline A=0 is embedded within a Charging2ule6efinition A=0, it defines whether the online charging interface from the 0C&7 for the associated 0CC rule shall be enabled. The absence of this A=0 within the first provisioning of the Charging2ule6efinition A=0 of a new 0CC rule indicates that the default charging method for online shall be used. #f the 3nline A=0 is embedded within the initial CC2 on command level, it indicates the default charging method for online preconfigured at the 0C&7 is applicable as default charging method for online. The absence of this A=0 within the initial CC2 indicates that the charging method for online preconfigured at the 0C&7 is not available. #f the 3nline A=0 is embedded within the initial CCA on command level, it indicates the default charging method for online. The absence of this A=0 within the initial CCA indicates that the charging method for online preconfigured at the 0C&7 is applicable as default charging method for online. The default charging method provided by the 0C27 shall take precedence over any pre configured default charging method at the 0C&7. The following values are definedE ;. 6#"A>L&43NL#N& *+/ This value shall be used to indicate that the online charging interface for the associated 0CC rule shall be disabled. ;B. &NA>L&43NL#N& *'/ This value shall be used to indicate that the online charging interface for the associated 0CC rule shall be enabled. 7or details, please refer to -900 T" );.)').

).$).1 !recedence The 0recedence A=0 *A=0 code '+'+/ is of type nsigned-). ithin the Charging 2ule 6efinition A=0, the 0recedence A=0 determines the order, in which the service data flow templates are applied at service data flow detection at the 0C&7. A 0CC rule with the 0recedence A=0 with lower value shall be applied before a 0CC rule with the 0recedence A=0 with higher value. The 0recedence A=0 is also used within the T7T0acket7ilter#nformation A=0 to indicate the evaluation precedence of the Traffic 5apping #nformation filters *for 902" the T7T packet filters/ as received from the &. 7or details, please refer to -900 T" );.)').

).$).2 Reporting-+evel The 2eportingLevel A=0 *A=0 code '+''/ is of type &numerated, and it defines on what level the 0C&7 reports the usage for the related 0CC rule. #f the 2eportingLevel A=0 is omitted but has been supplied previously, the previous information remains valid. #f the

#ssue '.() *)+'(-)/


)B



2eportingLevel A=0 is omitted and has not been supplied previously, the reporting level pre configured at the 0C&7 is applicable as default reporting level. The following values are definedE ;;. "&2=#C&4#6&NT#7#&24L&=&L *+/ This value shall be used to indicate that the usage shall be reported on service id and rating group combination level. '++. 2AT#N9492304L&=&L *'/ This value shall be used to indicate that the usage shall be reported on rating group level. 7or details, please refer to -900 T" );.)').

).%; !CC-Rule-tatus The 0CC2ule"tatus A=0 *A=0 code '+';/ is of type &numerated, and describes the status of one or a group of 0CC 2ules. The following values are definedE '+'. ACT#=& *+/ This value is used to indicate that the 0CC rule*s/ are installed successfully *for those provisioned from 0C27/ or activated *for those preprovisioned in 0C&7/ '+). #NACT#=& *'/ This value is used to indicate that the 0CC rule*s/ are removed *for those provisioned from 0C27/ or inactive *for those preprovisioned in 0C&7/ '+-. T&5032A2V #NACT#=& *)/ This value is used to indicate that, for some reason *e.g. loss of bearer/, already installed or activated 0CC rules are temporary disabled. 7or details, please refer to -900 T" );.)').

).%1 0o-Class-Identifier 8o"Class#dentifier A=0 *A=0 code '+)B/ is of type &numerated, and it identifies a set of #0CAN specific 8o" parameters that define the authoriGed 8o", e$cluding the applicable bitrates for the #0CAN bearer or service flow. #t is only applicable to network initiated 8o" control procedures. 7or details, please refer to -900 T" );.)').

#ssue '.() *)+'(-)/


);









).%2 0o-Information The 8o"#nformation A=0 *A=0 code '+'?/ is of type 9rouped, and it defines the 8o" information for an #0CAN bearer, 0CC rule or 8C#. hen this A=0 is sent from the 0C&7 to the 0C27, it indicates the reandwidthL A=0 andor the 5a$imum2eandwidth6L A=0/. The >earer #dentifier A=0 shall be included as part of the 8o"#nformation A=0 if the 8o" information refers to an #0 CAN bearer initiated by the & and the 0C27 performs the bearer binding. The >earer #dentifier A=0 identifies this bearer. "everal 8o"#nformation A=0s for different >earer #dentifiers may be provided per command. The Allocation2etention0riority A=0 is an indicator of the priority of allocation and retention for the "ervice 6ata 7low. #f the 8o"#nformation A=0 has been supplied previously but is omitted in a 6iameter message or A=0, the previous information remains valid. #f the 8o"#nformation A=0 has not been supplied from the 0C27 to the 0C&7 previously and is omitted in a 6iameter message or A=0, no enforcement of the authoriGed 8o" shall be performed. A=0 7ormat is depicted as followsE 8o"#nformation EER P A=0 HeaderE '+'? Q  8o"Class#dentifier I  5a$2eandwidthL I  5a$2eandwidth6L I  9uaranteed>itrateL I  9uaranteed>itrate6L I  A0NAggregate5a$>itrateLI  A0NAggregate5a$>itrate6LI  >earer#dentifier I  Allocation2etention0riorityI

#ssue '.() *)+'(-)/


-+











A0NAggregate5a$>itrateL and A0NAggregate5a$>itrate6L may e$ist only when the 8o"#nformation is included within the CCA2A2.

7or details, please refer to -900 T" );.)').

).%3 0o-8egotiation The 8o"Negotiation A=0 *A=0 code '+);/ is of type &numerated. The value of the A=0 indicates for a single 0CC rule re
N348o"4N&93T#AT#3N *+/ This value indicates that a 8o" negotiation is not allowed for the corresponding 0CC rule re


8o"4N&93T#AT#3N4"0032T&6 *'/ This value indicates that a 8o" negotiation is allowed for the corresponding 0CC rule re

).% 0o-9pgrade The 8o"pgrade A=0 *A=0 code '+-+/ is of type &numerated. The value of the A=0 indicates whether the "9"N supports that the 99"N upgrades the 8o" in a Create 060 conte$t response or pdate 060 conte$t response. #f the "9"N does not support a 8o" upgrade, the 0C27 shall not provision an authoriGed 8o" which is higher than the reearer#dentifier A=0. #f no 8o"pgrade A=0 has been supplied for an #0 CAN bearer, the default value 8o"4092A6&4N3T4"0032T&6 is applicable. #f the 8o"pgrade A=0 has previously been supplied for an #0 CAN bearer but is not supplied in a new 0CC rule re
8o"4092A6&4N3T4"0032T&6 *+/ This value indicates that the #0CAN bearer does not support the upgrading of the re


8o"4092A6&4"0032T&6 *'/ This value indicates that the #0CAN bearer supports the upgrading of the re

#ssue '.() *)+'(-)/


-'



).%$ TT-ilter The T7T7ilter A=0 *A=0 code '+')/ is of type #07ilter2ule, and it contains the flow filter for one T7T packet filter. The T7T7ilter A=0 is derived from the Traffic 7low Template *T7T/ defined in -900 T" )(.++B '-I. The following information shall be sentE 

 Action shall be set to !permit!.



 6irection shall be set to !out! or !in!.



 0rotocol shall be set to the value provided within the T7T packet filter parameter !0rotocol #dentifierNe$t Header Type!. #f the T7T packet filter parameter !0rotocol #dentifierNe$t Header Type! is not provided within the T7T packet filter, 0rotocol shall be set to !ip!.



 "ource #0 address *possibly masked/. The source #0 address shall be derived from T7T packet filter parameters !"ource address! and !"ubnet 5ask!. The source #0 address shall be set to !any!, if no such information is provided in the T7T packet filter.



 "ource and destination port *single value, list or ranges/. The information shall be derived from the corresponding T7T packet filter parameters. "ource andor destination port*s/ shall be omitted if such information is not provided in the T7T packet filter.



 The 6estination #0 address shall be set to !assigned!.


 No options shall be used.



 The invert modifier !X! for addresses shall not be used.

The direction !out! refers to downlink direction. 7or details, please refer to -900 T" );.)').

).%% TT-!ac
#ssue '.() *)+'(-)/


-)



).%& To-Traffic-Class The To"TrafficClass A=0 *A=0 code '+'(/ is of type 3ctet"tring, and it contains the Type of"erviceTrafficClass of a T7T packet filter as defined in -900 T" )(.++B '-I. 7or details, please refer to -900 T" );.)').

).%( =-:7-9sage-Report The :Hsage2eport A=0 *A=0 code )++@/ is of type 9rouped. hen sent from 0C27 to 99"N, it indicates that usage information for specified services andor the whole #0CAN session should be reported, and contains corresponding thresholds for reporting. hen sent from 99"N to 0C27, it contains the detailed usage information accumulated from the time point of last report to the time point of current report. 0lease be noted that usage report for each services andor #0CAN session is independent of each other, and local counters for usage accumulating are cleared immediately once reporting message is sent out. A=0 7ormat is depicted as followsE :Hsage2eport EER P A=0CodeEER )++@, =endor#dEER)+''Q :H"essionsageI U :H"ervicesageI

5a$imum :H"ervicesage number of :Hsage2eport is '+.

).%) =-:7-ession-9sage The :H"essionsage A=0 *A=0 code )++?/ is of type 9rouped. hen sent from 0C27 to 99"N, it indicates that usage information for the whole #0CAN session should be reported, and contains corresponding threshold for reporting. hen sent from 99"N to 0C27, it contains the detailed usage information of the whole #0CAN session accumulated from the time point of last report to the time point of current report. A=0 7ormat is depicted as followsE :H"essionsage ERP A=0CodeEER )++?, =endor#dEER)+''Q CC#nput3ctetsI CC3utput3ctetsI

).&; =-:7-ervice-9sage The :H"ervicesage A=0 *A=0 code )++/ is of type 9rouped. hen sent from 0C27 to 99"N, it indicates that usage information for specified service should be reported, and contains corresponding threshold for reporting. hen sent from 99"N to 0C27, it contains the detailed usage information of specified service accumulated from the time point of last report to the time point of current report. 7or which service to report, it is specified by the

#ssue '.() *)+'(-)/


--



combination of 2ating9roup and "ervice#dentifier. "ervice#dentifier is optional, and when used, it should be aligned with the reporting level of #0CAN session. A=0 7ormat is depicted as followsE :H"ervicesage ERP A=0CodeEER )++, =endor#dEER)+'' Q 2ating9roupI "ervice#dentifierI CC#nput3ctetsI CC3utput3ctetsI

#n release =-++2++)C+)C+-, the 2ating9roup and "ervice#dentifier are correlated to these in the Charging2ule6efinition to combine the usage and service flows. >ut from release =-++2++)C+@, the 2ating9roup A=0 here is mapped into the monitoring key defined in 0CC rule, and the "ervice #dentifier A=0 here is abolished, and so from now on it can work independently with the charging interfaces.

).&1 CC-Input-"ctets The CC#nput3ctets A=0 *A=0 Code (')/ is of type nsigned?( and contains the number of re
).&2 CC-"utput-"ctets The CC3utput3ctets A=0 *A=0 Code ('(/ is of type nsigned?( and contains the number of re
).&3 Redirect-erver The 2edirect"erver A=0 *A=0 Code (-(/ is of type 9rouped and contains the address information of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be connected when the account cannot cover the service cost. #t is defined as follows *per the groupedavpdef of 27C -@BB 6#A5>A"&I/E 2edirect"erver EER P A=0 HeaderE (-( Q S 2edirectAddressType  S 2edirect"erverAddress  Append3riginal2LI 6eactivate>y2edirectI  oneshot redirection :H2edirectTimesI :H2edirect2eportI

#ssue '.() *)+'(-)/


-(



=endor#d is -900.

).& Redirect-*ddress-Type The 2edirectAddressType A=0 *A=0 Code (--/ is of type &numerated and defines the address type of the address given in the 2edirect"erverAddress A=0. The address type can be one of the followingE #0v( Address

+

The address type is in the form of !dotteddecimal! #0v( address, as defined in #0v(I. #0v? Address

'

The address type is in the form of #0v? address, as defined in #0v?AddrI. The address is a te$t representation of the address in either the preferred or alternate te$t form #0v?AddrI. Conformant implementations 5"T support the preferred form and "H3L6 support the alternate te$t form for #0v? addresses.  2L

)

The address type is in the form of niform 2esource Locator, as defined in 2LI. " #02#

-

The address type is in the form of "#0 niform 2esource #dentifier, as defined in "#0I.


).&$ Redirect-erver-*ddress The 2edirect"erverAddress A=0 *A=0 Code (-@/ is of type T7B"tring and defines the address of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be connected when the account cannot cover the service cost.


).&% *ppend-"riginal-9R+ The Append3riginal2L A=0 *A=0 CodeEER''( =endor#dEER)+''/ is of type &numerated and defines that the srcinal 2L of the HTT0 get shall be included as a C9# parameter to the redirection 2L. The srcinal 2L in the redirection 2L should be sent via a C9# parameter separated with
+ *default/  do not append the srcinal 2L Huawei 0roprietary and Confidential Copyright 1 Huawei Technologies Co., Ltd

-@


enable


'  append the srcinal 2L

).&& Deactivate-y-Redirect The 6eactivate>y2edirect A=0 *A=0 CodeEER''@ =endor#dEER)+''/ is of type &numerated and defines that the redirection rule shall be disabled immediately when the 0C&7 detects a HTT0 9et with the redirection 2L in the redirection flow. *3ne"hot2edirection/ The A=0 can be set to one of the following valuesE disable

+ *default/  the rule is not deactivated once enforced

enable

'  the rule is deactivated once enforced

).&( =-:7-'onitoring->ey The :H5onitoringey A=0 is of type nsigned-) *A=0 CodeEER)++B, =endor #dEER)+''/ and contains the monitoring key for usage reporting. The value range is from +$++++++++ to +$77777777. #f it has not been previously provided in 0CC rules, its absence shall indicate that the corresponding service is not sub%ect to usage reporting. #f it has been provided, its value shall remain valid until it is provided the ne$t time.

7or these 5onitoringey predefined on 0C&7 *e.g. contains within predefined rule or predefined rule group/ shall be within range of +$+, +$7777776I, i.e. +, )'((B-?(@I.

).&) !roto-Classifier-8ame The 0rotoClassifierName *A=0CodeEER )+@', =endor#dEER)+''/ is type of T7B string, define the name of a protocol classifier or name of group of protocol classifiers predefined on the 0C&7s. 7or e$ample, it could be Jp)pK to indicate all 0)0 stream or J"kypeK for special application.

This A=0 has mutually e$clusive relation with the 7low6escription, i.e. they cannot be occurring in one Charging2ule6efinition.

).(; 9sage-'onitoring-Information The sage5onitoring#nformation A=0 *A=0 code '+?/ is of type 9rouped, and it contains the usage monitoring control information. The 5onitoringey A=0 identifies the usage monitoring control instance. The 9ranted"ervicenit A=0 shall be used by the 0C27 to provide the threshold level to the 0C&7. The CCTotal3ctets A=0 shall be used for providing threshold level for the total volume, or the CC#nput3ctets andor CC3utput3ctets A=0s shall be used for providing threshold level for the uplink volume andor the downlink volume.

#ssue '.() *)+'(-)/


-?



The sed"ervicenit A=0 shall be used by the 0C&7 to provide the measured usage to the 0C27. 2eporting shall be done, as re [ '(nit(ring-0e1 ] [ ranted-Ser3i4e-&nit ] [ &sed-Ser3i4e-&nit ] [ &sage-'(nit(ri ng-e3e6 ] [ &sage-'(nit(ring-Re7(rt ] [ &sage-'(nit(ring-Su77(rt ] 8[ A+$ ]

5a$imum sage5onitoring#nformation number of CC2CCA2A2 message is '+.

).(1 9sage-'onitoring-+evel The sage5onitoringLevel A=0 *A=0 code '+?B/ is of type &numerated and is used by the 0C27 to indicate whether the usage monitoring instance applies to the #0CAN session or to one or more 0CC rules. #f sage5onitoringLevel A=0 is not provided, its absence shall indicate the value 0CC42L&4L&=&L *'/. The following values are definedE 

"&""#3N4L&=&L *+/ This value, if provided within an 2A2 or CCA command by the 0C27 indicates that the usage monitoring instance applies to the entire #0CAN session.



0CC42L&4L&=&L *'/ This value, if provided within an 2A2 or CCA command by the 0C27 indicates that the usage monitoring instance applies to one or more 0CC rules.

).(2 9sage-'onitoring-Report The sage5onitoring2eport A=0 *A=0 code '+?;/ is of type &numerated and is used by the 0C27 to indicate that accumulated usage is to be reported by the 0C&7 regardless of whether a usage threshold is reached for certain usage monitoring key *within a sage 5onitoring#nformation A=0/ . The following values are definedE "A9&453N#T32#N942&032T42&8#2&6 *+/

#ssue '.() *)+'(-)/


-



This value, if provided within an 2A2 or CCA command by the 0C27 indicates that accumulated usage shall be reported by the 0C&7.

).(3 9sage-'onitoring-upport The sage5onitoring"upport A=0 *A=0 code '++/ is of type &numerated and is used by the 0C27 to indicate whether usage monitoring shall be disabled for certain 5onitoring ey. The following values are definedE "A9&453N#T32#N946#"A>L&6 *+/ This value indicates that usage monitoring is disabled for a monitoring key. The 0C27 may send an CCA2A2 with to disable usage monitoring for a monitoring key, with the sage5onitoring#nformation A=0 including the applicable monitoring key within the 5onitoringey A=0 and the sage5onitoring"upport A=0 set to "A9&453N#T32#N946#"A>L&6. hen the 0C27 disables usage monitoring in a 2A2 or CCA command, the 0C&7 shall send a new CC2 command to report accumulated usage for the disabled usage monitoring key*s/.

hen 0C&7 received a 2A2CCA which indicate to disable usage monitoring instances not e$isting, the 0C&7 shall ignore the disable indication with no error occurs and reply success.

).( 'onitoring->ey

The 5onitoringey A=0 *A=0 code '+??/ is of type 3ctet"tring and is used for usage monitoring control purposes as an identifier to a usage monitoring control instance.



The 5onitoringey in Huawei 0CC is treated as nsigned #nteger.



7or these 5onitoringey predefined on 0C&7 *e.g. contains within predefined rule or predefined rule group/ shall be within range of +$+, +$7777776I, i.e. +, )'((B-?(@I.

).($ CC-Total-"ctets The CCTotal3ctets A=0 *A=0 Code ()'/ is of type nsigned?( and contains the total number of re
).(% ranted-ervice-9nit 9ranted"ervicenit A=0 *A=0 Code (-'/ is of type 9rouped and contains the amount of units that the 6iameter creditcontrol client can provide to the end user until the service must be released or the new CreditControl2eA64AN"&2. #ssue '.() *)+'(-)/


-B



The 9ranted"ervicenit A=0 is defined as follows *per the groupedavpdef of 27C -@BB 6#A5>A"&I/E 9ranted"ervicenit EER P A=0 HeaderE (-' Q  TariffTimeChange I  CCTime I  CC5oney I  CCTotal3ctets I  CC#nput3ctets I  CC3utput3ctets I  CC"ervice"pecificnits I U A=0 I



The CCTotal3ctets is used by the 0C27 to indicate total granted volume *i.e. #nput [ 3utput/.



The CCTime is used by the 0C27 to indicate total granted duration *i.e. #nput [ 3utput/.



TariffTimeChange, CC5oney, CC#nput3ctets, CC3utput3ctets, and CC"ervice"pecific nits are not used now.



UA=0I is not supported.

).(& 9sed-ervice-9nit The sed"ervicenit A=0 is of type 9rouped *A=0 Code ((?/ and contains the amount of used units measured from the point when the service became active or, if interim interrogations are used during the session, from the point when the previous measurement ended. The sed"ervicenit A=0 is defined as follows *per the groupedavpdef of 27C -@BB 6#A5>A"&I/E sed"ervicenit EER P A=0 HeaderE ((? Q  TariffChangesage I  CCTime I  CC5oney I  CCTotal3ctets I  CC#nput3ctets I  CC3utput3ctets I  CC"ervice"pecificnits I U A=0 I

#ssue '.() *)+'(-)/


-;





The CCTotal3ctets shall be used by the 0C&7 to indicate total used volume *i.e. #nput [ 3utput/.



The CCTime shall be used by the 0C&7 to indicate total used duration *i.e. #nput [ 3utput/.



TariffTimeChange, CC5oney, CC#nput3ctets, CC3utput3ctets, and CC"ervice"pecific nits are not used now.

).(( Revalidation-Time The 2evalidationTime A=0 *A=0 code '+()/ is of type Time. This value indicates the NT0 time before which the 0C&7 will have to rere
).() ession-Release-Cause The "ession2eleaseCause A=0 *A=0 code '+(@/ is of type &numerated, and determines the cause of release the #0CAN session by the 0C27. The following values are definedE 

N"0&C#7#&642&A"3N *+/ This value is used for unspecified reasons.



&4">"C2#0T#3N42&A"3N *'/ This value is used to indicate that the subscription of & has changed *e.g. removed/ and the session needs to be terminated.



#N"77#C#&NT4"&2=&242&"32C&" *)/ This value is used to indicate that the server is overloaded and needs to abort the session.

).); R*T-Type The 2ATType A=0 *A=0 code '+-)/ is of type &numerated and is used to identify the radio access technology that is serving the &.



=alues +;;; are used for generic radio access technologies that can apply to different #0CAN types and are not #0CAN specific.



=alues '+++';;; are used for -900 specific radio access technology types.



=alues )+++);;; are used for -900) specific radio access technology types.



The informative Anne$ C presents a mapping between the code values for different access network types.

The following values are definedE 

LAN *+/ This value shall be used to indicate that the 2AT is LAN.



T2AN *'+++/ This value shall be used to indicate that the 2AT is T2AN. 7or further details refer to -900 T" );.+?+ 'BI.



#ssue '.() *)+'(-)/

9&2AN *'++'/


(+



This value shall be used to indicate that the 2AT is 9&2AN. 7or further details refer to -900 T" );.+?+ 'BI. 

9AN *'++)/ This value shall be used to indicate that the 2AT is 9AN. 7or further details refer to -900 T" );.+?+ 'BI and -900 T" (-.-'B );I.



H"0A4&=3LT#3N *'++-/ This value shall be used to indicate that the 2AT is H"0A &volution. 7or further details refer to -900 T" );.+?+ 'BI.



&T2AN *'++(/ This value shall be used to indicate that the 2AT is &T2AN. 7or further details refer to -900 T" );.)( ))I



C65A)+++4': *)+++/ This value shall be used to indicate that the 2AT is C65A)+++ ':. 7or further details refer to -900) :."++''6 )+I.



H206 *)++'/ This value shall be used to indicate that the 2AT is H206. 7or further details refer to -900) :."++''6 )+I.



5> *)++)/ This value shall be used to indicate that the 2AT is 5>. 7or further details refer to -900) :."++''6 )+I.



&H206 *)++-/ This value shall be used to indicate that the 2AT is eH206. 7or further details refer to -900) :.0++@ )(I.

).)1 Default-!-earer-0o The 6efault&0">earer8o" A=0 *A=0 code '+(;/ is of type 9rouped, and it defines the 8o" information for the &0" default bearer. hen this A=0 is sent from the 0C&7 to the 0C27, it indicates the subscribed 8o" for the default &0" bearer. hen this A=0 is sent from the 0C27 to the 0C&7, it indicates the authoriGed 8o" for the default &0" bearer. 6efault&0">earer8o"EER P A=0 HeaderE '+(; Q  8o"Class#dentifier I  Allocation2etention0riorityI U A=0I

).)2 *llocation-Retention-!riority *V! The Allocation2etention0riority A=0 *A=0 code '+-(/ is of type 9rouped, and it is used to indicate the priority of allocation and retention, the preemption capability and preemption vulnerability for the "67 if provided within the 8o"#nformationA=0 or for the &0" default bearer if provided within the 6efault&0">earer8o" A=0. Allocation2etention0riority EER P A=0 HeaderE '+-( Q S0riorityLevel #ssue '.() *)+'(-)/


('



0reemptionCapabilityI 0reemption=ulnerabilityI

).)3 !riority-+evel *V! 5*ll access types6 The 0riorityLevel A=0 *A=0 code '+(?/ is of type nsigned -). The A=0 is used for deciding whether a bearer establishment or modification re2 traffic/. The A=0 can also be used to decide which e$isting bearers to preempt during resource limitations. The priority level defines the relative importance of a resource re
).) !re-emption-Capa,ility The 0reemptionCapability A=0 *A=0 code '+(/ is of type &numerated. The A=0 defines whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level. The following values are definedE 

02&&50T#3N4CA0A>#L#TV4&NA>L&6 *+/ This value indicates that the service data flow is allowed to get resources that were already assigned to another service data flow with a lower priority level.



02&&50T#3N4CA0A>#L#TV46#"A>L&6 *'/ This value indicates that the service data flow is not allowed to get resources that were already assigned to another service data flow with a lower priority level. This is the default value applicable if this A=0 is not supplied.

).)$ !re-emption-Vulnera,ility The 0reemption =ulnerability A=0 *A=0 code '+(B/ is of type &numerated. The A=0 defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow with higher priority level. The following values are definedE 

02&&50T#3N4=LN&2A>#L#TV4&NA>L&6 *+/ This value indicates that the resources assigned to the service data flow can be pre empted and allocated to a service data flow with a higher priority level. This is the default value applicable if this A=0 is not supplied.



02&&50T#3N4=LN&2A>#L#TV46#"A>L&6 *'/ This value indicates that the resources assigned to the service data flow shall not be pre empted and allocated to a service data flow with a higher priority level.

#ssue '.() *)+'(-)/


()



).)% *!8-*ggregate-'a/-itrate-D+ The A0NAggregated5a$>itrate6L A=0 *A=0 code '+(+/ is of type nsigned-), and it indicates the ma$imum aggregate bit rate in bits per seconds for the downlink direction across all non9>2 bearers related with the same A0N. hen provided in a CC2e
).)& *!8-*ggregate-'a/-itrate-9+ The A0NAggregated5a$>itrateL A=0 *A=0 code '+('/ is of type nsigned-), and it indicates the ma$imum aggregate bit rate in bits per seconds for the uplink direction across all non9>2 bearers related with the same A0N. hen provided in a CC2e
).)( *8-7-*ddress *V! The AN9Address A=0 *A=0 code '+@+/ is of type Address, and it contains the #0v( and or #0v? *if available/ address*es/ of the access node gateway *"9 for -900 and A9 for non-900 networks/.

3nly one AN9Address A=0 can be provided in the CC2 message.

).)) upported-eatures *V! The "upported7eatures A=0 is of type 9rouped. #f this A=0 is present it may inform the destination host about the features that the srcin host supports. The 7eatureList A=0 contains a list of supported features of the srcin host. The =endor#d A=0 and the 7eature List A=0 shall together identify which feature list is carried in the "upported7eatures A=0. here a "upported7eatures A=0 is used to identify features that have been defined by -900, the =endor#d A=0 shall contain the vendor #6 of -900. =endors may define proprietary features, but it is strongly recommended that the possibility is used only as the last resort. here the "upported7eatures A=0 is used to identify features that have been defined by a vendor other than -900, it shall contain the vendor #6 of the specific vendor in
#ssue '.() *)+'(-)/


(-



S 7eatureList  UA=0I

).1;; eature-+ist-ID *V! The 7eatureList#6 A=0 is of type nsigned-) and it contains the identity of a feature list.

).1;1 eature-+ist *V! The 7eatureList A=0 is of type nsigned-) and it contains a bit mask indicating the supported features of an application. hen the bit set, indicates the corresponding feature is supported by the application. Table '.' defines the features applicable to the 9$ interfaces for the feature list with a 7eatureList#6 of '. &a2"e 1.17eatures of 7eatureList#6 ' used in 9$

eature ,it

eature

'?"

Description

+

2elB

5

This feature is applicable for the CC2CCA command pair and indicates that the srcin host re
7eature bitE The order number of the bit within the 7eatureList A=0 where the least significant bit is assigned number J+K. 7eatureE A short name that can be used to refer to the bit and to the feature, e.g. !&0"!. 53E 6efines if the implementation of the feature is mandatory *!5!/ or optional *!3!/. 6escriptionE A clear te$tual description of the feature.

).1;2 Rule-*ctivation-Time The 2uleActivationTime A=0 *A=0 code '+(-/ is of type Time. This value indicates the NT0 time at which the 0CC rule has to be enforced. The A=0 is included in Charging2ule #nstall A=0 and is applicable for all the 0CC rules included within the Charging2ule#nstall A=0

).1;3 Rule-Deactivation-Time The 2ule6eactivationTime A=0 *A=0 code '+((/ is of type Time. This value indicates the NT0 time at which the 0C&7 has to stop enforcing the 0CC rule. The A=0 is included in Charging2ule#nstall A=0 and is applicable for all the 0CC rules included within the Charging2ule#nstall A=0 #ssue '.() *)+'(-)/


((



).1; =-:7-u,scri,er-ervice-Definition The :H"ubscriber"ervice6efinition A=0 *A=0 code )++;/ is of type 9rouped. #t defines the service of the subscriber. A=0 7ormat is depicted as followsE :H"ubscriber"ervice6efinition EER P A=0CodeEER )++;, =endor#dEER)+''Q S:H"ubscriber"erviceName :H"ubscriber"ervicesernameI  :H"ubscriber"ervice0asswordI



5a$imum :H"ubscriber"ervice6efinition number in CCA2A2 is '+.



#tMs used for H specific scenarios which can support multiple serviceA0N.

).1;$ =-:7-u,scri,er-ervice-8ame The :H"ubscriber"erviceName A=0 *A=0 Code )+'+/ is of type T7B"tring, which contains the service name. The :H"erviceName 5"T N3T be longer than ?- bytes in length.

).1;% =-:7-u,scri ,er-ervice-9sername The :H"ubscriber"ervicesername A=0 *A=0 Code )+''/ is of type T7B"tring, which contains the username for the service. The :H"ervice sername 5"T N3T be longer than ?- bytes in length.

).1;& =-:7-u,scri,er-ervice-!ass#ord The :H"ubscriber"ervice0assword A=0 *A=0 Code )+')/ is of type 3ctet"tring and contains the password of the user for the service to be authenticated. The :H"ubscriber"ervice0assword A=0 contains a user password and therefore represents sensitive information. The :H"ubscriber"ervice0assword 5"T N3T be longer than ?- bytes in length.

).1;( lo#-Information 5*ll access types6 The 7low#nformation A=0 *A=0 code '+@B/ is of type 9rouped, and it is sent from the 0C27 to the 0C&7 and contains the information from a single #0 flow packet filter. The 7low#nformation A=0 shall include the 7low6irection A=0, declaring in what direction*s/ the filter applies.

#ssue '.() *)+'(-)/


(@



7or 0CC rules created as a result of &initiated resource allocation, the 0C27 shall assign and include the packet filter identifier in the 0acket7ilter#dentifier A=0. The 7low#nformation A=0 may also include the Typeof"erviceTraffic Class, the #0"ec "0#, and the 7low Label. The values of these A=0s are obtained from the packet filter information provided by the 0C&7. The 7low6irection A=0 shall be included unless no other A=0s other than 0acket7ilter #dentifier A=0 are included within the 7low#nformation A=0. A=0 7ormatE 7low#nformation EER P A=0 HeaderE '+@B Q  7low6escription I  0acket7ilter#dentifier I  0acket7iltersage I  To"TrafficClass I  "ecurity0arameter#nde$ I  7lowLabel I  7low6irection I U A=0 I

).1;) !ac
The 0acket7ilterContent A=0 *A=0 code '+@;/ is of type #07ilter2ule, and it contains the content of the packet filter as re
Action shall be set to !permit!.



6irection shall be set to !out!.



0rotocol shall be set to the value provided within the packet filter provided by the &. #f not provided, 0rotocol shall be set to !ip!.



"ource #0 address *possibly masked/. The "ource #0 address shall be derived from the packet filter parameters, for the remote end, sent by the &. #f the "ource #0 address is not provided by the &, this field shall be set to !any!.



"ource andor destination port *single value, list or ranges/. The information shall be derived from the remote andor local port packet filter parameters. "ource andor destination port*s/ shall be omitted if the corresponding information is not provided in the packet filter.



6estination #0 address *possibly masked/. The 6estination #0 address shall be derived from the packet filter parameters sent by the &. The 6estination shall be set to the value provided by the & or !assigned!, to refer to the #0v( address andor #0v? prefi$ of the & as indicated by the 7ramed#0Address andor 7ramed#0v?0refi$ A=0s.


No options shall be used.




#ssue '.() *)+'(-)/


(?



The direction !out! indicates that the #07ilter2ule !source! parameters correspond to the !remote! parameters in the packet filter and the #07ilter2ule !destination! parameters correspond to the !local! *& end/ parameters. The 0acket7ilterContent A=0 applies in the direction*s/ as specified in the accompanying 7low6irection A=0

).11; !ac
).111 !ac.-.( for &T2AN specific details. A=0 7ormatE 0acket7ilter#nformation EER P A=0 HeaderE '+?' Q  0acket7ilter#dentifier I  0recedence I  0acket7ilterContent I  To"TrafficClass I  "ecurity0arameter#nde$ I  7lowLabel I  7low6irection I U A=0 I

).112 !ac
#ssue '.() *)+'(-)/


(




6&L&T#3N *+/ This value is used to indicate that the resources reserved for the provided packet filter identifiers are to be deleted and are no longer used by the &.



A66#T#3N *'/ This value is used to indicate that the & re


536#7#CAT#3N *)/ This value is used to indicate that the reserved 8o", the filter, the precedence, or any of the fields for the provided packet filter identifiers are being modified.

).113 Charging-Correlation-Indicator 5*ll access types6 The ChargingCorrelation#ndicator A=0 *A=0 code '+-/ is of type &numerated. #f the ChargingCorrelation#ndicator A=0 is included within a Charging2ule#nstall A=0 it indicates that the AccessNetworkCharging#dentifier9$ A=0 assigned to the dynamic 0CC rules need to be provided. The following values are definedE CHA29#N94#6&NT#7#&242&8#2&6 *+/ This value shall be used to indicate that the AccessNetworkCharging#dentifier9$ A=0 for the dynamic 0CC rule*s/ shall be reported to the 0C27 by the 0C&7.

).11 3!!-'-Time@one -9005"TimeDone A=0 *A=0 code )-/ indicates the offset between universal time and local time in steps of '@ minutes of where the 5" currently resides. 7or details, please refer to -900 T" );.+?' and -900 T" )-.++-.

).11$ CC-Time The CCTime A=0 *A=0 Code ()+/ is of type nsigned-) and indicates the length of the re
).11% 9ser-4uipment-Info The ser&A"&I/E ser&

(B



S ser&
).11& 9ser-4uipment-Info-Type The ser&
+

The identifier contains the #nternational 5obile &
' The (Bbit 5AC address is formatted as described in 2A6B+).':I.

&#?(

) The ?(bit identifier used to identify hardware instance of the product, as defined in &#?(I.

536#7#&64&#?(

-

There are a number of types of terminals that have identifiers other than #5&#, #&&& B+) 5ACs, or &#?(. These identifiers can be converted to modified &#?( format as described in #0v?AddrI or by using some other methods referred to in the servicespecific documentation.

).11( 9ser-4uipment-Info-Value The ser&
).11) =-:7-Cell-Congestion-+evel The :HCellCongestionLevel A=0 *A=0 Code )+)B/ is of type nsigned-) and it defines on what level the 0C&7 reports the congestion status for the cell.

).12; =-:7-ession-Restoration The :H"ession2estoration A=0 *A=0 Code )+)?/ is of type &numerated. #f the :H "ession2estoration A=0 is embedded within the CCA on command level, it indicates the current session is restored, and 99"N should install the rules in the current CCA and remove old rules. The absence of this A=0 within the CCA indicates 99"N doesnMt need to remove old rules.

#ssue '.() *)+'(-)/


(;




6#"A>L&4"&""#3N42&"T32AT#3N *+/ This value is used to indicate 99"N doesnMt need to remove old rules.



6&L&T&46&7ALT4>&A2&242L&" *'/ This value is used to indicate 99"N should remove old rules of default bearers.



6&L&T&46&7ALT4AN646&6#CAT&64>&A2&242L&" *)/ This value is used to indicate 99"N should remove old rules of default bearers and dedicated bearer.

).121 /-T'"-Redirect-erver The T532edirect"erver A=0 *A=0 Code '''/ is of type 9rouped and contains the address information of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be redirected to. 9$T532edirect"erver EER P A=0 HeaderE A=0 Code ''', =>it set, =endor#6 );'?BQ #t is defined as follows *per the groupedavpdef of 27C -@BB 'I/E 9$T532edirect"erver EERP A=0 HeaderE ''' Q S 9$T532edirectAddressType  S 9$T532edirect"erverAddress  9$T53Append3riginal2L I 9$T53Append5"#"6N I 9$T53Append#5"# I 9$T53Append#5&# I 9$T53Append5"#0 I 9$T536eactivate>y2edirect I U T53A=0 I

).122 /-T'"-Redirect-*ddress-Type The 9$T532edirectAddressType A=0 *A=0 Code '')/ is of type &numerated and defines the address type of the address given in the T532edirect"erverAddress A=0. 9$T532edirectAddressType EER P A=0 HeaderE A=0 Code ''), =>it set, =endor#6 );'?BQ The address type can be one of the followingE 

#0v( Address

+

The address type is in the form of !dotteddecimal! #0v( address, as defined in BI. 

#ssue '.() *)+'(-)/

#0v? Address

'


@+



The address type is in the form of #0v? address, as defined in ;I. The address is a te$t representation of the address in either the preferred or alternate te$t form ;I. The 0C&7 and the 0C27 must support the preferred form and should support the alternate te$t form for #0v? addresses. 

2L

)

The address type is in the form of niform 2esource Locator, as defined in '+I. 

"#0 2#

-

The address type is in the form of "#0 niform 2esource #dentifier, as defined in ''I.

).123 /-T'"-Redirect-erver-*ddress The 9$T532edirect"erverAddress A=0 *A=0 Code ''-/ is of type T7B"tring and defines the address of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be connected. 9$T532edirect"erverAddress EER P A=0 HeaderE A=0 Code ''-, =>it set, =endor#6 );'?BQ

).12 /-T'"-*ppend-"riginal-9R+ The 9$T53Append3riginal2L A=0 *A=0 Code ''(/ is of type &numerated and defines that the srcinal 2L of the HTT0 get shall be included as a C9# parameter to the redirection 2L. The srcinal 2L in the redirection 2L should be sent via a C9# parameter separated with it set, =endor#6 );'?BQ The A=0 can be set to one of the following valuesE disable

+ *default/  do not append the srcinal 2L

enable

'

 append the original 2L

).12$ /-T'"-Deactivate-y-Redirect The 9$T536eactivate>y2edirect A=0 *A=0 Code '';/ is of type &numerated and defines9et thatwith the redirection rule2L shall in bethe disabled immediately when the 99"N detects a HTT0 the redirection redirection flow. *3ne"hot2edirection/ 9$T536eactivate>y2edirect EER P A=0 HeaderE A=0 Code '';, =>it set, =endor#6 );'?BQ The A=0 can be set to one of the following valuesE disable

+ *default/  the rule is not deactivated once enforced

enable

'

#ssue '.() *)+'(-)/

 the rule is deactivated once enforced Huawei 0roprietary and Confidential Copyright 1 Huawei Technologies Co., Ltd

@'



).12% /-T'"-*ppend-'ID8 The 9$T53Append5"#"6N A=0 *A=0 Code ''@/ is of type &numerated and defines that the 5"#"6N of the mobile station shall be included as a C9# parameter to the redirection 2L. &.g. 2edirection 2LRKredirect.tmobile.compassesZ 5"#6NR(;''@;-+-)#5"#R)?)+'';(;+++?)#5&#R-@-+)-+'?-B'??)5"#0R'+.'; B.?.''BoriginalurlRwww.dbank.desavingsZcookie'R')-(cookie)R)-(@K 9$T53Append5"#"6N EER P A=0 HeaderE A=0 Code ''@, =>it set, =endor#6 );'?BQ The A=0 can be set to one of the following valuesE disable

+ *default/  do not append the 5"#"6N

enable

'

 append the 5"#"6N

).12& /-T'"-*ppend-I'I The 9$T53Append#5"# A=0 *A=0 Code ''?/ is of type &numerated and defines that the #5"# of the mobile station shall be included as a C9# parameter to the redirection 2L. &.g. 2edirection 2LR Kredirect.tmobile.com passesZ 5"#6NR(;''@;-+-)#5"#R)?)+'';(;+++?)#5&#R-@-+)-+'?-B'??)5"#0R'+.'; B.?.''BoriginalurlRwww.dbank.desavingsZcookie'R')-(cookie)R)-(@K 9$T53Append#5"# EER P A=0 HeaderE A=0 Code ''?, =>it set, =endor#6 );'?BQ The A=0 can be set to one of the following valuesE disable

+ *default/  do not append the #5"#

enable

'

 append the #5"#

).12( /-T'"-*ppend-I'I The 9$T53Append#5&# A=0 *A=0 Code ''/ is of type &numerated and defines that the #5&# of the mobile station shall be included as a C9# parameter to the redirection 2L. &.g. 2edirection 2LR Kredirect.tmobile.compassesZ 5"#6NR(;''@;-+-)#5"#R)?)+'';(;+++?)#5&#R-@-+)-+'?-B'??)5"#0R'+.'; B.?.''BoriginalurlRwww.dbank.desavingsZcookie'R')-(cookie)R)-(@K 9$T53Append#5&# EER P A=0 HeaderE A=0 Code '', =>it set, =endor#6 );'?BQ The A=0 can be set to one of the following valuesE disable + *default/  do not append the #5&# enable

#ssue '.() *)+'(-)/

'

 append the #5&#


@)



).12) /-T'"-*ppend-'I! The 9$T53Append5"#0 A=0 *A=0 Code ''B/ is of type &numerated and defines that the #0Address assigned to the mobile station *060 address, framed #0 address/ shall be included as a C9# parameter to the redirection 2L. #0v( and #0v? addresses shall be supported. #n case of an #0v? address, the address type is in the form of #0v? address, as defined in ;I. The address is a te$t representation of the address in either the preferred or alternate te$t form ;I. The 0C&7 and the 0C27 must support the preferred form and should support the alternate te$t form for #0v? addresses. &.g. 2edirection 2LR Kredirect.tmobile.compassesZ 5"#6NR(;''@;-+-)#5"#R)?)+'';(;+++?)#5&#R-@-+)-+'?-B'??)5"#0R'+.'; B.?.''BoriginalurlRwww.dbank.desavingsZcookie'R')-(cookie)R)-(@K 9$T53Append5"#0 EER P A=0 HeaderE A=0 Code ''B, =>it set, =endor#6 );'?BQ The A=0 can be set to one of the following valuesE disable

+ *default/  do not append the 5"#0

enable

'

 append the 5"#0

).13; =-:7-'-roup-8ame The :H5"9roupName A=0 *A=0 Code )+)'/ is of type T7B"tring and contains the multi broadcast group name. The :H5"9roupName 5"T N3T be longer than -' bytes in length.

).131 =-:7-*C+-roup-8ame The :HACL9roupName A=0 *A=0 Code )+))/ is of type T7B"tring and contains the ACL group name. The :HACL9roupName 5"T N3T be longer than -' bytes in length.

).132 =-:7-Interim-Interval The :H#nterim#nterval A=0 *A=0 Code )+)-/ is of type nsigned-) and indicates that after the interim interval, >2A" will send charging message to 0C27 or AAA.

).133 =-:7-ervice-Type The :H"erviceType A=0 *A=0 Code )+)(/ is of type &numerated and indicates the service type which type service 0C27 will send to >2A". The A=0 can be set to one of the following valuesE 60# + #ssue '.() *)+'(-)/


@-



>36

'

6AA

)

).13 =-:7-9ser-!hysical-Info-Value The :Hser0hysical#nfo=alue A=0 *A=0 Code )+)@/ is of type T7B"tring and contains the physical position where subscriber logs in at >2A". 7ormatESatm\eth\trunk!NA"4slotNA"4subslotNA"4portE:0#.:C#K The :Hser0hysical#nfo=alue 5"T N3T be longer than )@@ bytes in length.

).13$ lo#-Direction The 7low6irection A=0 *A=0 code '+B+/ is of type &numerated. #t indicates the directiondirections that a filter is applicable, downlink only, uplink only or both down and uplink *bidirectional/. 

N"0&C#7#&6 *+/ The corresponding filter applies for traffic to the & *downlink/, but has no specific direction declared. The service data flow detection shall apply the filter for uplink traffic as if the filter was bidirectional. The 0C27 shall not use the value N"0&C#7#&6 in filters created by the network in Ninitiated procedures. The 0C27 shall only include the value N"0&C#7#&6 in filters in &initiated procedures if the same value is



received from in the CC2 re


0L#N *)/ The corresponding filter applies for traffic from the &.



>#6#2&CT#3NAL *-/ The corresponding filter applies for traffic both to and from the &.

).13% !ac
"&N64T34& *'/

This value is used to indicate that the related traffic mapping information, i.e. the packet filter, shall be sent to the &, if applicable to the #0CAN type as per relevant #0CAN specifications.

#ssue '.() *)+'(-)/


@(



).13& =-:7-Content-ilter P :H Content7ilter Q EERP A=0 HeaderE A=0 Code )+'-, =>it set, =endor#6 )+'' Q The :HContent7ilter A=0 *A=0 Code )+'-/ is of type &numerated. #t indicates the 0C&7 whether the current user has enabled Content 7ilter service. #t can be provisioned or updated at any time through CCA#CCA2A2 messages. This A=0 is optional and its absence means that the user doesnMt subscribe the content filtering service. The following values are definedE 

6#"A>L&4C3NT&NT47#LT&2 *+/

This value shall be used to indicate that the Content 7ilter service shall be disabled. 

&NA>L&4C3NT&NT47#LT&2 *'/

This value shall be used to indicate that the Content 7ilter service shall be enabled.

).13( =-:7-Content-ilter-Information P :HContent7ilter#nformation Q EERP A=0 HeaderE A=0 Code )+-B, =>it set, =endor #6 )+'' Q U :HContent7ilterCategory>asename I UA=0I The :HContent7ilter#nformation A=0 *A=0 Code )+-B/ is of type 9rouped. #t can only be sent from 0C27 to 0C&7 to indicate the 0C&7 the details of content filtering service. #t can also be carried in CCA#CCA or 2A2 message. #f :HContent7ilter A=0 is supplied and set to &NA>L&4C3NT&NT47#LT&2, :H Content7ilter#nformation A=0 is not supplied, There are two scenariosE the content filtering service of this user will be enabled with the content filtering category*s/ in 0C&7 when this service is still not available. The other is 0C&7 will ignore this A=0 when the content filtering service is already enabled #f both :HContent7ilter A=0 and :HContent7ilter#nformation A=0 are supplied and :HContent7ilter set to &NA>L&4C3NT&NT47#LT&2, The content filtering service of this user will be enabled and the category*s/ of :HContent7ilter#nformation will overrides the previous one in 0C&7. #f :HContent7ilter A=0 is supplied and set to 6#"A>L&4C3NT&NT47#LT&2 , 0C&7 will stop the content filtering service whatever :HContent7ilter#nformation A=0 is available or not.

5a$imum :HContent7ilterCategory>asename number of CC2CCA2A2 message is @.

).13) =-:7-Content-ilter-Category-asename P :HContent7ilterCategory>asename Q EERP A=0 HeaderE A=0 Code )+), =>it set, =endor#6 )+'' Q

#ssue '.() *)+'(-)/


@@



The :HContent7ilterCategory>asename A=0*A=0 Code )+)/ is of type T7B"tring. #t defines the operator delivered content filtering service packages that can be the user optin or not. #f some of the category basename*s/ provisioned dose not e$ist in 0C&7, only these name*s/ are ignored and others can be taken effect in 0C&7. #f all of the category basename*s/ are invalid, the content filtering category configured in 0C&7 will be used. This category basename should be configured in 0C&7, which includes 2L category 、action、time range information. 0C&7 gets corresponding 2L of then all the HTT0A0 traffic belong to this #0 CAN session by interacting withCategory#6 #CA0 "erver, match the Category#6 with :H Content7ilterCategory>asename, 0C&7 would carry out the action.

The ma$imum length of :HContent7ilterCategory>asename is -' >ytes.

).1; =-:7-Tethering-tatus P :HTethering"tatus Q EERP A=0 HeaderE A=0 Code )+);, =>it set, =endor#6 )+'' Q The :HTethering"tatus A=0 is of type &numerated and indicates the tethering status of the current user. The !T&TH&2#N942&032T *'+'/! &ventTrigger and :HTethering "tatus A=0 must appear in the CC2 message together. The following values are definedE 

"tart *+/E This value indicates that the beginning of the tethering behavior.



"top *'/E This value indicates that the end of the tethering behavior..

).11 =-:7-Redirect-Times P:H2edirectTimesQ EER P A=0CodeEER )+-?, =endor#dEER)+''Q nsigned-), value range '])@(. The :H2edirectTimes indicates the number of 2edirection allowed of the current user.

).12 =-:7-Redirect-Report P:H2edirect2eportQ EER P A=0CodeEER )+-, =endor#dEER)+''Q &numerated The :H 2edirect2eport indicates whether need the 0C&7 to report the redirection of the current user. The following values are definedE 

6isable *+/E No need to report 2edirection to 0C27



&nable *'/E Need to report 2edirection to 0C27

#ssue '.() *)+'(-)/


@?



).13 3!!2-ID The 7low6irection A=0 *A=0 code ;+'+/ is of type T7B"tring, for -900) indicates the >"#6 of where the & is currently located *e.g. Cell#d, "#6, N#6/. The =endor#d shall be set to -900) *@@-@/ )(I. The support of this A=0 shall be advertised in the capabilities e$change mechanisms *C&2C&A/ by including the value @@-@, identifying -900), in a "upported=endor#d A=0. This A=0 shall have the ^5M bit cleared.

).1 Resource-*llocation-8otification The 2esourceAllocationNotification A=0 *A=0 code '+?-/ is of type &numerated. #f the 2esourceAllocationNotification A=0 is included within a Charging2ule#nstall A=0 it defines whether the rules included within the Charging2ule#nstall A=0 need be notified. The following values are definedE &NA>L&4N3T#7#CAT#3N *+/ This value shall be used to indicate that the allocation of resources for the related 0CC rules shall be confirmed.

).1$ 8-ervice-lo#-Detection P"N"ervice7low6etectionQ EER P A=0CodeEER @)+, =endor#dEERB'?(Q &numerated. The "N"ervice7low6etection indicates whether the service flow detection function is enabled for the 0C&7. The following values are definedE 

&NA>L&46&T&CT#3N*+/E Need to report 2edirection to 0C27

).1% Re4uired-*ccess-Info The 2e
#ssue '.() *)+'(-)/


@



).1& *pplication-Detection-Information The Application6etection#nformation A=0 *A=0 code '+;B, =endor#d '+('@/ is of type 9rouped, and it is used to report once the startstop of the application traffic, defined by T67 Application#dentifier, has been detected, in case 0C27 has subscribed for A00L#CAT#3N4"TA2TA00L#CAT#3N4"T30 &ventTriggers, unless a re
< A+$ Header: ,9 >

 TD;-A776i4ati(n-)denti*ier  8[ ;6(-)n*(rmati(n ] 8[ A+$ ]

).1( TD-*pplication-Identifier The T67Application#dentifier A=0 *A=0 Code '+BB, =endor#d '+('@/ is of type 3ctet"tring. #t references the application *e.g. its value may represent an application such as a list of 2Ls, etc./ for which the Application 6etection and Control *A6C/ rule applies.

).1) 'ute-8otification The 5uteNotification A=0 *A=0 code )B+;/ is of type &numerated, and it is used to mute the notification to the 0C27 of the detected applicationOs startstop for the specific 0CC 2ule from the 0C&7. The following values are definedE 5T&42&8#2&6 *+/ This value is used to indicate that the 0C&7 shall not inform the 0C27 when the applicationMs startstop for the specific 0CC rule*s/ is detected. 5uteNotification A=0 shall be used for solicited application reporting only. Absence of this A=0 means that application startstop notifications shall be sent for the detected application.

#ssue '.() *)+'(-)/


@B



).1$; Redirect-Information The 2edirect#nformation A=0 *A=0 code '+B@/ is of type 9rouped. #t indicates whether the detected application traffic should be redirected to another controlled address. The 2edirect #nformation A=0 is sent from the 0C27 as a part of Charging2ule6efinition A=0. #f the 2edirect#nformation A=0 includes the 2edirect"erverAddress A=0, the 2edirect AddressType A=0 shall also be provided indicating the type of address given in the 2edirect "erverAddress A=0. A=0 7ormatE Redire4t-)n*(rmati(n ::= < A+$ Header: ,5 > [ Redire4t-Su77(rt ] [ Redire4t-Address-T17e ] [ Redire4t-Ser3er-Address ] 8[ A+$ ]

).1$1 Redirect-upport The 2edirect"upport A=0 *A=0 Code '+B?/ is of type &numerated. The following value is definedE 2&6#2&CT#3N46#"A>L&6 *+/ This value indicates that redirection is disabled for a detected applicationMs traffic. 2&6#2&CT#3N4&NA>L&6 *'/ This value indicates that redirection is enabled for a detected applicationMs traffic. This is the default value applicable if a 2edirect#nformation A=0 is provided for the first time and if this A=0 is not supplied.

).1$2 Redirect-*ddress-Type The 2edirectAddressType A=0 *A=0 Code (--/ is of type &numerated and defines the address type of the address given in the 2edirect"erverAddress A=0. The address type can be one of the followingE #0v( Address

+

The address type is in the form of !dotteddecimal! #0v( address, as defined in #0v(I. #0v? Address

'

The address type is in the form of #0v? address, as defined in #0v?AddrI. The address is a te$t representation of the address in either the preferred or alternate te$t form #0v?AddrI. Conformant implementations 5"T support the preferred form and "H3L6 support the alternate te$t form for #0v? addresses. 2L

#ssue '.() *)+'(-)/

)


@;



The address type is in the form of niform 2esource Locator, as defined in 2LI. "#0 2#

-

The address type is in the form of "#0 niform 2esource #dentifier, as defined in "#0I.

).1$3 Redirect-erver-*ddress The 2edirect"erverAddress A=0 *A=0 Code (-@/ is of type T7B"tring and defines the address of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be connected when the account cannot cover the service cost.

).1$ *DC-Rule-Install The A6C2ule#nstall A=0 *A=0 code '+;), =endor#d '+('@/ is of type 9rouped, and it is used to activate, install or modify A6C rules as instructed from the 0C27. 7or installing a new A6C rule or modifying an A6C rule already installed, A6C2ule 6efinition A=0 shall be used. 7or activating a specific predefined A6C rule, A6C2uleName A=0 shall be used as a reference for that A6C rule. The A6C2ule>aseName A=0 is a reference that may be used for activating a group of predefined A6C rules. #f 2uleActivationTime or 2ule6eactivationTime is specified then it applies to all the A6C rules within the A6C2ule#nstall. A=0 7ormatE AD-Ru6e-)nsta66 ::=

< A+$ Header: ,92 > 8[ AD-Ru6e-?ame ]

U A=0 I

).1$$ *DC-Rule-Remove The A6C2ule2emove A=0 *A=0 code '+;-, =endor#d '+('@/ is of type 9rouped, and it is used to deactivate or remove A6C rules as instructed from the 0C27. A6C2uleName A=0 is a reference for a specific dynamic A6C rule to be removed or for a specific predefined A6C rule to be deactivated. The A6C2ule>aseName A=0 is a reference for a group of predefined A6C rules to be deactivated. A=0 7ormatE AD-Ru6e-Rem(3e ::= < A+$ Header: ,9@ > 8[ AD-Ru6e-?ame ]

U A=0 I

#ssue '.() *)+'(-)/


?+



).1$% *DC-Rule-8ame The A6C2uleName A=0 *A=0 code '+;?, =endor#d '+('@/ is of type 3ctet"tring, and it defines a name for A6C rule. 7or A6C rules provided by the 0C27 it uni
).1$& *DC-Rule-Report The A6C2ule2eport A=0 *A=0 code '+;, =endor#d '+('@/ is of type 9rouped, and it is used to report the status of A6C rules. The A6C2ule2eport A=0 is used to report the status of the A6C rules which cannot be installedactivated or enforced at the 0C&7. #n this condition, the A6C2uleName A=0 is used to indicate a specific A6C rule which cannot be installedactivated or enforced, and the A6C2ule>aseName A=0 is used to indicate a group of A6C rules which cannot be activated. The 0CC2ule"tatus A=0 is set to #NACT#=&. The 2ule7ailureCode indicates the reason that the A6C rules cannot be successfully installedactivated or enforced. A=0 7ormatE AD-Ru6e-Re7(rt ::=

< A+$ Header: ,9/ > 8[ AD-Ru6e-?ame ] 8[ AD-Ru6e-ase-?ame ] [ $-Ru6e-Status ] [ Ru6e-;ai6ure-(de ] 8[ A+$ ]

5ultiple instances of A6C2ule2eport A=0s shall be used in the case it is re
).1$( *-ignalling-!rotocol The A7"ignalling0rotocol A=0 *A=0 code @);/ is of type &numerated, and indicates the protocol used for signalling between the & and the A7. #f the A7"ignalling0rotocol A=0 is not provided in the AA2e
#ssue '.() *)+'(-)/


?'



).1$) vent-Report-Indication 5*ll access types6 The &vent2eport#ndication A=0 *A=0 code '+--/ is of type 9rouped. hen sent from the 0C27 to the 0C&7, it is used to report an event coming from the Access Network 9 *>>&27/ and relevant info to the 0C&7. hen sent from the 0C&7 to the 0C27, it is used to provide the information about the re>&27s by including the 2outing#0Address A=0 in the &vent2eport#ndication A=0 to the 0C27. The 0C&7 may provide the following &ventTrigger values to the 0C27E 83"4CHAN9&, 2A#4CHAN9&, 2AT4CHAN9&, "&24L3CAT#3N4CHAN9&, &4T#5&4D3N&4CHAN9&, "&24C"94#N7325AT#3N4CHAN9&, "&24C"94HV>2#64">"C2#>&64#N7325AT#3N4CHAN9&, "&24C"94 HV>2#64N">"C2#>&64#N7325AT#3N4CHAN9&, TA#4CHAN9& and &C9#4CHAN9&. &ventTrigger value 83"4CHAN9& shall be used to report a change in A0NAggregate 5a$>itrate6L A=0 andor A0NAggregate5a$>itrateL A=0 included within the 8o" #nformation A=0. Applicability of the &ventTriggers to the different accesses is defined in clause ;.@@ &vent Trigger. A=0 7ormatE "3ent-Re7(rt-)ndi4ati(n ::= < A+$ Header: ,@@ > 8[ "3ent-Trigger ] [ RAT-T17e ] [ #(S-)n*(rmati(n ] [ RA) ] [ @$$-&ser-(4ati(n-)n*( ] [ @$$2-S)D ] [ @$$-'S-TimeB(ne ] [ @$$-SS?-Address ] [ @$$-SS?-)$3.-Address ]

).1%; =-:eader-nrichment The :Header&nrichment A=0 *A=0 code )+'-, =endor#d )B(@B/ is of type 9rouped, and it is used to carry the subscriber profile information as instructed from the 0C27. #ssue '.() *)+'(-)/


?)



A=0 7ormatE X-Header-"nri4hment：： X-Header-"nri4hment-)D X-Header-"nri4hment-Data

).1%1 =-:eader-nrichment-ID The :Header&nrichment#6 A=0 *A=0 code )+'(, =endor#d )B(@B/ is of type nsigned-), and it is used to carry the subscriber profile #6 information as instructed from the 0C27. The value is + always.

).1%2 =-:eader-nrichment-Data The :Header&nrichment#6 A=0 *A=0 code )+'@, =endor#d )B(@B/ is of type T7B"tring, and it is used to carry the subscriber profile value information as instructed from the 0C27. The ma$imum length of this A=0 is '@ bytes.

).1%3 inal-9nit-Ind ication *V! The 7inalnit#ndication A=0 *A=0 Code (-+/ is of type 9rouped and indicates that the 9ranted"ervicenit A=0 in the CreditControlAnswer, or in the AA answer, contains the final units for the service. After these units have e$pired, the 6iameter creditcontrol client is responsible for e$ecuting the action indicated in the 7inalnitAction A=0 *see section @.?/. #f more than one unit type is received in the CreditControlAnswer, the unit type that first e$pired "H3L6 cause the creditcontrol client to e$ecute the specified action. #n the first interrogation, the 7inalnit#ndication A=0 with 7inalnitAction 2&6#2&CT or 2&"T2#CT4ACC&"" can also be present with no 9ranted"ervicenit A=0 in the Credit ControlAnswer or in the AA answer. This indicates to the 6iameter creditcontrol client to e$ecute the specified action immediately. #f the home service provider policy is to terminate the service, naturally, the server "H3L6 return the appropriate transient failure *see section ;.'/ in order to implement the policydefined action. The 7inalnitAction A=0 defines the behavior of the service element when the userOs account cannot cover the cost of the service and 5"T always be present if the 7inalnit #ndication A=0 is included in a command. #f the 7inalnitAction A=0 is set to T&25#NAT&, no other A=0s 5"T be present. #f the 7inalnitAction A=0 is set to 2&6#2&CT at least the 2edirect"erver A=0 5"T be present. The 2estriction7ilter2ule A=0 or the 7ilter#d A=0 5AV be present in the Credit ControlAnswer message if the user is also allowed to access other services that are not accessible through the address given in the 2edirect"erver A=0. #f the 7inalnitAction A=0 is set to 2&"T2#CT4ACC&"", either the 2estriction7ilter2ule A=0 or the 7ilter#d A=0 "H3L6 be present. The 7ilter#d A=0 is defined in NA"2&8I. #ssue '.() *)+'(-)/


?-



The 7ilter#d A=0 can be used to reference an #0 filter list installed in the access device by means other than the 6iameter creditcontrol application, e.g., locally configured or configured by another entity. The 7inalnit#ndication A=0 is defined as follows *per the groupedavpdef of 27C -@BB 6#A5>A"&I/E 7inalnit#ndication EER P A=0 HeaderE (-+ Q S 7inalnitAction  U 2estriction7ilter2ule I U 7ilter#d I  2edirect"erver I

).1% inal-9nit-*ction *V! The 7inalnitAction A=0 *A=0 Code ((;/ is of type &numerated and indicates to the creditcontrol client the action to be taken when the userOs account cannot cover the service cost. The 7inalnitAction can be one of the followingE T&25#NAT& *+/ The creditcontrol client 5"T terminate the service session. This is the default handling, applicable whenever the creditcontrol client receives an unsupported 7inalnitAction value, and it 5"T be supported by all the 6iameter creditcontrol client implementations conforming to this specification. 2&6#2&CT *'/ The service element 5"T redirect the user to the address specified in the 2edirect"erver Address A=0. The redirect action is defined in section @.?.). 2&"T2#CT4ACC&"" *)/ The access device 5"T restrict the user access according to the #0 packet filters defined in the 2estriction7ilter2ule A=0 or according to the #0 packet filters identified by the 7ilter#d A=0. All the packets not matching the filters 5"T be dropped.

).1%$ Restriction-ilter-Rule *V! The 2estriction7ilter2ule A=0 *A=0 Code (-B/ is of type #07ilter2ule and provides filter rules corresponding to services that are to remain accessible even if there are no more service units granted. The access device has to configure the specified filter rules for the subscriber and 5"T drop all the packets not matching these filters. Dero, one, or more such A=0s 5AV be present in a CreditControlAnswer message or in an AA answer message.

#ssue '.() *)+'(-)/


?(



).1%% ilter-Id *V! The 7ilter#d A=0 *A=0 Code ''/ is of type T7B"tring and contains the name of the filter list for this user.

).1%& Redirect-erver *V! The 2edirect"erver A=0 *A=0 Code (-(/ is of type 9rouped and contains the address information of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be connected when the account cannot cover the service cost. #t 5"T be present when the 7inalnitAction A=0 is set to 2&6#2&CT. #t is defined as follows *per the groupedavpdef of 27C -@BB 6#A5>A"&I/E 2edirect"erver EER P A=0 HeaderE (-( Q S 2edirectAddressType  S 2edirect"erverAddress 

).1%( Redirect-*ddress-Type *V! The 2edirectAddressType A=0 *A=0 Code (--/ is of type &numerated and defines the address type of the address given in the 2edirect"erverAddress A=0. The address type can be one of the followingE #0v( Address *+/ The address type is in the form of !dotteddecimal! #0v( address, as defined in #0v(I. #0v? Address *'/ The address type is in the form of #0v? address, as defined in #0v?AddrI. The address is a te$t representation of the address in either the preferred or alternate te$t form #0v?AddrI. Conformant implementations 5"T support the preferred form and "H3L6 support the alternate te$t form for #0v? addresses. 2L *)/ The address type is in the form of niform 2esource Locator, as defined in 2LI. "#0 2# *-/ The address type is in the form of "#0 niform 2esource #dentifier, as defined in "#0I.

).1%) Redirect-erver-*ddress *V! The 2edirect"erverAddress A=0 *A=0 Code (-@/ is of type T7B"tring and defines the address of the redirect server *e.g., HTT0 redirect server, "#0 "erver/ with which the end user is to be connected when the account cannot cover the service cost.

#ssue '.() *)+'(-)/


?@



).1&; CT-/tension The CT&$tension A=0 *A=0 code )+++, =endor#d B'+++/ is of type 9rouped and contains the location information of the &. #t is defined as followsE CT&$tension EER

P A=0 HeaderE )+++Q

"ubnet#dentifierI UA=0I

).1&1 u,net-Identifier The "ubnet#dentifier A=0 *A=0 code )++', =endor#d B'+++/ is of type 3ctet"tring and it indicates details of where the & is currently located. "ubnet#dentifier is encoded as followsE >its (ctets

:

!

6

1



2

1

;

4

1

3

2

1

3CC@1&it

3

3CC

4 ;

39C@1&it "ro-@;&it

39C

6

%es@6&it

!

%es

:

%es

<

I" Adress@6&it

10

I" Adress

11

I" Adress

12

I" Adress

13

Color Code@8&it

14

Sector@&it

1;

Sector

16

Sector

39C

).1&2 0o-roup-Rule-Install The 8o"9roup2ule#nstall A=0 is used to activate
#ssue '.() *)+'(-)/


??



U 8o"9roup2ule6efinition I U A=0 I

).1&3 0o-roup-Rule-Remove The 8o"9roup2ule2emove A=0 is used to deactivate
).1& 0o-roup-Rule-Definition The 8o"9roup2ule6efinition A=0 specifies parameters for a configured
).1&$ 0o-roup-Rule-8ame The 8o"9roup2uleName A=0 *A=0 code R '-)++(/ is of type 3ctet"tring and specifies the name of a
).1&% Redirect-:ost The 2edirectHost A=0*A=0 code R );)/ is of type 6iam2#. 3ne or more of instances of this A=0 5"T be present if the 2esultCode A=0 is set to 6#A5&T&242&6#2&CT4#N6#CAT#3N*-++?/. pon receiving the above, the 0C&7 "H3L6 forward the CC2 directly to one of the hosts identified in these A=0s.

#ssue '.() *)+'(-)/


?



).1&& TD-Information *V! The T67#nformation A=0 *A=0 code '+B/ is of type 9rouped and may be sent from the 0C&7 to the 0C27 in a 9$ CC2 with CC2e [ TD;-Destinati(n-Rea6m ] [ TD;-Destinati(n-H(st ] [ TD;-)$-Address ]



#n this version, T676estination2ealm A=0 is not supported.

).1&( TD-Destination-:ost *V! The T676estinationHost A=0 *A=0 code '+B;/ is of type 6iameter#dentity and contains the 6estinationHost of the T67.




).1&) TD-I!-*ddress *V! The T67#0Address A=0 *A=0 Code '+;'/ is of type Address and contains the address of the corresponding T67 node. The address type may be #0v( or #0v?.

).1(; Rule-ailure-Code *V! 5*ll access types6 The 2ule7ailureCode A=0 *A=0 code '+-'/ is of type &numerated. #t is sent by the 0C&7 to the 0C27 within a Charging2ule2eport A=0 to identify the reason a 0CC 2ule is being reported. NN3N42L&4NA5& *'/ #ssue '.() *)+'(-)/


?B



This value is used to indicate that the preprovisioned 0CC rule could not be successfully activated because the Charging2uleName or Charging2ule>aseName is unknown to the 0C&7. 2AT#N9492304&2232 *)/ This value is used to indicate that the 0CC rule could not be successfully installed or enforced because the 2ating9roup specified within the Charging2ule6efinition A=0 by the 0C27 is unknown or, invalid. "&2=#C&4#6&NT#7#&24&2232 *-/ This value is used to indicate that the 0CC rule could not be successfully installed or enforced because the "ervice#dentifier specified within the Charging2ule6efinition A=0 by the 0C27 is invalid, unknown, or not applicable to the service being charged. 90C&745AL7NCT#3N *(/ This value is used to indicate that the 0CC rule could not be successfully installed *for those provisioned from the 0C27/ or activated *for those preprovisioned in 0C&7/ or enforced *for those already successfully installed/ due to 90C&7 malfunction. 2&"32C&"4L#5#TAT#3N *@/ This value is used to indicate that the 0CC rule could not be successfully installed *for those provisioned from 0C27/ or activated *for those preprovisioned in 0C&7/ or enforced *for those already successfully installed/ due to a limitation of resources at the 0C&7. 5A:4N24>&A2&2"42&ACH&6 *?/ This value is used to indicate that the 0CC rule could not be successfully installed *for those provisioned from 0C27/ or activated *for those preprovisioned in 0C&7/ or enforced *for those already successfully installed/ due to the fact that the ma$imum number of bearers has been reached for the #0CAN session. NN3N4>&A2&24#6 */ This value is used to indicate that the 0CC rule could not be successfully installed or enforced at the 0C&7 because the >earer#d specified within the Charging2ule#nstall A=0 by the 0C27 is unknown or invalid. Applicable only for 902" in the case the 0C27 performs the bearer binding. 5#""#N94>&A2&24#6 *B/ This value is used to indicate that the 0CC rule could not be successfully installed or enforced at the 0C&7 because the >earer#d is not specified within the Charging2ule#nstall A=0 by the 0C27. Applicable only for 902" in the case the 0C27 performs the bearer binding. 5#""#N947L34#N7325AT#3N *;/ This value is used to indicate that the 0CC rule could not be successfully installed or enforced because the 7low#nformation A=0 is not specified within the Charging2ule 6efinition A=0 by the 0C27 during the first install re
#ssue '.() *)+'(-)/


?;



This value is used toE indicate that the 8o" validation has failed or, 

#ndicate when 9uaranteed >andwidth Q 5a$2eandwidth.

#NC322&CT47L34#N7325AT#3N *')/ This value is used to indicate that the 0CC rule could not be successfully installed or modified at the 0C&7 because the provided flow information is not supported by the network *e.g. the provided #0 address*es/ or #0v? prefi$*es/ do not correspond to an #0 version applicable for the #0CAN session/. 0"4T34C"4HAN63=&2 *'-/ This value is used to indicate that the 0CC rule could not be maintained because of 0" to C" handover. This value is only applicable for -900902" and -900&0". T674A00L#CAT#3N4#6&NT#7#&24&2232 *'(/ This value is used to indicate that the rule could not be successfully installed or enforced because the T67Application#dentifier is invalid, unknown, or not applicable to the application re&A2&24>3N6 *'@/ This value is used to indicate that there is no #0CAN bearer which the 0C&7 can bind the 0CC rule*s/ to. 7#LT&242&"T2#CT#3N" *'?/ This value is used to indicate that the 7low6escription A=0*s/ cannot be handled by the 0C&7 because one of the following restrictions was not met.  3nly the Action !permit! shall be used. 

No !options! shall be used.






The keyword !assigned! shall not be used.

AN4947A#L&6 *'/ This value is used to indicate that the AN9ateway has failed and that the 0C27 should refrain from sending policy decisions to the 0C&7 until it is informed that the "9 has been recovered. 5#""#N942&6#2&CT4"&2=&24A662&"" *'B/ This value is used to indicate that the 0CC rule could not be successfully installed or enforced at the 0C&7 because there is no valid 2edirect4"erver4Address within the 2edirect "erverAddress A=0 provided by the 0C27 and no preconfigured redirection address for this 0CC rule at the 0C&7. C54&N64"&24"&2=#C&46&N#&6 *';/ This value is used to indicate that the charging system denied the service reL& *)+/

#ssue '.() *)+'(-)/


+



This value is used to indicate that the charging system determined that the service can be granted to the end user but no further credit control is needed for the service *e.g. service is free of charge or is treated for offline charging/. C54ATH32#DAT#3N42&_&CT&6 *)'/ This value is used to indicate that the charging system denied the service re
#ssue '.() *)+'(-)/


'

UPCC V300R006C10 Gx Interface Specification

Recommend Documents