You are on page 1of 15

EXHTBII

][ ]
216l
Further particulars are provided belotv on why claim 5 of ,lrl ")E0 is infringed by mobile stations (handsets) compliant
with CDMA2000 EV-DO Rev A or any subsequent revisions, standards or versions. The same explanation applies to
dongles.

in respect of infrastructure equipment compliant with CDMA2C0C EV-DO Rev A or any subsequent revisjons, standards
or versions, the Plaintiff will say that canying out the infrastructure functions identified below infrinees claim 5 of IN
'980,

The particulars below are not an exhaustive statement of all the ways in which Ili '980 is infringed.

A mcthod for 3GrP2 x.-\0011-004-tl oerra:r's ro the cDMA2c00 EV-D0 Rev A standard and subsequenr
oper3ting a mobile revisions/versions, including EV-DO Rev B,.
statiorl with a
radio access 3GPP2 X.S00l I -004-E specifie:: the protocol for Quality of Servi:e (Qo.S) srgnaling berween

network and ii m:bi.e c:ation, laci.o.Access Netu'ork (RAN) anC p-.:ket C..lta scrvtug node (pDSN):
a packet data
a

"This chapter describes Flow Maoping/TLeatment mechanisms and
serving node protocols used when niore tban on(: scr\:ce connection is estal'lished
between tlre I{S and the PDSN. Furthermore, a signalling rnechanisni
lrctween the MS, the RAN ind the PDSN is presentecl in this chapter to
support QoS on a per application ilow basis."

sending a flow As shown in th: diagram helow, in niobile station-iritiated QoS setup, the flow request
request message message in 3GPP2 X.s00l l-c04-E is the cornbination of (l) the Flow QoS Requcs: n,.rrog.
to th: packet date 5 scnt from the mobil: staticn (MS) to the RAN (BSiPCF), and (2) the A-ll Regis:raticl
--_--i I

I

seiving node Request message 9 sent from the RAN (BS/PCF) to the pDSN.
ccmprising

F,l MSlnitiatcd QoS Sctup

}F

I t&c;^'..S;l PFI*

{Cc-:f-"rr.- erl-
c.8.C.f-:J'. Cg(

C.C3A-c..:31
rdA:n{*c CJta,

10 Arr ftC.Adrn|lt

I'fgff0 9t Oo3 Sctp h lt|t €ft{trfd tll8i,|n
_t
Lvv
Source: 3GPP2 X.S00ll-004-E, Page 68

information The Flow QoS Request message 5 senr from the mobile starion (MS) to the RAN (BS/pcF)
specifying a contains an R-QoS-BLOB. As shown below, the R_QoS_BLoB contains
desired quality of QoS-ATTRIBUTE-SET which is information specifying a desired quality of service for the
service for the flow.
flow and

tuP&*
Irril t, corlentof oo$_ATTf[BlrTE-sEr

Source: 3GP!|X.S0A!:004:E, Page 6l

5a.2 a flow request The R-QoS-BLOB contains a Flow ID which is a flow request identifier generated by the
identifier mobile station. The Flow ID is used for uniquely identifying a particular flow request from
generated by the other flow requests from srid rnobile station.
mcbile staticn fo:
identifying the
QoS BLOE QoS BLOB
flow requ:st from
b Tq1r,.f QoS BLCB h tr.d ty tN )lg ;r scqrril $cr lo p f,r. t*
at lexst two flow
requests from said
.+?ry ! S119a q_"$1 l-e{Jlo3-f ,.$ t"ede
co:7rb l,_QuS-$A-lI.Ol &ld ir
t }trs.S$Flr tlr,pD cpr*ce
r.iE b US
mobile station, D._f,-eS-5IrB-BL0B qpsn b *. f-eS_gl,Ol. Ib cc=cr Df h$ C tu
where each flow f_QoS_SUa-EIOB ir ce-.stabct sosrjCAd U
=f np.
h cpree. 5 r_$S^_tloE n p:rS crdd r
request I*:!If
DrF3cFlr I;rrfi4=ntl-ra. n
A, Ss-?.{rxs Eld
[91.
uniqu:ly

o identified
different
by
flow
a
Fa lllPD cfercicr Cr f-QsS-SttB_ErcA b
=rbdd ir r
Ir:s*'=EE$Sbqel:Ilrd c: trgr:l$E&Slrqor*Er riab:r g rrellcjsr
r'lrEl cr.ugr. n [ll rJ 2EJ-f,_QeS_8f.08 a.r; ir b[+rne6 ft'ir:" '
request identifier; r:Ef It Rcqutib{ mt BLOB {n-A0$-SLOBI

ocfi.rtica!of !t Ej3|{'ll llcpftl:

Source: 3GPP2 X.S00l1.0J4-E, Page 59

Each flow request is uniquely identified by a different Flow ID (flow request identifier):

?{uu iLffi5: ltrlrgtqraf IP Srrr:^

Tb li$ .t-lt i:&tdr d:ii 6eld rsd g ir,lr tb n."+c odlp:0lrrr ilftdsl ia &a
I.-qps_EtoB.
Tb !J.3 rlall fuladr .n:e orrrrmqr od ee,&ib*iry *"tra &re*ii nqrrrnrllP ft::
Fi.o['iD: Tte iP florlr lil^rr;F:r.

Iit f !5 !5rll eGtSir Sqli 6 - raignd i1sgtr t!0 mi?.rfu il;*ifiril re S iionr b
&e :ff tb( ris dilr.1ilu,ryrcifsib.reltrirEctico fu:il.
?s9
Source: 3GPP2 X.S00ll-004-8, Page 59-60

After the RAN (BS/PCF) receives the R-QoS-BLOB containing information specifying a
desired quality of service for the flow (QoS-ATTRIBUTE_SET) and flow request identifier
(Flow ID), the RAN (BS/PCF) transmits the A-ll Registration Request message 9 to the
PpSN a Granted QoS BLO-Blc _aoS-BLOBf
9ory-ging
l*'s
"If a new over-the-air interface connection is needed, a new Al0 connectlon
is also req:rired to be established. The R A,^\ then sends an Al I Registration-
Request message to the PDSN indlcating the A10_ID and the Granted QoS
BLOB for the flow. The Granted QoS BLOB includes the FLOW_ID and
the Direction. If a new over-the-air interface connection is not needed, the
RAN still sends an All Registration-Request message to the pDSN
indicating the Al0 ID, FLOW_ID, and the modified Granred eoS BLOB
for the existing connection."

Source: 3GPP2 X.SC01 l-004-E, Page 69

The Granted QoS BLOB (G-QoS-BLOB) will contain the same desired quality of service
for the flow (QoS-ATTRIBUTE-SET) and flow request identifier (Flow ID) sent from rhe

f MS to the RAN (BS/PCF).

E.2 Granted Qo$ ELOB {G_QoS_8LOBI frorn lhe RAH
Ib trred Q'5 SIO! fu rrd b. tr MN ro irftrn *r lS Si:! nrrnd eoS br u Ip
,tr Lrr bra FE=d, l* :rbll00 h *g*rria &. €b G_SS_nna d rrar Dy Or
lA\" [q lllPD Arri.( n]f Cr CJqeS-SftB-ll0S 6rtd h ru by ib t L\.
IL C_QS-f{D;&.OD 49or ia *r O-Qo$_8tl}B. Tb rram d hr sf *r
0_Qlt_StDjBlOl ir cmr h !,*b ctul$0 lr rcJ Atg.
ls cdsl0$ k oprrica. 5 G_$,S_8IOB ir 9*rg. ccrd h, ria Ltrls p lb XS
b er fts_PAff6 eld b ppropnr u3u!4 cau5:r. lr [9t.

I* IilID ^qcn:\ &r r-
truuiodKQo3frperfrnd
c-qdS-SlJ8-8tOB *f ir b*rLd i$ |
lirn:iceESQoSnr:+s:f.:ff rf!*ns ig
tp5.ridFg =r..:rpr u [l!j tad F(].
G-Qo9-ELS3 rwc= tr tr:::rieg 5rtsu
nu*r ?r G.:ntc{t oot SLoE (c:ool3_Bt_o3l

's

Source:3cPP2 X.SC31LQELE, Page 64

Th Fllbiqd$ E:l BL:\

Thc bore rtnio r&dl iriode Sr h:dB'rq! tm SrEr irtbe G QrE_itIl_ELSE.
Flr:t Lrfl0ilr {tfrl
Q.T3JTTFTUTLEF IB
Ra:rr,--d

QoS.AITIIBIITE_$EI_ID rlr 1;r--d5$ or.iryq
\. 6a xi ro & qqsremBiEflIiE-ssl tsr !,$
bro.graabdbf &inA\.

If te nrL{ i;rdiCf, fto .Tllr nt of SS pac:a1 rr4grral \. $r }J3 &r .jd! IF
In. &o BAH rul czit Sir 6rld. O6s,rriro; tbB{l'l rhl l:t r!:r iir.llu 6Im;:
ThrLtll{ma1.ctLr &U to ttr idrsd&r dxtriby rla SIS lo t*m+irl. &r nt cf Qo!
p=tscrn *'t h*o ha grredtydl R*l{;m,
Foc I cd!!d.'00 h l.llE rlr *{lt rnq. s,! ih:6{.i. r{ ,fff9li$, !0 idkzr tu: tb.
$S p*oor nE:rd byt Ug iu tii trPticr tobrsr rdderthrrr uicdrd
ctudlfi k L{!( &r L{}i:ury rc &in sdilb ,l1l I il l. b* rEdi!!ts &s rt :Br!
Fcr r
nfp'mr nq=ruf btinlt$ tr dir tr g!il brlbru rwrrd
F* s HIID X$I. 6r Lt|}i rsy xr i!ir, E:U ro .fi,l0t00y b i!irr.:t fur$ql&al
frS_SL3_BIXE hrt brn dfd hd& i:ll3tu tri! L{,}i rsi 6. }t$ rbcldlll
lsanr tr r.wu,pod. IF :f ur.
r8\
Source: 3GPP2 X.S00l1-004-E, Page 65

receiving from the The MS willreceive from the RAN (BSIPCF) a QoS Granted message 7,
radio access
netwcrk an F.l MS-lnitiated QoS Sctup
assigned service
reference
identifier,
information
specifying at least
granted quality of
service parameters
and the flow
request identifier;

aSOrr:radtn
fdAtrffioclllll

t C liti.(tadh(r
fucit
$.) 3'cilccg.:
P:tt*n)
r0. A1{ frl'.aa'^$N

t1$r| t, oot E|Ll h h. crtrldoc0 8$m

Source: 3GPP2 X.S001l-004-8, Page 68

The QoS Granted messlge (7) contains a Granted QoS BLoB (G_QoS_BLOB) which is
used by the RAN (BS/PCF) to grant QoS to the MS:

\{ "E.2 Granted QoS BIOB (G_QoS_BLOB) from the RAN

The granted QoS BLOB is used by the RAN to inform the MS which
requested QoS for an IP flow has been granted. For cdmr2000 lx operation;
the entire G_QoS_BLOB is sent by the RAN."

Source: 3CPP2 X.S0Cl l-C04-E,Page 64

"7. The MN grants QoS to the MS. The RAN also sends the appropriate
air lin-k parameters to the MS in this step. There are two possible sequenccs
that can occur in this s:ep. If a new air interface connecticn is neecled to
cany the new flow over-the-air interface, then RAN will setup a new over-
the-air interface connection. If RAN decides to cany the flow(s) on an
existing over-the-air interface connection, it then reconfigures the
parameters of that over-the-air interface connection."

Source: 3GPP2 X.S0011-004-8, Page 69

I Th. Gtunt.d QoS BLOB (G-QoS-BLOB) will contain information specifying at leasr
granted quality of service parameters (QoS_ATTRIBUTE_SET) anC flow request identifier
(Flow ID) sent from the RAN (BS/PCB to the MS.
zB{
Gt'ftrfifrnftffim'r 'ritt

8.2 Granred QoS BL08 {G_QoS_8108} from rhe RAN
'Ibr grrbd LL\ i$cn *r ts tr
QS ll,OB ir rad bI tb ao VS d;.icl nfrorod Qo$ rn
0{,s"}lr broFEi. fcrcd:n2l$ h of*rdon t}r r:*n G-Q,S-BLO3 ir rmrf tr
ld\. !s lIiD 6nrrd0c rFtI ri, O;QoS-5UB-lCm 6dl ir ncn b7 b lili,
Ito OJQS-Sn_e.llB rs2c=r in *, C-Qol-rnO:]. tbr scc;* !51 &nflr sf ir
O-QaS-CAjUOD b ocm to ba& cbrF0 h ul tltlg.
l'rci!ri!)O0 trc4*i:o, te ;r:clllyflsi.d fnlnrb &t}lrotbXS
G_QoS_EIOB tu
b tb QoS-PzlIlS 6r:: b ryrpb debs nrsp. n [tl.
C-SS-S1ID-8A'OA @lt ir b*dd ir I
W n f,lsua=E$Sl€€=fr\. rlssiHr ir
rpprp:itr crnpr n fltl :d t30j.
Spdig
O-SS-Blr! €:r!s rb !3cairy ft&:
nDp?t Gnnbdoos 8tO8(G-ArS_BLOBl

\
Source: 3GPP2 X.S_0C11-004-E, Page 64

C_Qcs;Sltsf,l,o8r TloF!&adSE !*Blc5.

Tlr bsu rttioo €r.l hrhdr 6r nbliag tnn 6rlir b tir {Q:5_SIIE-BII3E.
Fbkt Lc:Eth{El
O63 ATTE.ELITE gET It}.
R!tlnrEd

Q:$.ATIXIEUIE^8FI_IS: !!3 iitsrr;;r rtrrpri try.!!r HS ro tia, S,S "{.IIRIBIIF._EII &r llr
b.a t.f-+H.
IffuRllf gdifitr e{'xtqfQo3 F c::fr nqrrrgdb}'tbl hts &f &EIF
it
flon, lbo ttlt {}{ $dl, rrt t}ir 6atd ;s Slorr::
lilN rry s#t &ir Sair O&rnr1
Ih 3.tli u4. rc ti: f.S to fu iiltiGcr rrll-t dh!' !b Mg rr id"d? &r lst cf QrS
v paani* trt krr lo gradti' &r l.d$cr',
Fsr cdsai00l Lfi-$i tbrll$:r,l-l.mi&rf4dts 'fi*L\10'o i:C:$c fti!.!s
Qo3plnrtur ngr'od by0a ${S tnti! IF irrrltolt*e addrilUdalt tdir=d"
Frl r cdlerll00 h X-4J{ $g &dlt uryr'* Sir fetlto "ltlil lt'ro iDii!r.r::r all s:ir
ofprc=r n'gerudtltbllS IcrtLr IF,ibrlnnbcrl Fuoffd"
Fcs::IIEPD n lli, iXn [.{li luy *l &il 6rid is '{,000ff}' n bdicra. r{"rn1rcrd
Qo5:SUE_EIOB lrr bro Lidd ht ir bnn -1 fta tt! lltli r:{ 6c llS. rhmld.lol
rrth:antrco*pod.F&-

Source: 3GPP2 X.S00l l-C04-E, Page 65

3GPP2 x.s00ll-004-E spec:fies the use of a Service Reference ID (SR_ID) which is an
assigned service reference identifrer: "The MS and the cdma2000 identify specific lx RAN
service instances with a unique nurnL':r refened to as the Service Reference ID (SR_ID)."

Source: 3GPP2 X.S_001_LQ0,LE, Page 3

For example, the Granted QcS BLoB (G-QoS-BLOB) sent from the RAN (BSiPCF) to the
MS is contained in a QoS_PARMS field:

For cdna2000 lx opcratior:" tbc G_QoS_BLOB i: gcocnlly canicd &om fie RAN ro thc MS
il fte QoS-PARlvtS field in appropriatc sigrahug rue$sages, sec [9j"

Source: 3GPP2 X.SCCll-004-E, Page 64

The above refercnce [9]refers to 3GPP2 C.S0005-D:
t9l C,S0005"D, Uppr Lrycr (taycr 3) Signaling Standard for cdnra?ffiO
Strrlards for Sprcad Spcctrum Syrtcms, Mnrch 2004.

Source: 3GPP2 X.S001 I -001-E, Page 64

3GPP2 C.S0005-D specifies that the QoS-PARMS field is one of the records contained in a
Service Connect Message. QoS-PARMS field also includes information specifying at lmst
granted quality of service parameters. The Service Connect Message also includes an
SR_ID.

For I $crwc Cffincd Mcsrrp. s Cencr"el ftxl&df Ocrcdrt lrlc:sra5r" or I Us:r,rn*t
ftcdo@ surion *hdl irxludc or|! ocrrrrnftcr d thc foticsin3
tari$leJct6tlr rccutd for ceclr nrdcn opticn corurecdorr of thr xtrral rcnicr
rqnfguetion to be urcd,

Source:C.S0005-D v1.0, Page 3-859

5. 'Bas: stetion" rc::rs to the lur'lctiotrs pedbnned in tho lixcd nltwork. The.sn
funotions typicatly distributerd i.tr:mn3 cr lls, sectors, all(l niobilo sw;tching centet's,
\ SR_ID - Selvicc reference ldentifier.

The merb:le stati0n shall set tlri$ lielcl as lollo|s:

For a Stah$ Response Message, the rnobile station shall
set this field to the serlice refercnce identifirr in use.
Fol a Seryice Rcque-st jllessage arrd a Seryice Re.sl.ronse
,lfessage. tl:e mobile staticln shall set this field as fcrllows:

Tlie' basc station shall set tlris lielcl as lbllotvs:

For a Sol'yir:e Rr,'rlucsl iVlcsse,ge n S*rryice Re.slxrn.se
rlfessage, a Seryjce Connect Message, a Genela.l Handoff
Dtectlon /l4cssago, r:r a Univer.sal Handoff .Di.{,rlion
Message, the base station shell set tttis fielC as follows:

Il thc s<trvicc option mnlle(:tion is a pzlrt ol' tho currollt
sewice conliguration, the base station slrall set this field
to the sen;ce reference identiiier in use.
Ifthe service optioll conr:pctiort is not a part of the
curlert scrvice corrfigtrration, the l^rase statioll shall
perlornr f h
" frrllowing :

- lf tlris
service optiorr cotlltectiorl request is llitiatecl by
the nrobile station. the base station shall sct this fir'd
to tho valuo slnt by tire lnobile staLion.

- If this service optioll conllectiorl requcst is initiated lry
the base str tion, thc base stat:on sliall perlornr tl:e
l'crllnv"ng: if the service instanctl pr'ovides a scllia ,

r(r;eronco itisntilier', ttro binn station slriill st:t this fie:rl
to lhJ s,'lvico refercnce itlentifier specilied by the
service instance otharwise, the base station sitall set
this field to the highest unused servicc reL:rerrce
irlerrtili<u: valtro l:rrrtwxln l. ;;nd 6 inchrsivo^

Source: C.S0005:D v1.0, Page 3-863

QOS-ltARt\S - Qa$purctcrrb:oci
TtE Nno:bi& $trtionsh!:l zct tlrrfnldc: blb*r:
lf QGJSflMSJ:,TL b
=i io'l'" thr rmbilc :rtgrion CrlI
indrde thh iiCd hllm tccord l* f:lhr:r::
I;cr l $alur &.rycn*
lJcc;nge. tlx nrobih srarhn shrll
nct thr field *o the *ct
of QoS pilnffFlcfi ennli;trul for
thlr ccrviac cpdpn csrxrcctisn"
u%\

$or a Scnicc &qx::t f,icostgr or Scrui* Rcapcu*
lfcsr.rpn, Xtrc rnobile;tltion rlurll rct thi* fdd ro t:r: rcr
of AoS pffirm*te$ rqutltcd hr $n m:pcctirr
corulmtion.

The bl*r rt.rtisn shrll:r* fhb 6*ld n* fo[nm:

lf QOS-PARlrlSJllCt ir scl [o 'lo, thc bffo :&rtian clutl
includ* tlf.: fEH in thr: rrorrl ffd *d it tp rtu rct o{Qo$
panff[tnfi rqursttd ur mguircd lor rhc Kqpcdi]r
aoruhctloft"

Source: C.S0005-D v1.0, Page 3-866,3-867

As shown in the diagram below, a cdma2000 lx voIP setup call flow is an exampie of a
situation in which the MS will receive from the RAN GS/PCF) a Service Connect Messase.

t
t.Eol|F,8Jn 3o*trll

tO tcar Cfrfi|lt!*nf| rr t!i{ |laq

b Source: 3GPP2 X.S00 ; 1-004-8, Page 55

The SR-ID is also canied in a ResvConf message 12 which originates from the PDSN and
travels to the MS via the RAN. The MS receives the ResvConf message including the
SR-ID frorn the RAN (BS/PCF).
I

I

,{
ri

I
@hhnffirryrfrm @INhflmDtW{mlnspAAM1sdhe$rgitrffi
:7

F"{ M$.fnittatod Qo.s Setup

.(

l+.$
h U*Yr.ilrL** Nr:
trr'*tr'131
$S
frfir:,:ao
*Sn$r* t Sffi#i;:{.rfil
ftf,lr#s
ll,tlHtlilt
S'5
.{ r*rSiitH/i*s'**
d.frJr; ik
2i

'a ]}st SS* in

*:0f,:1.*tt.1..*ii.
*r11.0c'E*iUS E'-O*;
f
n
S'{$ gsnr:tc-t':
s:l,fii,ns:1€n$$
l^ &r*Sfi**ild
SJ$rS*Eif,l *"
f r*Sc3*G|.1]*SnA, tfi].'i
ftffr:,.d*!g

'a AI',f:,ll:r;,.'i
,Ccni';::l
lAf:*il. C..::rt*r-)
.i

Fgs":' ii,.1

\.};
\.' 10. Al I f*-*f-{*^ f,.-'p*1

,I

I

,

:,

.l

1
1

a

r: fi;guro$t Oo$ '$cfrip,ur f'$ *{rla;:t.}[$ 3f$r,.rr

Source: 3GPP2 X.S00l 1-004-E, Page 68

11. The ltl$ smds a Resu nesage lo the PD$ltl to pmride the PDSIi uith TtT for the ftelv
datr llow. The !!S fiuy rls€ SD8 to serd lhr Revt message. ln &ir caseo the tr{S ".hall
aslochle $g $DB nrith the nrin orer.tft,e.rir iltaface cotuection

12" Tlc PDSN r*sponrk wih RcrvConforesrag* coafirnirg tie reserra$on
i

l,i
l\\

a\1
\-A
r
.'

'; Source: 3GPP2. X.S00.1.!_-004-E, Page 69
I

j
-j

3GPP2 X,S0062-0 vl.0 specifies that the ResvConf message includes an IE List.
;
i1

-r
"l-h* l'l)$N trd lvl$ sh;ll lullnrr tlm lhltnwing firr$.r{ i'nr Rsr*f:onf lnrjrillls-
it

a

:l
'l
Thc Hstvf,onf mrtlast rpncifird inX,li{}tlll tfll ix rnmlilirrl in tlris rp;"ilic-rtlnn hy adrling
,{
)l ths lfi l"ist to thn uurmgc..
,}

.l

I a s
.]

i
I
I
78s0 g4s s901 78901
3GPP? Class I #rf
a
'ftancnstinn l.D
i

!'ffi-
ll, I.isl
4*ffiffi f ffiwwri..s\-a*-rFwr_
;
; ,F{gura 23 $GPP? OBJFST fn ffssy0onf lsannago
:.
l:

l:

i.

't
Source: 3.G.PP2 X.SQ_062-0 vl.0,Page 64
i

i
1

Section 8.1.1.1 of 3GPP2 X.S0062-0 vl.0 describes the IE List:
)
.t

l
I
lr
t
{
lli l,Lrtr
I:,
lfhc f'PSN rhall include thin fisld if
the lt$$hl d*ternrincx rs mo{tiry rhu
st'flluetion pme*d$Rss vnlu$ of pilshct liltcrs tlurt ilr* i;rnt by rhe iltli
CInu $r mCIrp,
ln lhe Renv rne{ifillgc. The IH Lirt Infiy :include ons or nrerr l$.,i" T}rr. fnrmat *f
.lol
v%\
G'uftmnffinfun GlNlMm0lmftm&vAAmd$rftsryrnr0M
i Source: 3GPP2 X.S0062.0 v 1.0 ,P.age 64

; Section B.1.1.1 of 3GPP2 X.S0062-0 vl.0 specifies that the IE List includes an IE Type #:
i

7:
I[ Lict:
ii
ii m H$ shall includc on$ sr slsrs ffi$" The forun* of an If, is as follorw"
ii,l
IahJn 5 lH
123
1l

012 3d5SVI I0 { 2 3 4 5 '1 2 3 -{ S 6 7 g g 0 1
i I fE Type #
1S Data

lS Data I Paddins

,.1

1i Source: 3GPP2 X.S00il-004-E, Page 32The IE Type # refers to a Traffic Flow Template
x
(TFT) such as TFT IPv4 and TFT IPv6:

IETWe#:
I
r1
$.' A utunbcr ussd to identify the InfnrmatinnElnment,
ad/
\:
; Feble S lE Type #

lE Typ€ # lE Type#
:
valus
IrIlrv{
r%
0
lrllFv4uffor 1
trtfrvD 2
.l f r ilrvo gnor 3
ffeader Rennoval 4
Hnader Remosal 5
finor
l 'Channel Treatrnent 6
)
Channel Traatmont 7
I
finor

I
i Source: 3GPP2 X.S00l I -004-E ,Page 32
i

TFT IPv4 and TFT IPv6 contain the SR ID:
:

l
Table i TFT l,Pv4 tH Type # n 0
:
f 2 3
.
73 { 5 0 V g I0 12 3,t 567 S 9012345S 78901
r
D Rss
efv
$d
h
(
\.. '*T Resnnl'ed F TF"f Oporation Cpdn NumbBr of Packpt
filten
Packsl filter li
i

:
Tahlo 8 TfT lPvS lE Typo # tt 0

1 3
;
CI I 23 45 S78 I 0 1 2 3 45 6 78 I 0 t 23 *t 5'0 7 89 01
;

lPv6 addrsse
i MSlPv6 addrees
:
ffi$lPvd nddress

i
I Packst filter
I

i
I

Source: 3GPP2 X,S001l-004-E, Page. 33

receiving a flow As shown in the diagram below, the flow request confirmation message in 3GPP2 X.S0011-
request 004-E is the ResvConf messase 12 sent from the PDSN to the MS.
.t

.

i
?rqe
ffinunflnfrrlfiua GINAAmB\HDOReuAeWSdlreWgilffi;&:
confirmation
message from the

..
packet data
serving node, the ,LlS Afr'Ftr pssH AAA
:

l
flow request
{ confirmation H3 t. T*o*cr"le:Qanx 3d{}:f$-**n t#l}
t-"sfril
I
message also fiF*1u*ro
rt**s * ,rrs.*$,tt'tr*l
i
comprising the ft$fhrcs
rrpcio
i flow request QIB
?.J**: JF-;t1i*!rc:*:: tg n, ..,
identifier; and d. I,Ai:e,rr*oI irri*
;
!,
a hJ nS Ri.;.rJ 'i{,1.,*, F
:
*rf, *lC .?t: '.[t"C;;

ffi

I -'il;rl*;i;*-:
t *t"r*aft:J
tiiiiixilaacai

j

;:
0}{*
:

v' 10. 1 l};;'i^**; 3- !.?
"6t
ii
,
: rr it: t'fi1.
nq ;^ficnf
1

j,

I

D

Flgwo$l O$$ $*rp n rtr *ffi;ft3$S 'syrtfiyt
,,

')
Source: 3GPP2 X.S00l l-004-8, Page 68

It. The M$ smd: a Resv ne$age to the ?DSN to provide the fDSN r*ith TFT fbr tha ner:,'
data flow. Tbe }{S eay use $DB to smd tbe Rew nessage. Ia $is casq the:t''!ff 6hall
a$sciatetb* $lDB u,ith the nais or.er4be.air iater&ce cosuection

12. The PDSN respondb uith Re,ltfosfose$s8g€ con$rnhg tbe rercrratior

Source: 3G_PP2 X.S0011-004-E, Page 69
.i

3GPP2 X,S0062-0 vl,0 specifies that the ResvConf message includes an IE List.
l
,l

I "llm ['DliN and M$ $all follow ttlt follt]winf ftlnmt lirr Rssvt'onl'tnrnrirgr:,

ThcRcivConfmsltrgespccilicdinX,${X}ll lfrl is nrrxlilied in thir specilic;ltion b,r,adrling
ltlr II5 [.ist to lhc nwsmgr. t
:
4 l2 3

;
34S678g{}12345S78S01 fl,3 4 5 S 7 g g 0
SGPP? C,lass
Tr*nrnqtion lD
s r *,..8!. .+4aat{afiK*ffi;ls.nia({att'llffilr*
^r$9nw" a*q {'..re
ll. l.ist
:
flgure 2S 3GPPA OzuACT ln ffeav0o,nl Mssssgs

Source: 3GPP2 X.S0062-0 v 1.0, Page 64

Section B.l.l.l of 3GPP2 X.S0062-0 vl.0 describes the IE List:

ISLI$r
Ths Pf)$N slmll include rhir field if $s PD$N dcnrmines lo rnontify rhe
evnlu*tion precod*ncc vtluc of oue or nwre pire*e| liltm* tlrat ma rcnt by ttrc l*U
' in u\e Resv mnrmgc. Thc lE List rnay inclu& onc sr mors Ttre founim of lk.
the ffi List shall follow rlu lF List.rpaciSrd tn;ie*rinn B"l.l.I of X.Sfl{tt I [61.
\|{ :

ai I

'1,r

i,-

Mil
tt'l

:tj
rrt

.t\
::'

:
I
gldinrnrnh{ncm MWdD@MAAdW
.;l

.l

Source: 3GPP2 X.S0062-0 v1.0, Page 64
'Jl

"l
'^
Section B. I . I . I of 3GPP2 x.s0062-0 vI .0 specifies that the IE List includes an IE Type #:

I
!

IE List:
.J

IE tist shdl includc o$e or rlror$ IE$. Ths form* of an IS is as fnllour.
.!.

i: I'able 5 lE
t,.,

01?345678901
1 23
.t

-'.
3__9"-{._"5- S7 II 0 { 2 3 ,r 5 $ 7 I e 0

'l!
lE 0ata
tr
.:
lE Da{a
:r
.4

:1
'1
I
',1
a

a
;,r

.1
_:!
Source: 3GPP2 X.S00 I 1-004-8, P age 32
't
(r.
,.1
,,I

The IE Type # refers to a Traffic Flow Templare (TFT) such as TFT lpv4 and rFT lpv6:
;I
!{

l\

;
IS Tlpe #:
\';
.,;l

br'
\.l-:
A numbe,r u$ed to idmtify thn lnforsnrion slrmmt

:
I

Iable 6 lE Type #
I
lE Type # fE Type#
vaNus
IrIfFV4
a

.i
0
,I
'l

I
fFlltrv4trror 1
'I
.l
'\
rrftrvs 2
l
ffi
ffi%

.) 3
: flnadsr Rernovaf 4
:
l
I
Hsader ftarnoval 5
.i
f;nor
'a

fihannel Treamsnt 6
'i

Channef Tr*atmsnt 7
1!
:
Enor
I

j

Source: 3GPP2 X.S001 I -004-E , Page 32
.Q i

TFr IPv4 and TFT IPv6 conrain a packet filter lisr:

Inblo 7 TfT |Pvd lE Type #''r 0
1 3
0- 1 ? 3 4"9_q_l s 9 0 I 234567SI 0 1 23456 7I I0 |
M$lFv4 address
D Rss ,$HJU p
N Ressrved Nurnber of Facket
0fv .s
filters
*tl
Enshel tllerlillll]

IEDIo I TFTIPvS lE TypCI # rs 0
123
12 349 6 7 il 9-! 1 2s 456 ?Ee0 1

M$fPvG address
TFT Opointion nnde -1" f'iuffier ofFffii

Source: 3@2 X.S001l-00a-8, Page 33

!le-p39k9t filter list includes flow requesr identifiers (Flow ID) identifying each flow.
%1v
.j

i
glfintlffihffm GIMAAm0nMdEOeeA,Anrn$fmEfnmn@
Paclcet tilter lirt:

Th* paclret filter list contarns a variable numbcr of prckct Slt$ns, for ths "dclste
adsting TFf opimtiorl tlre packct filtcr list *hall be rrqpq'.
:

I For thc operation "deletc packet filtsr$ &om €xistrng TfT' and '-Initiatc Delete
I
Packst filtcr &om Existing lTT"n thn packet filts list shall *ontain a ruieblp
number of flow identifrers girnn in thc numbor of paclBt filtcrs field" In rbis casc
',? tbc pa*ct frltcr precedorce, lengtln, and rontents aro not includodn only ths Florv
Identifim ue incMrd. Figurn 4 rhnrxs th* li*of Florvidontifiers.
1

I
.:
fl,url' 12 l' ln lu lu I'
-l.-
r'Iurrr'(IBmfnErrl
Flow ldentifier 2

Flow ldentifiBr N

I
Source: 3GPP2 X.S00 I 1-004-8, Page 36
i

rt Flmr Id:EtS."g.# ffiffiII
V A gxkc gm cuC;ihs fru*J::sil {l *,mgr
i

?t$ *:,,$l*f ib; fn $u:i$x4?,w.::r) I

'l
,Tn pc*c* €rur m;w i r.F ry $*:; i* ;r*:: f; fi a:ls E$ *ei,al
i
Ss epd*e*I Ssir gsr:s,* xnh-qaa: t*;d,*i,mkr fi t:,i$
i

,
J
Source: 3GPP2 X.f0_0,1 1-004-E ,Page 37
:
1

;
3GPP2 X.S0011-004-E defines the flow identifier field (Flow ID) as follows:
{

i
1
Florv l&nllllrr (FLOIV_ID) (8 blt$:

Thr Flow ldentifier field is rued to identifr ench ressnfiior to or from an lrIS and
'i shall be mique withio tllc ldS acros diffcrent rescn'alions. The lrRlue frc$'_iD
'I mluc nmy be uscd h thc fonrnrd nnd rrt'qsr dircctions. Onc fl,O\\'_ID can be
j assocjated with orc or rmre packct filtsrs.
:

1

l.
Source: 3GPP2 X.S001 1-004-E ,Page 37

j 5d conelating the A Resv message 11 is sent from the MS to the PDSN.
flow request
identifier with the
i assigned service
reference
I
identifier.

;

:,

.1.

i
"aq9
Ohnmftffir'rftirrr GlWhflmWmtswAAmilftlbsqfrmnffi
F.{ M$Jnitint*d Qo$ Setup

ScfuJ t ...)3 *r..-'-?:ll

? A'nt: iar. -'.;r i-;utcrr*rr *t
J.i.;.;t l"rf,;^lf;"3ll

r* 0;ifi*tg-l',lt.**-L
fr n.g$.it}3*trg:i

6.&*l t*,'ti,*l#, '
*rd J\lir::lt:r fi4;€*l

f g;:i:l
l, &
f0 *
"OtS*S,i4'i
fi 'tel f$t./{(''il
gtr$
hra:rtc-ut

fi 41"{;qi.-r*t;lr
I.L- s4
:., l'a,frrrt

llri10; C"*: :J *:i
Fl l.*-.;l

'Is ,fi I r: .i +v
-:i;d-f

f!$ffiet, so$ $ct$nfi fiHsffi*sl} syuiln

Source: 3GPP2 X.S00l I -004-E, Page 68

The Resv message contains a 3GPP2 OBJECT which includes an IE List.

f;l*'1"1,.1 $$pFn sruf;fiT
T.d$ : ffm CAAn:f thtt r;;r;ss h .kt$ tr i$$grl ,*f rry ssirhtt0'd*'r{g hhli cI
;'-r
arrl{F afffi,^r*lrH 1flra t

td U .TFT

e lfurkgffi;';'J ialu,,lgsicrFa:r.s,frfl
n ,tlu=$T;ruEg:"u
fi:l lt$ ml ** ffi$:f tH fxhfu Li L:;t mr hfnm*"is gxs::s rT*i r:* fu l*i;Fi
$3;:tF; *n & n**i- br npxet fx I$F#t *S-[,ff r*\.til bo {rlml-ra{ m pcr n-l-*lA
filelsd ura};rxg ffibc:.'Tlp }l-Ip:. *AE{I **l Lsra (i;; il;rnk.r's Al" S*:,r
Tiyrt er S.TlBrs I ,md n iE*f H*", ift* fsnm *f*b: i$)flk *BI3{.t li *r-.';hli;

raslr d 9GiPfre ps;*sl

.1 3 $, !t S $ ?,il'* S f I l S s' ? i'i Q1&n .* :i j 3 -: t S i
Lt':93 lIe.^F,3Cxl fS:'').*
Ytrsr.itcn'.$

m
trrst a$ s9 n*i l: ti?

Source: 3GPP2 X.S00l l-004-E, Page 31

IE List includes an IE Type #:
wqv

If, List:
IE List shall inctudn ono or rnoro lts. Ths format of an IE is as follont,

Tabls 5 lE
123
t3a
01 23 { 567800'r 2 34 $6? 890 12 3{567 88 0 1
Lenotlr | ffiTvne#
It Data

lE Dnla I Faddinq

Source: 3GPP2 X.S001 1-004-E, Page 32

The IE Type # refers to a Traffic Flow Template (TFT) such as TFI IPv4 and TFT IPv6:

IE Tfp* #:
A nurrrbcr u$$d to identify ths Infornation slemenil
t
J

6
I

I
t
,l
Tahte lE Typo #
l.
L
1

L1 lE Typp # lE Type#
tl

Yalils
t r ilPv4 tt
tF ilhrv4 tror 1

rr ilrvo 2
lrtrrvDgffor 3
H*ader Rnmovaf 4
|fender Removal 5
finor
Channel Treatmsnl 6
Ohannef Treatment 7
Fnnr

Source: 3GPP2 X.S00l 1-004-E,Page 32

TFT IPv4 and TFI IPv6 contain an NS bit:

Y{. Inble 7 ffT lPv4 fE Typo # o 0
1 2 3
n'f 234557ff901?3{$A78 901 23*l$6789 01
Nl$lPv4 address
T,FT Operntion Gode

Packet litt

Inble I TFT lPv6 lE Typs # Er 0

1 3
0 1 23 456 78 I 0 1 23 {'$S 7g g 0 I 23 {5 6 r S g 01
M$lFv$ addrnss
h{SlPv6 addrnss
M$lPvn sddre,ss
MS:Pv6 addrsss
"
$* oruoil
fFfTFWfffiiffi;oiffi;ilei
II I
nrers

Pnchel fih*+h#J

Source: 3GPP2 X.S0011-00tE, Page 33

NS bit which indicates the type of FLOW_ID-Io-A10 connection mapping:
vT(
tl ('l
ffiqffiOnsr/{Anil@
ll
I nt. Non-Specific bit. This bit indicates the ry1re of FLOW-ID-Io-AI0 coru*ction I
the
I n*ppirrg requested for
to-f,10 coil$ction rnapping shall be indicated by the RAN hr All siEraliug. Mren I
l
I
I Ure bil is uot se(, it iudicates tlmt the FLOW_ID-Io-AI0 connection mat)ping will be I

I dictared by the lvtS. Wheu set, rhe SR_ID field shnll bc ser ro 0 and th* P bir shalt be I
| *t.,:J:I3'*1,?.'|:.Nsbi.,{,ulyt*::1,:.1 . ._. _ - |

Source: 3GPP2 X.S001l -004-E,Page 34

An Al0 connection exists between RAN and PDSN for data transfer.

fu ouflined iu [1], the RA]i tramfei's data witb the PDSN via one or more Al0

Source: 3GPP2 X.S0011-004-E, Page 3

The A10 corurection is identified bv SR ID:

t-l
I Contains tlu ideirtifisr for the Al0 corur*ctiou on nhich rhe T.FT a14llies. l\'hen the I

I ir
Ns bir i.i6m',ffiJffiffiyxTe caire for: I
I HRPD. I

Source: 3GPP2 X.S00l1-004-E, Page 35

Since the NS bit indicates the type of FL.OW-ID+o-A10 connection mapping and the Al0
connection is identified by the SR-ID, the NS bit is used for conelating the florv request
identifier (Flow_ID) with the assigned service reference identifier (SR_ID).

Furthermore, the Flow ID is conelated with the SR_ID when any transmission occurs using a
specific SR-ID, since that transmission will need to be allocated to a transmission link by
reference to the Flow ID.