UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`ZTE (USA) Inc.,
`HTC Corporation, and
`HTC America, Inc.
`
`Petitioners
`
`v.
`
`Evolved Wireless LLC,
`
`Patent Owner
`
`
`
`
`
`DECLARATION OF ZUO ZHISONG
`
`Case No. IPR2016-00758
`
`
`
`
`
`ZTE/HTC
`Exhibit 1015-0001
`
`1
`
`APPLE 1015
`
`

`
`1.
`
`My name is Zuo Zhisong.
`
`I am a Standard Engineer at ZTE Corporation.
`
`I
`
`have been employed by ZTE Corporation since 2005.
`
`2.
`
`For more than 10 years, since February 2005, I have served as one of ZTE’s
`
`delegates to the Third Generation Partnership Project (“SGPP”) in a subgroup of
`
`3GPP’s Technical Specification Group - Radio Access Network (“TSG-RAN”)
`
`known as Working Group 1 (“WG1”).
`
`3.
`
`During this period, I have attended dozens of WG1 ’s meetings and
`
`subscribed to WGI ’s reflector list (3GPP_TSG_RAN_WGl@list.etsi.org), to
`
`which I have sent hundreds of e-mail messages and through which I have received
`
`thousands of e-mail messages. In general, before each WGI meeting that I
`
`attended, I received e-mail messages from delegates of other companies through
`
`WG1’s reflector list, providing technical documents, called contributions, for
`
`discussion at the meeting. Some of those e-mail messages provided the technical
`
`documents as e-mail attachments, while other e-mail messages provided links to
`
`the locations where the technical documents were stored on 3GPP’s publicly
`
`available website <http://www.3gpp.org>. Regardless of how the e-mail messages
`
`provided access to the technical documents, those documents were also uploaded
`
`to and available for download at 3GPP’s publicly available website.
`
`4.
`
`As a delegate for WG1, I sent e-mail messages submitting technical
`
`documents on ZTE’s behalf to WGl ’s reflector list hundreds of times before
`
`ZTE/HTC
`Exhibit 1015-0002
`
`2
`
`

`
`meetings for which the documents were submitted for discussion. I also uploaded
`
`technical documents to 3GPP’s publicly available website more than 200 times
`
`before meetings for which the technical documents were submitted for discussion.
`
`5.
`
`In my 10 years as a delegate for WG1, I have also regularly accessed the
`
`location on 3GPP’s website storing technical documents submitted to WG1. That
`
`location is available at the uniform resource identifier
`
`<http://www.3 gpp.org/ftp/tsg_ran/WG1_RL1/>, which I refer to in this declaration
`
`as “WG1’s public directory.” Since 2005, I have accessed WG1’s public directory
`
`in several ways, such as, for example, by entering the uniform resource identifier
`
`of WG1 ’s public directory into an Internet browser and by accessing 3GPP’s
`
`homepage <http://www.3gpp.org> and then navigating to the uniform resource
`
`identifier of WG1’s public directory. Regardless of which method I used to access
`
`WG1’s public directory, I have never encountered a password requirement or any
`
`other restriction that would prevent me or a member of the general public from
`
`accessing WG1 ‘s public directory or any intermediate location. Based on my 10
`
`years of experience as a WG1 delegate, since 2005 to the present, any member of
`
`the public could freely access WG1 ’s public directory, browse it, and download
`
`technical documents stored to it without restriction.
`
`6.
`
`I attended WG1 Meeting #44bis, which was held on March 27-31, 2006, in
`
`Athens, Greece. Attached as Exhibit 1 is a true and correct copy of an e-mail
`
`ZTE/HTC
`Exhibit 1015-0003
`
`3
`
`

`
`nw$@emmdMmw2L2MmJmmwbfimeM%mg#MhsIommmdmfie
`
`mail message from 3GPP’s public e-mail website, which is available at
`
`<https://list.etsi.org/> and with which I have become familiar as a WG1 delegate.
`
`Like all other members of WGI, I received this e-mail message from Mr.
`
`Katsuhiko Hiramatsu through WG1’s reflector list along with five ZIP file
`
`attachments, including a ZIP file titled “Rl —060792.zip.” That ZIP file contained a
`
`single Microsoft Word document, a true and correct copy of which is attached as
`
`Exhibit 2. Neither the ZIP file nor the Word document enclosed in the ZIP file had
`
`a password or anything else that would have restricted my ability to access its
`
`contents.
`
`7.
`
`In preparing this declaration, I accessed
`
`<www.3gpp.o1'g/ftp/tsg_ran/WG1_RLl/TSGRl_44bis/Docs/>, the location on
`
`3GPP’s web site at which R1-060792.zip is accessible to any member of the public
`
`without restriction. Attached as Exhibit 3 is a true and correct copy of a printout
`
`from that website. Exhibit 3 lists several ZIP files, including R1-060792.2ip, as
`
`shown in the following excerpt.
`
`3/21/2806 16:4
`
`1 AM
`
`3/21/2666 10:2
`
`3/21/2996 9:9
`
`3/21/2966 9:9
`
`3/21/2896 9:0
`
`0 AM
`4 AM
`4 A
`
`4 AM
`
`963139 R1-969789 . Zip
`468156 R1-866790.219
`124596 R1-866792.219
`17727 R1-B66793 . zip
`35394 R1-966794. zip
`
`ZTE/HTC
`Exhibit 1015-0004
`
`4
`
`

`
`(Ex. 3 at 1.) The text “R1-060792.zip” provides a link to a ZIP filed titled R1-
`
`O60792.zip.
`
`I downloaded and opened this ZIP file and found that it contains a
`
`single Microsoft Word file, a true and correct copy of which is attached as Exhibit
`
`4.
`
`I compared Exhibit 4 to Exhibit 2, the Word file in the attachment that I
`
`received from Mr. Hiramatsu on March 21, 2006, and found that those two exhibits
`
`are identical.
`
`8.
`
`In the excerpt from the 3GPP website printout shown above, there is also a
`
`date stamp (3/21/2006) to the left of the link to R1-060792.zip. Based on my 10
`
`years of experience as a delegate for WG1, having uploaded more than 200 ZIP
`
`files to 3GPP’s publicly available server, I understand this date stamp to mean that
`
`R1-060792.zip was uploaded to 3GPP’s publicly available website on March 21,
`
`2006, and that any member of the public could have downloaded the ZIP file,
`
`extracted the Word document it enclosed, and viewed the contents of that Word
`
`document without restriction on March 21, 2006 and thereafter.
`
`I have no reason
`
`to believe this date stamp is inaccurate.
`
`9.
`
`I also attended WGI Meeting #45, which was held on May 8-12, 2006 in
`
`Shanghai, China. Attached as Exhibit 5 is a true and correct copy of an e-mail
`
`message dated May 2, 2006, shortly before Meeting #45.
`
`I obtained this e-mail
`
`message from 3GPP’s public e-mail website, which is available at
`
`<https://list.etsi.org/>, and with which I have become familiar as a WG1 delegate.
`
`ZTE/HTC
`Exhibit 1015-0005
`
`5
`
`

`
`Like all other members of WG1, I received this e-mail message from Mr.
`
`Hiramatsu through WG1’s reflector list along with two ZIP file attachments,
`
`including a ZIP file titled “R1-061l14.zip.” That ZIP file contained a single
`
`Microsoft Word document, a true and correct copy of which is attached as Exhibit
`
`6. Neither the ZIP file nor the Word document enclosed in the ZIP file had a
`
`password or anything else that would have restricted my ability to access its
`
`Contents.
`
`10.
`
`In preparing this declaration, I accessed
`
`<http://www.3gpp.org/ftp/tsg_ran/WGI_RL1/TSGRl_45/Docs/>, the location on
`
`3GPP’s website in which R1—06l114.zip is accessible to any member of the public
`
`without restriction. Attached as Exhibit 7 is a true and correct copy of a printout
`
`from that website. Exhibit 7 lists several ZIP files, including R1—061 I 14.zip, as
`
`shown in the following excerpt.
`
`5/12/2996
`5/2/2006
`5/2/2006
`5/2/2906
`5/3/2006
`
`:
`:
`:
`:
`:
`
`431339 R1-061111.219
`174661 R1-661112.219
`71687 R1-961114.zip
`93632 R1-661115.219
`231279 R1—661116.ziQ
`
`(Ex. 7 at I.) The text “R1-061 1 l4.zip” is a link that, when selected, initiates a
`
`download of a ZIP file titled RI-O61 I 14.zip.
`
`I downloaded and opened this ZIP
`
`file and found that it contains a single Microsoft Word file, a true and correct copy
`
`of which is attached as Exhibit 8.
`
`I compared Exhibit 8 to Exhibit 6, the Word file
`
`ZTE/HTC
`Exhibit 1015-0006
`
`6
`
`

`
`in the attachment that I received from Mr. Hiramatsu on May 2, 2006. and found
`
`that those two exhibits are identical.
`
`1].
`
`In the excerpt above, there is also a date stamp (5122006) to the left of the
`
`link to R1-061ll4.zip. Based on my 10 years of experience as a delegate for WG1,
`
`having uploaded more than 200 ZIP files to 3GPP’s publicly available server, I
`
`understand this date stamp to mean that R1-061 1 l_4.zip was uploaded to 3GPP’s
`
`publicly available website on May 2, 2006. and that any member of the public
`
`could have downloaded the ZIP file. extracted the Word document it enclosed. and
`
`viewed the contents of that Word document without restriction on May 2, 2006 and
`
`thereafter. I have no reason to believe this date stamp is inaccurate.
`
`12.
`
`I declare under penalty of perjury that the statements made herein are
`
`believed to be true based upon either my personal knowledge or to the best of my
`
`knowledge, information, and belief.
`
`Da:e:1=ebruaryi.2o16
`
`'
`
`3””-2% g
`
`4
`
`2
`
`ZTE/HTC
`Exhibit 1015-0007
`
`7
`
`

`
`ZTE/HTC
`
`Exhibit 1015-0008
`
`ZTE/HTC
`Exhibit 1015-0008
`
`8
`
`

`
`l6_.D
`1_J_._STS_ER'_b’
`Subscriber's Corner Email List
`
`'1
`
`Q’ 3GPP_TsG_RAN_WG1 Archives
`J
`
`3GP P_TSG_RAN_WG1@LIST.ETSI.ORG
`
`View:
`
`lleeseue: [F|ret|PrevioI.I|Ne:t|uet]
`Byfople:
`[Flrai
`|Prevlous |Ne:d |Lasl]
`ByAI.dhor:[fimt |Previous |Ne:d |Laal]
`Fort:
`ProporflonelForl
`
`‘Ax L|5TS$VAI'c|'IiIlIl
`‘_- 3GP|'_T3G_FIAll_\'lG1 Home
`J.-, 3GPl'_T8C|_RAll_WG‘l lflerch 2fl0IJ\'ee|\'3
`
`subject: Penaeotlc conlrlmtlonfor LTE
`From: Kahuhiko HIRAMATSU «flog in to u1n1eek]>
`Reply-To: Kalsuhlko HIRAMATSU qleq In to I.l'I'nael(]>
`Deb: Tue, 21 Mar 2006 15:51:25 +0900
`content-Typo: mulliparlnuhned
`texb‘phIn(23 lines). R1-noommp
`_ (23 lines) , R1-00019-I-.zlp(23 lines),
`.;_=.=:;-»- R1-0007'I5:ip (23 lines) . n2-
`namnzznp (23 lines). R1 .nom2zIp
`(23 linea)
`
`PerIelAflIcl1|nenI:e:
`
`Dear all,
`
`ficyarch Arcnwoss
`
`__ Log In
`«-09 3| PIIOIDIII
`
`Please -Find the attached Panasonic contributions on
`LTE.
`
`Q Search Archlvee
`
`Best regards ,
`Katsuhiko Hiranatsu
`
`3 Subeorlae or unauh-erb-
`
`R1-060792 Random access burst evaluation in E-UTRA
`uplink
`R1-B60793 Indication of combination between L1IL2
`control
`
`signaling and uplink data
`n1—B6B?94 channel Coding Structure for LTE
`dlnlink
`R1-B60795 Feedback of UE measurement for HIHO
`
`RAN1/2 joint:
`
`R2-966982 Channel coding Structure -For LTE
`dounlink
`(same contents as in R1-B69794)
`
`Top of Ileeeege ] Prevleue Page [ Pemlallne
`
`Archhaes
`
`December 2015, Wonk Il-
`Decenlber 2015. Week 3
`Decemllr 2015, Woek 2
`December 2015, Weeki
`I|ove¢IIber2o15,‘|!loek 5
`November 2013. Weak 4
`NovenIber2I.'I15.Week I
`NovenIIIr2015,Woek2
`November 2015. Week 1
`October 2015, Week I
`October 2015. Week 4
`October 2015, Noel! 3
`October 2015. Week 2
`October 2015, Week ‘I
`September 2B1 5, Week 5
`Sefilnbor 101 5, Hook 4
`September 2015. ‘Neel: 3
`September 2015, week 2
`Seplamber 2015. Week 1
`August 2015, Week 5
`Anguetiflfi, Wonk 4
`Au§uel.2015. Week 3
`Allguet 2015, Week 2
`Joy 2015. Week 5
`
`ZTE/HTC
`Exhibit 1015-0009
`
`9
`
`

`
`J uly 2015. Wick 4_
`July £015; Wool: 3
`J uly 2015. WIOII 2
`July 2015, Wank 1
`Jun! 2015; Wonk 5
`June. 2015, Well; 4
`J._ur.I.o_ :01 5'. W9:9_|.I:3
`Jum :01 5. Week 2
`Jum 2015. Walk 1
`[lay 2015. Week '5
`my 20.15, Wpek 4'
`Hly 2015, Walt 3
`May 201.5. Wash 2
`Hay'2015. Wink 1
`AprII.201. 5. Wank 5
`April 2015, Wank .4
`April 2015, Wick 3
`April 2015. ‘Noel: 2
`Apr]I.20_15. 'l_V_e;e'k 1
`March 2015. Week 5
`March 2015, Wank 4.
`march 2o15..wuk 3-
`Hlrch Z015, Wank 2
`Mirch 2015, Hook 1
`Fnhruary_Z015. ‘Neck 4
`l_=I_lIrua_ry‘20‘_I 5.
`3
`Fo'brua'ry 2015, weak 2
`Puhmau-y 21:15. max 1
`Jlmnry 2015, Wonk 5'
`January 2015, Wbok-4
`Ja nuary 201 5..Wu.k.'3
`J: nunry 20‘I5._WenIc 2-
`J1 nunry 20'l5..,'Woo|:-1
`Duuaumbjr 201 4. We'll! 4
`Doonrnlahr "201 .4. Wuk 3
`Donum [hr 2014. Week 2
`I:la_o.a_n1 bar. '2,01_4.:Wa¢k_ 1
`mmmbor 2014,.‘|N¢-Ik 5
`Hovimbor 20-‘I 4.'WI_Ok 4
`Howrn'I:|r 201 '4. WOIK 3
`l'l_cI'\'r§'rrlI_1_l_r Z014,-Wjlk 2
`Illuwrnlair 2014. Walk ‘I
`October 2014, Wegk '5
`Oclnbor 2014, Wash 4
`ocmhor 2014, w_oo1:_a
`Ociinbnr 201 4, Wick 2
`Ocinhnr 2014, Wick‘ 1
`septum bar 2014, Wall: 5
`.sopt'aniuarzo14.wu|_:4
`septum her 2014. Week 3
`Sdptumbsr 2014, Wank 2
`Septumbar 2014. Wopk 1
`August 2014. Walk 5
`August-2014. Walk 4
`August 2014, ‘Will: 3
`Aufllast 2014. Wdlk 2
`August 2014. Walk 1
`July 2014. wo_a,k- :-
`..-| uly 2014, Wink 4
`July 2014, ll_\'Ie'k-3
`July 2llI4,.WIok 2
`July 2014. max 1
`June 2014. Wonk 5
`June 2014, weal; 4
`Juno 1,014, Wepk-§
`J um 201:, W_iI_|: 2
`J.uI'l_l 2014, Well: 1
`In 2014, weak 5
`
`10
`
`ZTE/HTC
`
`Exhibit 1015-0010
`
`ZTE/HTC
`Exhibit 1015-0010
`
`10
`
`

`
`lily 20,1-I, Wick 4_
`May 1_I_l'l‘_4, Wool: 3
`May 2014. Wait 2
`iluy[2Il'I.4. Wink 1
`April 2014, wuk 5
`April 201.4. Wugk -I
`April 2014. WI.IQ|§._a'
`April 2014. Wu]: 2
`April 2014, Week 1
`[larch 2014. Week 5
`lurch 2014, weak 4
`Hnrch 2014. Week 3
`March 2014. Week!-
`Marcli 1014. Wick 1
`Fahruary 2014, W11-alt 4
`1'-‘abruary 2'l:|14,'o.9lo1_1l:-3
`Flhruary 2014. Week‘!
`Fuhrulrjr 2.014. Wool; 1
`.m.1'u1'ry‘ 1914.
`5
`Jlnulry 201-I._‘Weol1 4-
`..I_ar1uIr.y 2014, Wool: 3
`..lIrIulry'2014, 'WaIII:'2
`Jlnulry 1014, Won]: 1
`DIoIrI1'|I_l'I"201 3, Wall: 4
`nooombor 2013. Hook 3
`December-2013.-Wonk 2
`Dmnmbor 201 3. Weak» 1
`lilovarnlur 2013. Week 5
`l|la\ran1'I:Ir2013. ‘Wonk 4
`Novumhpr 2013, Wall: 3
`Nmrnh-r 20:13. v.v_-.-k-'2
`November 2013. Wait -‘I
`Octolior 2013. Wflck .5
`Ocuhur 2013, Wait 4
`-OI:tnhnr2DI3,Wnol: 3
`2.01 3,_V__U__a_Qlt.2'
`October 2013. Wait 1
`sopum bar 201 3,W_Ial1 s
`Soptom bar 201 3. Wonk 4
`Slfliln Mr 201 3'. Willi}
`2013, Walk"-2
`Scptlmhur 2013. Wonk 1
`Augustzfll 3__, man 5
`August 2013, Walk 4
`August 191 3, max 3
`Aug1ut2l'.I13, Wllk 2
`August 201:1, Wink 1
`July 2013-, Wool: 11
`July 201 3,.W'l.o|l. 3
`J uly 2013. ‘Neck 2
`..I1;1iy‘2llI3. weak 1
`Juno 2013. Walk 5
`J 11110 _a_o-_I 1_._ Wu Ital
`Jum 2013. _Wuk.3,
`Jun! 1013, W9'Ik_2
`June 201 3, Hell! 1
`my 2013, Wuk-'5'
`my 2013', wank 4
`my 2013, Wink 3
`my 2013, wool: 2
`HI]! 2llI3,.W|ak 1
`April 201 3‘, WIOK 5
`April 2013. Wick 4
`April 2013-. Wick-3
`Aprl_l_20I3. Wu]: 1
`April 2013. Wqok 1
`March ;o13.1_Nuk 5
`Hitch 2013. Week‘ 4
`
`11
`
`ZTE/HTC
`
`Exhibit 1015-0011
`
`ZTE/HTC
`Exhibit 1015-0011
`
`11
`
`

`
`March 2013.. Wick 3
`I.lIrch.!'lJ'1S.. Wuk'2
`March 2013. .W6Ik.1
`Fahruary. 2913. Ikfilk 4
`Fabruary 21113, WOIK 3
`February 2913, ’o\h;al;.2
`Fla'.hr'u,II'll 2013.._WgIk. 1
`January 2'01:-, ‘Neal; 5
`January 2013, Weak 4
`January 2015. Wail: 3
`January 2013, Weak 2
`January 2013. Weak 1
`December 2012. Weak 4
`D_0o_lI'mher 2012. weak .3
`Doolmlanr-2012, Wick 1
`Nuvomlur 2012. We-all: 5
`Nwam hr 201 2.'Waak 4
`Nwalrllaar 2012. Wall: 3
`NW'0.rI'(hajr 2012. W_e:!l( 2
`Hcvambar 201 2.'Wa'ak 1
`Octnbor 2012, Weak 5
`Ochdllr 2012, Wank 4
`Ocfflar 2012, Hank 3
`Ocinhar 2012, Want: 2
`Ocllobor 2012, Wool: 1
`September 2012-. Weak 5
`bar 2012, Walk 4
`Soflarnbar 2012, Wllk 3
`-5_a|:t|r|‘II:l_ar'20_12,V'loIlI:2
`Scpbamhar 2912. Wonk 1
`August 2012. Woaikl.
`August‘-2012. Weak 4
`Auauat 2012. Weak 3
`August 2012, ‘Hank 2
`August 2012, WIIK1
`_-July 2_'01Z..WI.o.k 5
`.-l‘ul'y 20‘l2,__Wajak 4
`July 2912, llllaal: 3
`July 2D12,_Waak 2
`J Illy 2912, Waok 1
`JHMZO1 2; W.o'I'|tT 5
`Juna 2012. Weak -I
`Juno 21112, Wank 3
`J.unO-1012; Wa'a‘kI2
`June 2012, weak 1
`May 201 2, Wank 5
`May 2012. Wick 4
`May 2012, W|’o_|_c 3
`May 2llI2..W'aTok'2
`May 2012. Week 1
`AprlI2012, wank:
`April 2012-. Waok 4
`April 2012, Wank!"
`Aprl|.2lI12. Wick}
`April 2012. week 1 _
`Hlrch 2012. Week 5'
`March 2012. Week 4'
`March 2012. Wank 3,
`flarc'h~ 2012-, Wool: 2
`llurch 2012. _V__VeeI_l: 1
`FahrI.llry' 2012, WOIK 5
`February 2012, weak 4
`Fahruary 2012‘. Wick 3
`February 2012, Wank 2
`Fahluary 2012, Weak 1
`.Lanua'ry 21:12. lllluls 5_
`January 2012. weak 4
`.I_a'nua'ry 201-2. would
`
`12
`
`ZTE/HTC
`
`Exhibit 1015-0012
`
`ZTE/HTC
`Exhibit 1015-0012
`
`12
`
`

`
`.lInua'r'y' _201_2.WoIk 2'
`.1-;.u.u-ry 2'0'I2.Wo_oI:1
`Docurnlnr 2011. W_0a'Ig1 5
`Docnmhor-2011. Walk 4
`D0oorn'bIr=2011. Wait 3
`Dgoambnr 2011, ‘(look 2
`DI'O'l_|'l.1|_II_r 201-I. Woak 1
`l'l0v0n1Iaor2011. Week 5
`IluvIrnhar'2011._WoIk -1
`Nuvambir 2011. weak 3
`Huvan1h,ar.201-1. Walk 2
`Il1wun1b0r201'1. Week 1
`October 2011, Weeks’
`O_c00b_0_r z'011.1_Mo.ak 4
`October 2011, Week 3
`October 201'1.Wook 2
`Ocinbbr 2011. Wonk 1
`Soplombur 2011. Wonk 5
`September 2011. W001: 4-
`S_optIl'nbar'2011. Walk 3
`sopurnbor 2011, would
`8Iptnm|_:11Ir2_011,WoIk 1
`August 2011, Wonk 5
`Augus1_z0_'11'. ‘WIIII1-4
`August 2011, Wool: 3
`August-2011.WIiIk 2
`Auaust.201-I, Wuk 1
`July 2011, Wale 5
`_.IuIy 2011, w-.-11.4
`J_u1y z011,_woo_k 3
`July 2011. WIIOIK-2
`July 2011. Wooki
`Juno 20.11.W00k5
`Juno 20!11,’a_1l'oIk'4
`Jun: 2011, Wank 3
`_-{uni _101fl..W°Ik 2
`June 2_G1'1_yWBIk 1
`may 2011. Week 5
`May 2011, Walk!
`my 2011, week 3
`My 2011. WI'_I_k .2-
`May 2011, wulc-1
`AprIl2_011. Wicks
`AprII.201'1. Week 4
`Apnll-2011-. WIOK 3
`April 201 1-, -'ll|ok'-2-
`Aprll2lI11. WIGK -‘|.
`March 2011. W0_|I_1:_5'
`Mlrcéh 2011. Week 4-
`March2011. Week 3
`March-101 1, Week 2
`March 2011 . Week 1
`Fahruary 2011. Won]: 4
`Fnhruary-2011. ‘We'll: 3
`FIbrI‘.IIry'2011,V\bIk2
`Fqbruary Z_0'1"| . Wo_0'k 1
`January 2011.‘Weok 5'
`JInuI1y2011.Woal: 4
`January 20‘_i1.Wook3
`._JanuI_ry1011.V_h'o0I1_2’
`January 201"l,Weok 1
`Dcoinilinr 2010. W0-0|: 5
`D0e0m|a0r201.0..W0'Ik -I
`Duc0rn'I:0r2010. Walls 3
`Duoorrylnr 2010. Week 2
`_DII:In1I:‘ur20'10.‘|_Vo'Ik 1
`HuvamIaar201.0. Week 5
`Hmmmhor-20-10. Wnk 4
`
`13
`
`ZTE/HTC
`
`Exhibit 1015-0013
`
`ZTE/HTC
`Exhibit 1015-0013
`
`13
`
`

`
`November 2010. Week"!
`Hevemblir 201 .O,.W°€Ik -2
`November 2010. Week 1
`Dcfliher 2010, Week '5
`October 2010,’ Week .4
`October 2010. Neck 3
`201.0.
`2
`October 2010, Week 1
`September 201 0. Week 5
`Sebternber 2010, Week 4
`5e|le'ml:er 201 0. Week 3
`Septelnber 201 0, Week!
`September 2010. Week‘!
`August "2010. Week 5."
`AUBUOK 201 0, Week 4
`August 201 0, Week 3
`August-201 0. Week 2
`August 2.010: Week 1
`July 2010. Wejelt '4
`July 2010. Week 3
`J my 291 0. Week 2
`July 2010, Week 1
`June 201lJ,Week 5
`J.lIl_II "101 0, W:e_l_l_I 4
`June 2010, Week 3
`June 2010, Week 2
`June 2010. Week 1
`June 10-‘! II
`Hey 2010, Week 4
`may zo1o,_woo_k 3
`Hay 2010. Wefelr-2
`Hey 2010. Week 1
`April 2.010. Week '4_
`April 2010. Week“;
`Aprll 2011:. Week!
`April 201 0_. Week 1
`March" 201 0
`February 2010, Week!
`February 2010, Week‘!
`February 2010. Week 2
`Fubrugary 2.010.; Week 1
`January 2010. Week 4-
`J1 nuery 2010, Well; 3
`Jlnuery 2010. Week 2
`January 2010, Week 1
`December "2009
`Nmneniher 2009, Well; ll
`NoverrlIIeI"2009, Week 3
`November 2009. ‘Week 2
`November 2009. Week 1
`October 20.00, Week I
`October 2009. Week 3
`-Dubber 2009. WILIII: 2
`2069. Week.i
`Sepbem ber 2009
`Aufllast 2000. week II-
`Auguet 2009. Week 3
`Auyuet 20,09‘, Week 2
`August 20-03;. Week 1
`July 2009 _
`June 2009, Week 4
`June zajoe, mix:
`J uee 2009. Week-2
`June 2009, Week 1
`May 2009, V_U'ee_l(_4
`Hey Z009. We'e_lr__3
`May 2009. Week '2
`Iley 2009, Week 1
`
`14
`
`ZTE/HTC
`
`Exhibit 1015-0014
`
`ZTE/HTC
`Exhibit 1015-0014
`
`14
`
`

`
`APl'iI.20'0.9'. WIQR 4
`APPII 200$. Wick"!
`Agrll 2009. Week!
`April :."0,09."I‘\."'I.I'_k 1
`Hitch 2000. WOIK 4
`Ilnrch 2009. Week 3
`I,|_I.l".c|'I 2.909.. W§Bk'2_
`March 2000. Week 1
`Fa bruary 20 09. Wink 4
`Fabruiry 2009. weak 1
`Fa bruaw 20 09. ‘Neal: -2
`Fa bruary 20 00. ‘Neck 1
`Jnnmry 2009. Weak 4-
`January 1009'. Week 3
`J-Inulry 2000. Wool: 2'
`Jlnuury 2000, ‘Wonk 1
`Beam liar 2003
`November 2000. Wuk -I
`I'l¢V'O.l'I'[hIIr 2008. 'W_0:!lt -.3
`Novlrnblr 2000_.'WI-bk 2
`Hmqmhr 2000. Week 1
`Ochghor 2000
`5I|fl_Il'll bar'2.0fl8, Wank 4
`3'|pft_Im_I:_n'r 2000. Walk 3
`Soptim bar 2000. Wonk 2
`Sjflom bbr 200Zl._WcIk 1
`August 2008. Wuk 4
`Auuuot‘2000. Wall: 3
`August-2000, WIIK 2
`August 2000. wopk 1
`July 2008
`_
`_
`June. 2000. weak 4
`J um -20.08. Week 3.
`J urn 2000'. Wuk-2
`Jun: 2000. Walk 1
`Ml'y'2:008'.
`«I
`Hay 2000'. Wniakl.
`my 290:, week 2
`May 2008, Wonk-1'
`April 2008. Wick 4
`APrll_200.8. Wupk '3
`April 2000. Walk 2-
`April gong. week 1
`MIrc‘h' 2000. Wink"-4
`Harsh 20.00. [|!_oak'3=
`Mlrbjll 200.8, Wllk 2
`March 2005. Wonk 1
`Eu bruary 20 08. W:-o__I( 4
`Fuhruary 20.00. ‘Neck 3
`Fa bruary 2000. weak 2
`February 2008, Walk 1
`January 200B._W9ak 4
`J": I"l|'.|‘Il_'y';oo3__. Wank 3
`January 2003. Wool: 2
`J: nm'ry- 2003. We'll: 1
`Ddoombnr-Z001
`Hovomlaor 2001. Wnk -4
`Hwomhnr 200-'I.'Wnk-3
`Novurnlabr 20.01. Weak 2
`_NOVIll'l_IlB_f_ 3007. Week 1
`Qcfinbor 200?, Weak.-0
`Ocmbor 2001, men
`October 2007. Wonk 2
`Ocfiubor 2007, Wonk 1
`septum bar 2007
`August 2007. Wu kl-
`August 2001. ‘Monk 3
`August 2007. Walk 2
`
`15
`
`ZTE/HTC
`
`Exhibit 1015-0015
`
`ZTE/HTC
`Exhibit 1015-0015
`
`15
`
`

`
`M0089 2001. Wuk 1
`Jul’! 20.07
`June 2007, Wank 4
`Junl 2007, Walk-3
`Jl.ll'lI 2007, Won It-2
`June. 2007. Neal: 1
`flay 2001'. Wlleflk 4
`may 2007, would
`May 2007. Week 2
`May -2001’, Week 1
`Apr|l1_00T:. Week 4
`April 2001. week 3
`Aprll 2001'. Waek 2
`April 20.01. Wnfik 1
`Illrch 200-'f_. weak 4
`March 2001'. Week 3
`lhrch 2007. Wank 2'
`Hitch 2007. Week 1
`Fe_h_ruary_'20_0T. W.lI_lt 4
`February 2007. weak 3
`Fubruary 2007. “link 2
`Fubruary 200?, ‘Wonk 1
`.1: many 2007, Wall: 4
`January 200?, ‘wool: 3
`January 2007. Week:
`J_a n_IL:|_ry-2007, Week 1
`Dumrnhor 2006
`Nuvnmhqr 2003.-Wool:-4
`lilavunihur 2000. Wonk 3
`Novumhpr 20,06. Wall: 2
`Hhvumhqr @006. Wouk 1
`October 2006, Week 4
`October 2003. W901: 3
`Ocubur 2008. Week 2'
`Ontnhnr 2000, wax-1
`Sblihm her 2000.
`A_"llL’Iat. 2'0,4‘I__B, ‘fink 4
`August 2003,. Wu |_:.3
`Auuustr2003.'Wuk 2
`August 20 08, Walk 1
`.-I llly 2000
`J uril 2000
`May 2008, Wqqk-4
`May 2006; Wick-.3
`flay zum, w_o'ok.z
`Mly 20.00, WIok'1
`Aprll 2006
`March zon§,.wu|_:_ 4
`March 2006. Weak-3
`March zoflfilweek 27
`Ilnrch 1000. Week 1
`Fa bn1_a_ry 2000. Wink -1
`Fa hruary 2000. Win]: 3
`Fa bruary-20.00. Wail: 2
`Fa
`20 06, ‘Monk 1
`Jinuary 20.00
`Dooomhor 2005
`Huyomhnr 2005
`October 2005, Wonk 4
`.°=i°b°.f 3395: WIN‘ 3.-
`Qcfinbor 2005, Week!
`Ocmbor 2005-, Waak:1
`Soptorn bar 2005
`August 2005, weak 4
`August 2005, Walk 3
`August 2005. ‘Hank 2
`August 2005. Wonk 1
`July-2005
`
`16
`
`ZTE/HTC
`
`Exhibit 1015-0016
`
`ZTE/HTC
`Exhibit 1015-0016
`
`16
`
`

`
`J um‘ 2005
`may 300:
`April 2005'
`March 2005
`F0 bruary 20 05.
`Junulry 1005
`0uo'g.m.I.:o_r 2004
`Nuvombor 2004
`-Ocinbar -2004
`Septumbar 2004
`August 20.04
`July 20.04
`Juno" 1004
`P0302004
`AprlI.2004
`March 2004
`Flhruary 2004
`JI nuary 2004
`Dofilrlthofr 2003
`Navornlaor 2003
`Octnbor 2003
`septum bur 2.0.03
`August 2003
`July 2003
`J am 1003
`IN 390.3
`April 20.03
`March 2003.
`Fchrulry 2003
`Jarjuary 2003
`Do_oo'm_l_nr 2002
`November 2002
`Octobor 2002
`-septum bgr 2002.
`August 2002
`.J my 2002'
`J'uno‘2'002'
`May 2002
`Aprll 2.002-
`Mlfch 2002
`Fubrugqri 2.002
`January 2002
`December 2001
`Nainmbnr 2001
`October 2001
`50|:IhI'nh|r»200‘I
`August 21: n1 '
`-.1|I|v— 2.°‘!". .
`Jun: 2001
`May 2001
`April 2001
`March 1001
`Fabruai-y_ 2001
`January 2001
`Daoamlnr 2000
`November-20.00
`October 2000
`septum bar 2000
`August 2000
`July 20.00
`J um 2000
`may 2000
`A;p‘r|I 2000
`March 2.000
`F_ubI'uary_2000
`J.ITIua'ry 2000 _
`Dacacmlaar ‘I000
`Haumhor 1000. Week 4
`
`17
`
`ZTE/HTC
`
`Exhibit 1015-0017
`
`ZTE/HTC
`Exhibit 1015-0017
`
`17
`
`

`
`Nunn1hnr1!9!.'Wu'nk 3
`IlaumhIr1'99!'.Wuk2
`Huvunhpr1I09.’Ilnlr1
`octqbnr 1IOl
`Sopbmbor 1000
`AI.uIM19I:U
`J_Ily1II9
`Jun 19!!
`Hay 1§B9
`Aprnum
`flIn:II1I99
`
`Flhrunry 195!
`January 1890 _
`DUOIlflKl'1I.I
`
`
`ATOM | R331 0]
`
`LI§T.EI'8l.OR0
`
`VOX
`
`ZTE/HTC
`
`Exhibit 1015-0018
`
`18
`
`ZTE/HTC
`Exhibit 1015-0018
`
`18
`
`

`
`ZTE/HTC
`
`Exhibit 1015-0019
`
`19
`
`ZTE/HTC
`Exhibit 1015-0019
`
`19
`
`

`
`TSG-RAN WG1 Meetin
`Athens, Greece,
`
`his
`
`R1 -060792
`
`Source:
`Title:
`Agenda Item:
`Document fOl'l
`
`Panasonic
`Random access burst evaluation in E-UTRA uplink
`10.2.3
`Dl50l.l5Sl0f'|
`
`1.
`
`Introduction
`
`Random access burst is used for the initial physical connection on initial cell access, handover and the resource
`allocation when the UE uplink has not been time synchronized. Several discussions on random access burst to
`achieve short initial physical connection setup have also been reported in [4] - [7] . Random access burst sub-
`Frame may be composed of a preambte part and a message part. We evaluate the preamble performance. Based
`on the evaluation results. we discuss the inclusion of message part on random access burst.
`
`2. Discussion
`
`2.1. Random access burst requirements
`In random access burst structure design, the following requirements have been considered [1] [3] - [I0] .
`
`I
`
`I
`
`-
`
`-
`
`Reliable acquisition ofpreamble
`
`Estimation of arrival timing
`
`Reduction in the whole process delay
`
`To minimize the usage of time—frequency resources regarding spectrum efiiciency
`
`The most important requirement ofthe above is reliable acquisition and estimation of arrival timing because the
`success rate of random access burst attempt should be high enough. The inclusion of message part on random
`access burst has been considered to shorten physical connection setup delay [4] - [7] .
`
`2.2. Discussion on preamble length
`In TR [2] . E-UTRA is required to support at least 30km cell size. Therefore. we showed the link budget and
`achievable number of bits per TTl (0.5ms) to estimate how many bits can be contained on random access burst
`in [[0] . The result would be useful in the case coverage is critical although the result is still preliminarily. On
`the other hand, we also need the discussion in the case that interference is critical. Ref. [6] reports that
`approximately -I3 dB and -18 dB ofthe average received EsfNo were derived from the system level evaluation.
`As mentioned above, the most imponant random access burst functions are reliable acquisition and estimation of
`arrival timing. For these reasons, first, we evaluate the required preamble length that corresponds to the required
`average received Es/No. Next we discuss the possibility of the inclusion of message part.
`
`in the preamble evaluation. we assume the followings:
`
`a
`
`I
`
`Random access burst TTI is a multiple of 0.5msec. Preamble. guard time and possibly message part
`share a random access burst TTI
`
`Random access burst is tirneffrequency multiplexed with other channels [3] [4] .
`
`-1/7-
`
`20
`
`ZTE/HTC
`
`Exhibit 1015-0020
`
`ZTE/HTC
`Exhibit 1015-0020
`
`20
`
`

`
`Prea mble structure
`
`A preamble sequence should have a good auto-correlation and good-cross correlation. General chirp-like {GCL]
`sequence has been considered to satisfy these requirements [5] [S] [9] . In our preamble performance evaluation,
`Zadoff-Chu CAZAC sequence [[3] , a special case ofGCL sequence, is used. RACH preamble structure is
`shown in Figure I.
`We evaluated l.25MHz and 5MHz as transmission bandwidth ofthe random access burst.-
`
`M Reetition M=3 200u I? 467us l'14 933us I28 1867us
`
`CAZAC sequence
`N=m1 25MHZ)‘ N=2Q3{5MHZ)
`512 samples (EEVETUS)
`
`BB sample
`
`CAZAC sequence
`
`CAZAC sequence
`
`remaining sa
`
`le
`
`Random access burst TTI length = 0.5 I 1.0! 2.0 ms
`
`Figure I — preamble structure
`
`Performance of preamble
`
`The simulation parameters are shown in Table 1. As preamble perfomtance evaluation criteria, we used false
`alarm and miss detection probability to the average received Esme. The definition is as follows:
`
`a
`
`False alarm (Pfa): the probability of a particular code being detected when nothing. or different code was
`transmitted
`
`Miss detection (Pmd):
`transmitted
`
`the probability of a particular code not being detected when the code was
`
`Although time domain preamble detection would also possible, in our evaluation, the RACH preamble detection
`is performed in frequency domain. which is similar to the detection algorithm described in [S] .
`
`1. Repeated CAZAC sequences ofthe received signal are combined in time domain.
`2. The combined CAZAC sequence is processed by FFT.
`3. A transmitted CAZAC code is detected by using coherent detection in frequency domain.
`4. A delay profile response is obtained after IDFT processing.
`
`Transmission Bandwidth
`
`RACH TTI length
`
`Length 01°C/’~ZAC Sequence (N)
`
`Repetition factor (M) of
`CAZAC sequence
`
`Table I — Simulation parameters
`
`l .25MHz
`Localized FDMA
`0.5 rnsf l.0ms / 2.0ms
`CAZAC sequence (Zadoff-Chu CAZAC[l 3] )
`
`(total preamble length: 200usec)
`3
`(total preamble length: 467usec)
`7
`14 (total preamble length: 933usec)
`28 (total preamble length: l867usec)
`
`Coherent detection in freq uency-domain
`Preamble detection in time-domain (after IDFT)
`
`channel model
`
`ZTE/HTC
`Exhibit 1015-0021
`
`21
`
`

`
`Figure 2 and Figure 3 illustrate the miss detection probability (Pmd) to the average received EsfNo of l.25MHz
`and 5MHz bandwidth to achieve the false alarm Pfa = l0"l under AWGN channel and TU l20knu’h, respectively.
`
`10”
`
`,
`.
`Bandwidth. 5MHz
`Channel: AWGN
`3 repetition (2Cll.lLlSl
`7 rep-eution(467usl
`I4 repetilion[933us}
`28 repetititsnt l86'Jusl
`
`Bandwidth: l.25MHz
`Channel: AWGN
`——-l—— 3 repetitinntlfluusl
`--A-- Frepetitiont-16‘lus)
`--fi-- l4 repelilion(933Lis}
`-—-A—— 28 repetitiontlsmusl
`
`
`
`Missdetectionprobability(Pmd)
`
`
`
`
`
`._- 3.
`
`Ja-
`-35
`
`-30
`
`-25
`
`-20
`
`-l 5
`
`-5
`
`Average received EsfNo [dB]
`
`Figure 2 Miss detection probabilit)'(Pn1d) to the average received Es/No (AWGN}
`0
`
`=_‘
`‘f
`‘
`=
`I‘
`‘ =l‘=
`Fasfifiarmlf f‘;
`‘
`'
`‘
`'
`
`=
`
`l
`
`3 Bandwidth:5MHz
`* Channel: TU ]20km/h
`—I— Srcpclitiontltlous}
`—I— ‘fret!-e1ition(4t':7us}
`—I— |4repe1i[ion[933us}
`—D— 23 repclition(lSt‘i7us)
`
`Bandwidth: 125MHz
`Channel: TU l20kmfh
`--A-- 3 rcpelilinntlllous}
`--I-- 7 repelilion:46'.-'us}
`--I-- 14 repelilion{933us}
`--A-- 28 rep-:liliorI(I867u5)
`
`10
`
`GEQ
`
`.
`\-—i
`
`.33
`Eas
`..I::
`EQ.
`'50an0-4
`tn
`‘'0
`U]
`. 52
`E
`
`CO
`
`-5
`I -10.
`-15 I
`-25. Q20“
`Average received ES/N0 [dB]
`
`Figure 3 Miss detection probability (Pmd) to the verage received Esr’No (TU lzflkmlh}
`
`Target value ofthe false alarm is S l()'3 and the target value ofrniss detection is S 10': and 10"‘ in WCDMA [I I] .
`We think similar target also would be required in LTE. Therefore, ifwe use the same target values from the
`above results, we can derive the required preamble length to fulfill the average received EsfNo. The required
`preamble length in 1.25MHz bandwidth is illustrated in Figure 4 to the average received EsfNo to achieve Pmd 2
`I04 and Pmd 5 10': with false alarm Pfa = 10"]. Figure 5 shows the case of SMHZ bandwidth.
`
`ZTE/HTC
`Exhibit 1015-0022
`
`22
`
`

`
`Bandwidth: l.25Mllz
`—o— Pmd=l0"‘(AWGN)
`—o— Pm:I=10'3(AwGN)
`
`—-+—- Pmd=10"(Tui2-uknvh)
`——+—— l’md=l0’3(TUl20kmlh)
`
`——-o-—- Pmd=I[}':'(Tl,l|20krn.lh)
`—-+-- Pmd=l0'3(TU|20km.lh)
`
`[ms] 3 U-
`
`
`Requiredpreamblelength
`
`
`
`
`
`
`‘1125
`
`-5
`140'
`-25
`I-20‘
`Average received F.sfNo [dB]
`
`'0
`
`Figure 4 Preamble length to ESINO of false alarm probability = I0“ (1.25MHz)
`Bandwidth: 5MHz
`—o— Pmd:10'3 (AWGN]
`’ —o— 1=md=i0'1(AwGN)
`
`
`
`Requiredpreamblelength[ms] 3 (II
`
`0130
`
`-l0
`-I 5
`-20
`-25
`Average received EsfNo [dB]
`
`-5
`
`Figure 5 Preamble length to Es/No of false alarm probability = ID“ (SMHZ)
`
`According to [6] , approximately -13 dB and -18 dB ufthe average received EsfNo were derived from the system
`level evaluation for the ]SD 500m and l'?32m, respectively, when using open-loop TPC‘ and SMHZ transmission
`bandwidth. Table 2 shows preamble length required for -l3dB and -l 8dB of Es/‘No under AWGN and
`TUl20km/h.
`
`Table 2 Required preamble length to the average received EsINo (SM Hz bandwidth}
`
`
`
`-13 dB (ISD=500m)
`
`-I 8 dB (ISD=l732rn)
`
`l-repetition
`(67 usec)
`3-repetition
`(200 usec)
`
`2-repetition
`(I33 usec)
`4-repetition
`(267 usec)
`
`5-repetition
`(333 usec)
`l4-repetition
`(933 usec)
`
`7-repetition
`(467 usec)
`28-repetition
`(I867 usec)
`
`-4/7-
`
`23
`
`ZTE/HTC
`
`Exhibit 1015-0023
`
`ZTE/HTC
`Exhibit 1015-0023
`
`23
`
`

`
`In this evaluation. only one preamble is transmitted. If multiple preambles are transmitted and multiple
`preambles are also received at the same time, additional preamble length would be required due to multiple
`access interference [MAI].
`
`2.3. Random access procedure
`For non—synchronized random access procedure, we introduced the four methods in the Denver meeting [10] .
`We extended the discussion to following five methods. In the figure "preamble" couid be randomly chosen
`signature sequence
`
`UE
`
`Node B
`
`Random access burst
`(preamble + msnurce re ucst + Data)
`
`Random access burst
`(rcamblc + resource re ucst]
`UL resource allocation
`
`Node B
`
`Random access burst
`( rcamblc]
`UL resource allocation
`
`Node B
`
`SUCH (lit. data}
`
`SDCII (i'ult resource re ucst + lJl. data )
`
`Random access burst
`( reamble + resource re uest]
`UL resource allocation for resource re uest
`
`Node B
`
`Random access burst
`( reamhle]
`UL resource allocation for resource re uest
`
`Node B
`
`SDCH (full resource rt: ucst]
`U]. resource allocation
`
`SDCE l(U]. data)
`
`Method D
`
`SDCII ( full rcsourcc re ucst)
`UL resource allocation
`
`SDCI |tUl. datal
`
`Method F.
`
`Figure 6 Initial resource allocation sequence
`
`- Method A
`
`The random access burst contains preamble, resource request and data. The delay for data transmission
`could be shortest.
`
`- Method B
`
`The random access burst contains preamble and resource request. The resource request could tell the amount
`of UE buffer and/or transmitter status. We assume only one or a few bits for this. The allocated amount of‘
`UL resource could be based on this resource request. The actual data is transmitted after one round trip time
`{RTT).
`- Method C
`
`The random access burst contains preamble only. The allocated amount of U L resource could be based
`without UE buffer and/or transmitter status. Tltercfote, the uplink resource allocation is not so accurate and
`could be waste of time-frequency resource in the uplink. The actual data is transmitted after one RTT.
`- Method D
`
`ZTE/HTC
`Exhibit 1015-0024
`
`24
`
`

`
`The random access b