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 MA WEI
`
`Case No. IPR2016-00757
`
`SAMSUNG 1017-0001
`
`SAMSUNG 1017-0001
`
`

`
`1.
`
`My name is Ma Wei. I am a Standard Engineer at ZTE Corporation. I have
`
`been employed by ZTE Corporation since 2008.
`
`2.
`
`Since 2003, I have served as one of ZTE’s delegates to the Third Generation
`
`Partnership Project (“3GP ”) in subgroups of 3GPP's Technical Specification
`
`Group - Radio Access Network (“TSG-RAN") known as Working Group 2
`
`(“WG2”) and Working Group 5 (“WG5”).
`
`3.
`
`In 2008, I attended WG2’s meetings and subscribed to WG2’s reflector list
`
`(3GPP_TSG_RAN__WG2@list.etsi.org), through which I both sent and received e-
`
`mail messages. Since at least early 2009, I have also attended WG5’s meetings
`
`and subscribed to WG5's reflector list, through which I have sent and received
`
`hundreds of e-mail messages. In general, before each Working Group meeting that
`
`I attended, I received e-mail messages from delegates of other companies through
`
`that group’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:l/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.
`
`
`
`SAMSUNG 1017-0002
`
`

`
`4.
`
`As a 3GPP delegate, I sent e-mail messages submitting technical documents
`
`on ZTE’s behalf to WG2’s and WG5’s reflector lists before the meeting for which
`
`the documents were submitted for discussion. I also uploaded technical documents
`
`to 3GPP’s publicly available Website before the meeting for which the technical
`
`documents were submitted for discussion.
`
`5.
`
`As a delegate for WG2, I have also regularly accessed the location on
`
`3GPP's website storing technical documents submitted to WG2. That location is
`
`available at the uniform resource identifier
`
`<http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/>, which I refer to in this declaration
`
`as “WG2’s public directory.” Since February 2008, I accessed WG2’s public
`
`directory in several ways, such as, for example, by entering the uniform resource
`
`identifier of WG2'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 WG2’s public directory. Regardless of which method I used
`
`to access WG2's public directory, I never encountered a password requirement or
`
`any other restriction that would prevent me or a member of the general public from
`
`accessing WG2’s public directory or any intermediate location. Based on my 7
`
`years of experience as a 3GPP delegate, since 2008 to the present, any member of
`
`the public could freely access WG2’s public directory, browse it, and download
`
`technical documents stored to it without restriction.
`
`SAMSUNG 1017-0003
`
`SAMSUNG 1017-0003
`
`

`
`6.
`
`As a delegate for WG2, I also routinely consulted 3GPP technical
`
`specifications. In my experience, since I started as a delegate in 2008,
`
`specifications have been made available on 3GPP’s website to any member of the
`
`public without any restrictions. In preparing this declaration, I accessed the
`
`location on 3GPP’s website where different versions of the technical specification
`
`TS 36.321 are made available. That location is available at the uniform resource
`
`identifier <http://www.3gpp.org!dynareport/3632l.htn1>, which I refer to in this
`
`declaration as “3GPP’s public 36.321 specification site.” I accessed 3GPP's public
`
`36.321 specification site without any password or any other restriction. Attached
`
`as Exhibit 1 is a true and correct copy of a printout of 3GPP’s public 36.321
`
`specification site as I accessed it. Exhibit 1 provides links to the different versions
`
`of TS 36.321, along with dates on which those versions were made available to the
`
`public. For example, Exhibit 1 provides a link to version 8.2.0 of TS 36.321 and
`
`shows that this version was made available on June 17, 2008. Based on my 7 years
`
`of experience as a 3GPP delegate, having routinely accessed versions of 3GPP
`
`technical specifications shortly after they became available to me and members of
`
`the public, I understand" the June 17, 2008 date on Exhibit 1 to be accurate and
`
`have no reason to dispute its accuracy.
`
`7.
`
`In preparing this declaration, I selected the link to version 8.2.0, which
`
`initiated a download of a ZIP file titled “36321-320.zip.” I opened that ZIP file
`
`SAMSUNG 1017-0004
`
`SAMSUNG 1017-0004
`
`

`
`and found a single Word file titled “3 6321—820.doc.” Attached as Exhibit 2 is a
`
`true and correct copy of that Word file. I recognize Exhibit 2 as the version 8.2.0
`
`of 3GPP TS 36.321 that I had access to and had reviewed in June 2008 shortly
`
`after it was released.
`
`8.
`
`In preparing this declaration, I also accessed the location on 3GPP's website
`
`where different versions of the technical specification TS 36.300 are made
`
`available. That location is available at the unifonn resource identifier
`
`<http://WWW.3gpp.org/dynareport/36300.htm>, which I refer to in this declaration
`
`as “3GPP’s public 36.300 specification site.” I accessed 3GPP’s public 36.300
`
`specification site without any password or any other restriction. Attached as
`
`Exhibit 3 is a true and correct copy of a printout of 3GPP’s public 36.300
`
`specification site as I accessed it. Exhibit 3 provides links to the different versions
`
`of TS 36.300, along with dates on which those versions werelmade available to the
`
`public. For example, Exhibit 3 provides a link to version 8.4.0 of TS 36.300 and
`
`shows that this version was made available on March 20, 2008. Based on my 7
`
`years of experience as a 3GPP delegate, having routinely accessed versions of
`
`BGPP technical specifications shortly after they became available to me and
`
`members of the public, I understand the March 20, 2003 date on Exhibit 3 to be
`
`accurate and have no reason to dispute its accuracy.
`
`
`
`SAMSUNG 1017-0005
`
`

`
`9.
`
`In preparing this declaration, I selected the link to version 8.4.0, which
`
`initiated a download of a ZIP file titled "36300-340.zip.” I opened that ZIP file
`
`and found a single Word file titled “36300-840.doc.” Attached as Exhibit 4 is a
`
`true and correct copy of that Word file. I recognize Exhibit 4 as the version 8.4.0
`
`of 3GPP TS 36.300 that I had access to and had reviewed in March 2008 shortly
`
`after it was released.
`
`10.
`
`I attended WG2 Meeting #61bis, which was held on March 31 to April 4,
`
`2008, in Shenzhen, China. Before Meeting #61bis, delegates from companies
`
`circulated technical documents for discussion at this meeting. During Meeting
`
`#61bis, delegates also collaborated on and generated technical documents. All of
`
`these documents were stored to a publicly available location on 3GPP’s website
`
`that was and remains available at the uniform resource identifier
`
`<www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_61bis!Docsf>.
`
`11.
`
`In preparing this declaration, I accessed that location without any password
`
`or any other restriction. Attached as Exhibit 5 is a title and correct copy of a
`
`printout from that website as I accessed it. Exhibit 5 lists several ZIP files,
`
`including R2-08 1764. zip, as shown in the following excerpt.
`
`39028 R2-681766.219
`
`3/24/2068 7:45 PM
`3/25/2068 5:35 AM
`3/24/2008 10:39 PM
`3/25/2008 5:38 AM
`3/24/2608 10:41 PM
`
`16259 R2-081762.219
`34197 R2-081763.219
`137378 R2-081754.219
`8158 R2-—08l765.ziQ
`
`SAMSUNG 1017-0006
`
`SAMSUNG 1017-0006
`
`

`
`(Ex. 5 at 6.) The text “R2—08 1764. zip” provides a link to a ZIP file titled R1-
`
`08l764.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
`
`6.
`
`12.
`
`In the excerpt from the 3GPP website printout shown above, there is also a
`
`date stamp (3/24!2008) to the left of the link to R2-08l764.zip. Based on my 7
`
`years of experience as a 3GPP delegate, having uploaded ZIP files to 3GPP's
`
`publicly available server, I understand this date stamp to mean that R2-081764.zip
`
`was uploaded to 3GPP’s publicly available website on March 24, 2008 (before
`
`Meeting #61bis), 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 24, 2008 and thereafter. I have no
`
`reason to believe this date stamp is inaccurate.
`
`13.
`
`On April 23, 2008, after Meeting #61bis, I received an e-mail message from
`
`ETSI employee Joern I-{rause through WG2’s reflector list. Attached as Exhibit 7
`
`is a true and correct copy of Mr. Krause’s e-mail message as obtained from 3GPP’s
`
`public e-mail website, which is available at <https://list.etsi.org/>, with which I
`
`have become familiar as a 3GPP delegate. Like all other members of WG2, I
`
`received this e—mail message along with an attached ZIP file, which enclosed a
`
`Word document, a true and correct copy of which is attached as Exhibit 8.
`
`SAMSUNG 1017-0007
`
`SAMSUNG 1017-0007
`
`

`
`14.
`
`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.
`
`Date: March JL, 2016
`
`MG
`
`Ma Wei
`
`SAMSUNG 1017-0008
`
`SAMSUNG 1017-0008
`
`

`
`
`
`SAMSUNG 1017-0009
`
`SAMSUNG 1017-0009
`
`

`
`The Mobile Broadband Standard
`
`-I»‘I'®OE&*E18-olrlilil-"'-'s'\‘CcYs
`
`ABOUT 3GF'F'
`
`5[JL:t;i'ir<;atIor1t= Groups
`
`Spccilicalions
`
`ZGPP C?llI,'l'|d£1T
`
`Tecllliolugies-3
`
`NL:v.rs 3. E\a'E,’|'1l5
`
`Harm’.-:
`
`SllL‘£l!lI.1|.J
`
`CtJ:1l;!L;l
`
`3GPP Specification detail
`Go to spec numbering scheme page
`Backto seriesindex
`
`3GPP TS 36.321 (click spec number to see fileserver directory for this spec)
`
`Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification
`
`TSG IWG responsible: R2 (click TSGIWG to see its home page)
`Work item which gave rise to this spec: LTE-L23 (click Wt code to see Work Item details in die Work Plan)
`Work items which may have impacted this spec: cllclt here
`Rapporteur: STATHN. Magnus
`Specification required for: E~UTR.AN—based systems
`In the table below
`click meeting nurnberfor meeting details;
`click spec version nurnberto download that version;
`click SDO publication reference to download SDO transposed document.
`
`Release
`
`Freeze meeting
`
`Freeze date
`
`2015-12-11
`
`::
`
`::
`
`Re!-13
`
`Rel-12
`
`SP—?0
`
`event
`
`RP-T0
`
`SP-E5
`
`event
`
`RP—70
`
`version
`
`13.0.0
`
`available
`
`2016-01-14
`
`2014-09-17
`
`1:
`
`version
`
`available
`
`remarks
`
`12.8.0
`
`12.i".0
`
`2016-01-04
`
`2015-09-25
`
`remarks
`
`.
`
`.
`
`.
`
`.
`
`remarks
`
`500 publications
`
`ETSI
`
`click refto download
`
`-
`
`ETSI
`
`click refto download
`
`RTS-|'TSGR—0236321vc80
`
`RTSl'TSGR—0235321vc‘i'0
`
`RP-59
`
`RP-E-B
`
`RP-6?
`
`RP—66
`
`RF‘—65
`
`RP-64
`
`RP-64
`
`RP-63
`
`RP—62
`
`12.6.0
`
`12.5.0
`
`12.4.0
`
`12.3.0
`
`12.2.1
`
`12.2.0
`
`12.1.0
`
`12.0.0
`
`2015-El?-03
`
`2015-03-2?
`
`2015-01-05
`
`2014-09-23
`
`2014-0?-10
`
`editorial
`
`2014—0?—02
`
`2014-03-20
`
`2014-01-0?
`
`Rel-11
`
`SP-5?
`
`2012-D9-12
`
`::
`
`.
`
`.
`
`event
`
`RP—6?
`
`RP-63
`
`RP-62
`
`version
`
`available
`
`remarks
`
`11.6.0
`
`11.5.0
`
`11.4.0
`
`2015-03-2?
`
`2014-03-20
`
`2014-01-0?
`
`RTSl'TSGR—0236321vcE0
`
`RT3"TSGR-0238321vc5I0
`
`RTSJ"|'SGFl—0236321vc40
`
`RTSl'TSGR—0236321vc30
`
`RT3"TSGR-0238321vc21
`
`—
`
`ETSI
`
`click refto download
`
`RTSl'TSGFt—0236321vbf.i0
`
`RTSITSGR-023S321vb50
`
`vb-10
`SITSG -0236321R
`RT
`
`SAlVlSUNG1017- 010
`
`SAMSUNG 1017-0010
`
`

`
`remarks
`
`Rel-10
`
`RP-60
`
`RP-59
`
`RP-5-B
`
`RP-5?
`
`SP-51
`
`event
`
`RP—62
`
`RP—30
`
`RP—59
`
`RP-50
`
`RP-57
`
`RF‘-55
`
`RP-54
`
`RP-53
`
`F-{P-52
`
`RP-51
`
`RF‘-50
`
`11.3.0
`
`11.2.0
`
`11.1.0
`
`11.0.0
`
`2013-0?-03
`
`2013-03» 13
`
`2013-01 -03
`
`2012-09-24
`
`2011-03-23
`
`::
`
`.
`
`.
`
`version
`
`10.10.0
`
`10.9.0
`
`10.3.0
`
`10.?.0
`
`10.6.0
`
`10.5.0
`
`10.4.0
`
`10.3.0
`
`10.2.0
`
`10.1.0
`
`10.0.0
`
`available
`
`2014-01-0?
`
`2013-0?-03
`
`2013-03-13
`
`2013-01-03
`
`2012-09-21
`
`2012-03-10
`
`2011-12-21
`
`2011-10-03
`
`2011-03-24
`
`2011-04-0E
`
`2010-12-21
`
`Rel-3
`
`SP-46
`
`2009-12-10
`
`::
`
`.
`
`RTSJ"|'SGR—0236321vb30
`
`RTS|"|'SGR—0235321vb20
`
`RT5«"TSGR-023632111010
`
`RTSJ'TSGR—023632‘1\rb00
`
`ETSI
`
`click ref to download
`
`RTS.|'TSGR—0236321vaa0
`
`RTS.ITSGR—0236321va'30
`
`RTSJTSGR-0236321va50
`
`RTaI'TsGR-0236321va70
`
`RTSJ'TSGR—0236321\ra60
`
`RTSfl'SGR—0236321va50
`
`RTS:I'TSGR-023532111340
`
`RTSITSGR-023632111830
`
`RTSfl'SGR—0236321va20
`
`RTS-'T5GR—0236321 V810
`
`RTS.|"|'SGR-023E321va00
`
`ETSI
`
`available
`
`remarks
`
`click ref to download
`
`Rel-8
`
`event
`
`RP-55
`
`RP-54
`
`RF‘-53
`
`RP-43
`
`RP-47
`
`RP-46
`
`RP-45
`
`SP—-42
`
`event
`
`RF‘-55
`
`RP-54
`
`RP-53
`
`RP-43
`
`RP-46
`
`RP-45
`
`RP—44
`
`RP-43
`
`RP-42
`
`RP-41
`
`version
`
`9.6.0
`
`9.5.0
`
`9.4.0
`
`9.3.0
`
`9.2.0
`
`9.1.0
`
`9.0.0
`
`2012-03-13
`
`2011-12-21
`
`2011-10-03
`
`2010-06-13
`
`2010-04-21
`
`2010-01 -05
`
`2000-09-23
`
`2003-12-11
`
`::
`
`,
`
`version
`
`available
`
`remarks
`
`8.12.0
`
`3.11.0
`
`0.10.0
`
`3.9.0
`
`3.3.0
`
`8.?.0
`
`3.0.0
`
`3.5.0
`
`3.4.0
`
`8.3.0
`
`2012-03-13
`
`2011-12-21
`
`2011-10-03
`
`2010-06-13
`
`2010-01-05
`
`2009-00-20
`
`2009-06-13
`
`2009-03-23
`
`2009-01 -05
`
`2008-09-23
`
`RTS.I'TSGR—0236321v960
`
`RTSITSGR-0235321\1'950
`
`RTSI"|'SGR-0236321v-940
`
`RTSfl'SGR—0235321v930
`
`RTS.|'TSGR—0236321v920
`
`RTSITSGR-0235321v910
`
`RTS«"TSGR—0236321v000
`
`ETSI
`
`click ref to download
`
`RTSFTSGR-0236321v8c0
`
`RTS.|"|'SGR—0236321v3‘b0
`
`RTSrrSGR—0236321vBa0
`
`RTS.|"|'SGR—0236321vB90
`
`RTSJTSGR-0236321v33-0
`
`RTSTSGR-023332111370
`
`RTS.|TSGR—0236321v3-60
`
`RTS.|"|'SGR—0236321v350
`
`RTSTSGR-0233321vB40
`
`RT
`R
`SITSG -023S321vB30
`SAMSUNG 1017-0011
`
`SAMSUNG 1017-0011
`
`

`
`DTSIT SGR—0236321v820
`
`RP—40
`
`RP-39
`
`RP-38
`
`RP-36
`
`R2430
`
`R2-60
`
`R259b
`
`RF-37
`
`R2-59
`
`R2-58b
`
`R2-58b
`
`R2-58b
`
`8.2.0
`
`8.1.0
`
`3.0.0
`
`2.0.0
`
`1.3.0
`
`1.2.0
`
`1.1.1
`
`1.1.0
`
`1.0.0
`
`0.2.1
`
`0.2.0
`
`0.1.1
`
`0.1.0
`
`0.0.0
`
`2003-05-1?
`
`2008 - 03- 20
`
`200?-12-20
`
`200?-12-11
`
`RP-W091?
`
`R2—0?54B8
`
`R2—0?5243
`
`R2-(F5093
`
`2014-12-18
`
`R2-0?4-530
`
`200?—09-24
`
`F€F'-[F0633
`
`R2-073885
`
`RP: 0?3?1 5
`
`R2-[H2994
`
`R2— W291 2
`
`R2-0?2?10
`
`Change Requests for this spec: click here.
`Genealogy of this spec:
`
`anlecede nt(s}
`
`page generated from database: 201 6-01-19 17:46:51
`
`‘this spec
`
`36.321
`
`descend ant(s)
`
`ABILHJT RELEASES
`
`BROVVSE '3 ECHNOLUGFES
`
`Release 14
`Release 13
`Release 12
`Release 1 1
`Release 10
`Release 9
`Release 8
`Release ?‘
`Release 6
`Release 5
`Release 4
`Release 1999
`
`LTE—Adva nced
`LTE
`Carrier Aggregation Explained
`HetNet.I'SmaiI Cells
`NAS
`The Evolved Packet Core
`HSPA
`UMTS
`W-CD MA
`GPRS 8: EDGE
`
`SAMSUNG 1017-0012
`
`SAMSUNG 1017-0012
`
`

`
`
`
`SAMSUNG 1017-0013
`
`SAMSUNG 1017-0013
`
`

`
`V8.2.0 (2008-05)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`Evolved Universal Terrestrial Radio Access (E-UTRA)
`Medium Access Control (MAC) protocol specification
`(Release 8)
`
`TM
`
`Tlat‘ prcxcnt docllmtlnt has i:!t:I:11 developed within the 3"‘ (iencralion |’artnc:rs|1ip I‘rojz-:cl {3('il‘|‘ N} and Jnay he l‘urlht:r elalhurutcd for [he ptlrposcs oi‘ 3(il‘I‘.
`
`The prcxenl doCLlmt-:nL has not been suhiecl to any ilppftwill [}fl)E,‘t.‘SS by [he 3{iP1"0rga1I1ixa1tiona| Purlners and shall not be lI!'|pi|',‘I'|'lI3]'l1t:Li.
`'I'Iiis Specil'ICaliun is provided For future di.‘\«’Ci(l}’l’r'|‘It:l]l work within 3(il’l’oni_v, The ()rgani2;1lion2||
`|’arlncr!; accept no liaihilily for any use oi‘ 111 is Specification.
`Spccilicalions and regions lor implementation of [he .‘>(jPP '“ syslt.-in should be obtained via the SUPP Orgzmizalional |’a1nm:r5' Publications IZ)l‘l'1c::.=..
` -0014
`
`SAMSUNG 1017-0014
`
`

`
`Release 8
`
`2
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`Keywords
`UMTS, radio
`
`3GPP
`
`Postal address
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipoiis
`Valbonne - FRANCE
`Tel_: +33 4 92 94 42 00 Fax: +33 4 93 65 4? 16
`
`Internet
`
`http:Hwww.3gpp.org
`
`Copyright Notification
`
`No part may be reproduced except as authorized by written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`CC: 2008. 3GPP Organiziltional Partners {ARIB, ATIS, CCSA, |:"|'S[. T['A. TIC).
`All rights reserved.
`
`3GPP
`
`SAMSUNG 1017-0015
`
`SAMSUNG 1017-0015
`
`

`
`Release 8
`
`3
`
`3C-SPF TS 36.321 V8.2.0 (2008-05)
`
`Contents
`
`Foreword .......................................................................................................................................................... ..5
`
`1
`
`Scope ...................................................................................................................................................... ..6
`
`References .............................................................................................................................................. ..6
`
`Definitions and abbreviations ................................................................................................................. ..6
`6
`7
`
`l
`.2
`
`General ................................................................................................................................................... ..
`4.] Introduction
`4.2
`MAC
`4.2.]
`MAC
`4.3 Services
`
`4.3.]
`4.3.2
`4.4
`4.5
`
`Services provided to upper
`Services expected fromphysical
`Functions
`Channel structure
`
`TransportChannels
`4.5.]
`4.5.2 Logical
`4.5.3
`Mapping of Transport Channels toLogical
`4.5.3.1
`Uplinkmapping
`4.5.3.2
`Downlinkmapping
`
`MAC procedures .................................................................................................................................. ..
`Random Access
`Random Access Procedure initialization
`Random Access Resource
`Random Access Preamble transmission
`
`Random Access Response reception
`Contention
`
`._.
`
`555::
`
`4?
`
`Completion ofthe Random Accessprocedure
`Maintenance of Uplink TimeAlignment
`DL-SCH data transfer
`DL Assignment reception
`HARQ
`
`HARQ
`Disassembly and
`UL-SCHdatatransfer
`
`ULGrant
`HARQ
`HARQ
`HARQ
`Multiplexing andassembly
`Logical channel prioritization
`Multiplexing of MAC
`Scheduling
`Buffer Status
`Power Headroom
`PCH
`BCH
`Discontinuous Reception
`MAC
`MAC
`
`
`
`000000‘-JI--lG"\O'\G'\D\U‘I(.J1
`_——.—.—._..—-.—-_._—
`|*Jl\J|\Jl~Ji\JI~Jl\)l.‘-Jl‘-Jl\Jl\Jl\)—*—*-I1‘-P-I>.-LrJl.a~Jl‘\Jl\J—'—'—©@\-C2'0O
`
`Handling of unknown, unforeseen and erroneous protocol data
`
`3GPP
`
`SAMSUNG 1017-0016
`
`1
`2
`.3
`
`4 5
`
`.
`
`5.1.6
`5.2
`5.3
`5.3.]
`5.3.2
`
`5.3.2.2
`5.3.3
`5.4
`
`5.4.]
`5.4.2
`5.4.2.1
`5.4.2.2
`5.4.3
`5.4.3.1
`5.4.3.2
`5.4.4
`5.4.5
`5.4.6
`5.5
`5.6
`5.7
`5.8
`5.9
`
`5.)(
`
`SAMSUNG 1017-0016
`
`

`
`Release 8
`
`4
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`Protocol Data Units, formats and parameters ....................................................................................... ..24
`Protocol Data
`24
`24
`24
`MAC PDU (DL-SCH and
`MACControl 26
`
`I
`.2
`3
`
`6.1.3.4
`6. I .3.5
`6.1.3.6
`
`6. I .4
`6.1.5
`6.2
`6.2.]
`
`6.2.2
`6.2.3
`7
`1.]
`1.2
`
`Buffer Status Report MAC Control Elements
`C-RNTI MAC Control
`DRX Command MAC Control
`
`
`
`
`
`UE Contention Resolution Identity MAC Control
`Timing Advance MACControl
`
`Power Headroom MAC Control Element......................
`
`MAC PDU (transparent
`MAC PDU [Random Access Response}
`Formats andparameters
`MAC header for DL-SCH and UL-SCH
`
`26
`26
`26
`
`27'
`2?
`27
`
`28
`28
`29
`29
`
`30
`MAC header for Random Access
`30
`MAC payload for Random Access
`Variables and constants ........................................................................................................................ ..3l
`RNTI values
`32
`Backofl’ Parameter values
`32
`
`
`
`
`
`
`
`Annex A (informative):
`
`Change history ...............................................................................................33
`
`3GPP
`
`SAMSUNG 1017-0017
`
`SAMSUNG 1017-0017
`
`

`
`Release 8
`
`5
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`Foreword
`
`This Technical Specification has been produced by the 3"] Generation Partnership Project (3GPP).
`
`The contents ofthe present document are subject to continuing work within the TSG and may change following formal
`TSG approval. Should the TSG modify the contents ofthe present document, it will be re—re|eased by the TSG with an
`identifying change of release date and an increase in version number as follows:
`
`Version x.y.z
`
`where:
`
`x
`
`the first digit:
`
`I
`
`presented to TSG for infonnation;
`
`2 presented to TSG for approval;
`
`3
`
`or greater indicates TSG approved document under change control.
`
`3!
`
`the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
`updates, etc.
`
`2
`
`the third digit is incremented when editorial only changes have been incorporated in the document.
`
`3GPP
`
`SAMSUNG 1017-0018
`
`SAMSUNG 1017-0018
`
`

`
`Release 8
`
`6
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`1 Scope
`
`The present document specifies the E-UTRA MAC protocol.
`
`2
`
`References
`
`The following documents contain provisions which, through reference in this text, constitute provisions ofthe present
`document.
`
`0 References are either specific (identified by date of publication. edition number, version number, etc.) or
`non-specific.
`
`I
`
`0
`
`:1]
`
`:2]
`
`:3]
`
`:4]
`
`:5]
`
`:6]
`
`For a specific reference. subsequent revisions do not apply.
`
`For a non-specific reference. the latest version applies. In the case ofa reference to a 3GPP document (including
`a GSM document], a non-specific reference implicitly refers to the latest version ofthat document in the same
`Release as the present document.
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`3GPP TR 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer
`Procedures".
`
`3GPP TS 36.322: “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control
`(RLC) protocol specification".
`
`3GPP TS 36.323: “Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data
`Convergence Protocol (PDCP) Specification".
`
`3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA]; Multiplexing and
`channel coding".
`
`3GPP TS 36.2 I4: “Evolved Universal Terrestrial Radio Access (E-UTRA]; Physical layer:
`Measurements”.
`
`3
`
`Definitions and abbreviations
`
`3.1
`
`Definitions
`
`For the purposes ofthe present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
`term defined in the present document takes precedence over the definition ofthe same term, ifany, in TR 21.905 [1].
`
`Active Time: time during which the UE monitors the PDCCH for a PDCCH-subframe. Section 5.? defines the
`conditions for which a subframe is included as part ofActive Time.
`
`Contention Resolution Timer: Specifies the number ofconsecutive PDCCH-subfran1e{s) during which the UE shall
`monitor the PDCCH after the uplink message containing the C-RNTI MAC control element or the uplink message
`associated with UE Contention Resolution identity submitted from higher layer is transmitted.
`
`DRX Cycle: Specifies the periodic repetition ofthe On Duration Followed by a possible period of inactivity (see figure
`3.|-l below).
`
`3GPP
`
`SAMSUNG 1017-0019
`
`SAMSUNG 1017-0019
`
`

`
`Release 8
`
`7
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`4 On .D1.'f£J'fit)i? HI
`
`Op_.rmrrmiir_i'_fE:r DRX
`
`Iv
`
`L-'.F.'
`
`.\'.Ilifl'.l.|l mom'mJ'
`PUCC.-'.-’
`
`I
`
`4
`
`-IJRX (:}‘£‘.’t.’
`
`I»
`
`Figure 3.1-1: DRX Cycle
`
`DRX Inactivity Timer: Specifies the number of consecutive PDCCH-subframets] after successfully decoding a
`PDCCH indicating an initial UL or DL user data transmission for this UE.
`
`DRX Retransmission Timer: Specifies the maximum number of consecutive PDCCH-subframe{s} for as soon as a DL
`retransmission is expected by the UE.
`
`DRX Short Cycle Timer: This parameter specifies the number of consecutive subframe{s)the UE shall follow the short
`DRX cycle after the DRX Inactivity Timer has expired.
`
`HARQ RTT Timer: This parameter specifies the minimum amount ofsubframe{s} before a DL HARQ retransmission
`is expected by the UE.
`
`On Duration Timer: Specifies the number of consecutive PDCCH-subframets} at the beginning ofa DRX Cycle.
`
`RA-RNTI: The Random Access RNTI is used on the PDCCH when Random Access Response messages are
`transmitted. lt unambiguously identifies which time-frequency resource was utilized by the UE to transmit the Random
`Access preamble.
`
`PDCCH—sulJframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes.
`
`NOTE:
`
`A timer is running once it is started, until it is stopped or until it expires.
`
`NOTE: When defining On Duration Timer, DRX Inactivity Timer, DRX Retransmission Timer and Contention
`Resolution Timer, PDCCH-subframes and subframes including DwPTS are considered as subframes
`where the timer, ifrunning, shall be updated.
`
`3.2
`
`Abbreviations
`
`For the purposes ofthe present document, the abbreviations given in TR 21.905 [1] and the following apply. An
`abbreviation defined in the present document takes precedence over the definition ofthe same abbreviation, if any, in
`TR 21.905 [1].
`
`BSR
`C-RNTI
`
`CO]
`E-UTRA
`E-UTRAN
`MAC
`
`PHR
`P-RNTI
`RA-RNTI
`
`RNTI
`SI-RNT]
`SR
`SRS
`TB
`
`Buffer Status Report
`Cell RNTI
`
`Channel Quality Indicator
`Evolved UMTS Terrestrial Radio Access
`Evolved UMTS Terrestrial Radio Access Network
`Medium Access Control
`
`Power Headroom Report
`Paging RNTI
`Random Access RNTI
`
`Radio Network Temporary Identifier
`System Information RNTI
`Scheduling Request
`Sounding Reference Symbols
`Transport Block
`
`3GPP
`
`SAMSUNG 1017-0020
`
`

`
`Release 8
`
`8
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`4
`
`General
`
`4.1
`
`Introduction
`
`The objective is to describe the MAC architecture and the MAC entity from a functional point of view.
`
`4.2
`
`MAC architecture
`
`The description in this sub clause is a model and does not specify or restrict implementations.
`
`RRC is in control ofconfiguration of MAC.
`
`4.2.1
`
`MAC Entities
`
`E-UTRA defines two MAC entities; one in the UE and one in the E-UTRAN. These MAC entities handle the following
`transport channels:
`
`- Broadcast Channel (BCH];
`
`- Downlink Shared Channel (DL-SCH);
`
`-
`
`Paging Channel {PCH);
`
`Uplink Shared Channel [UL-SCH);
`
`- Random Access Channei(s) {RACH).
`
`The exact functions performed by the MAC entities are different in the UE from those performed in the E-UTRAN.
`
`4.3
`
`Services
`
`4.3.1
`
`Services provided to upper layers
`
`This clause describes the different services provided by MAC sublayer to upper layers.
`
`-
`
`-
`
`data transfer
`
`radio resource allocation
`
`signalling of Scheduling Request;
`
`4.3.2
`
`Services expected from physical layer
`
`The physical layer provides the following services to MAC:
`
`data transfer services;
`
`signalling of HARQ feedback;
`
`-
`
`-
`
`-
`
`- measurements (e.g. Channel Quality indication (CQ[)).
`
`The access to the data transfer services is through the use oftransport channels. The characteristics ofa transport
`channel are defined by its transport format (or format set), specifying the physical layer processing to be applied to the
`transport channel in question. such as channel coding and interleaving. and any service-specific rate matching as
`needed.
`
`3GPP
`
`SAMSUNG 1017-0021
`
`SAMSUNG 1017-0021
`
`

`
`Release 8
`
`9
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`4.4
`
`Functions
`
`The following functions are supported by MAC sublayer:
`
`- mapping between logical channels and transport channels;
`
`- multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to
`the physical layer on transport channels:
`
`-
`
`-
`
`-
`
`-
`
`-
`
`demultiplexing of MAC SDUs front one or different logical channels from transport blocks (TB) delivered from
`the physical layer on transport channels;
`
`scheduling information reporting;
`
`error correction through HARQ;
`
`priority handling between UEs by means of dynamic scheduling;
`
`priority handling between logical channels ofone UE;
`
`- Logical Channel prioritisation;
`
`-
`
`transport format selection.
`
`NOTE:
`
`How the multiplexing relates to the QoS ofthe multiplexed logical channels is FFS.
`
`The location ofthe different functions and their relevance for uplink and dovvnlink respectively is illustrated in Table
`4.4-1.
`
`Table 4.4-1: MAC function location and link direction association.
`
`MAC function
`Mapping between logical channels and transport channels
`
`UE
`X
`
`Multiplexing
`
`Dernultiplexing
`
`Error correction through HARQ
`
`Transport Format Selection
`Priority handling between UEs
`Priority handling between logical channels of one UE
`Logical Channel prioritisation
`Scheduling information reporting
`
`X
`
`X
`
`X
`
`X
`X
`
`eNB
`
`X
`
`X
`
`X
`
`X
`
`X
`X
`X
`
`Downlink
`X
`
`Uplink
`X
`X
`
`X
`
`X
`
`X
`X
`
`X
`X
`X
`
`X
`
`X
`X
`X
`
`X
`X
`X
`X
`X
`
`4.5
`
`Channel structure
`
`The MAC sublayer operates on the channels defined below; transport channels are SAPS between MAC and Layer l.
`logical channels are SAPs between MAC and RLC.
`
`4.5.1
`
`Transport Channels
`
`The transport channels used by MAC are described in Table 4.5.]-1 below.
`
`Table 4.5.1-1: Transport channels used by MAC
`
`3GPP
`
`Transport channel name
`Broadcast Channel
`Downlink Shared Channel
`Paging Channel
`Uplink Shared Channel
`Random Access Channel
`
`Acronym
`BCH
`DL-SCH
`PCH
`UL-SCH
`RACH
`
`Downlink
`X
`X
`X
`
`Uplink
`
`X
`X
`
`SAMSUNG 1017-0022
`
`

`
`Release 8
`
`10
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`4.5.2
`
`Logical Channels
`
`The MAC layer provides data transfer services on logical channels. A set oflogical channel types is defined for
`different kinds of data transfer services as offered by MAC.
`
`Each logical channel type is defined by what type ofinformation is transferred.
`
`MAC provides the control and traffic channels listed in Table 4.5.2-l below. When MAC uses the PDCCH to indicate
`radio resource allocation, the RNTI that is mapped on the PDCCH depends on the logical channel type:
`
`- C-RNTI, Temporary C-RNTI and Semi-Persistent Scheduling C-RNTI for DCCH and DTCH;
`
`-
`
`P-RNTI for PCCH:
`
`- RA-RNTI for Random Access Response on DL-SCH;
`
`- Temporary C-RNTI for CCCH during the random access procedure;
`
`-
`
`Sl-RNTI for BCCH.
`
`Table 4.5.2-1: Logical channels provided by MAC.
`
`Logical channel name
`Broadcast Control Channel
`Paging Control Channel
`Common Control Channel
`Dedicated Control Channel
`Dedicated Traffic Channel
`
`Acronym
`BCC!-I
`PCCH
`CCCH
`DCCH
`DTCH
`
`Control channel
`X
`X
`X
`X
`
`Traffic channel
`
`X
`
`4.5.3
`
`Mapping of Transport Channels to Logical Channels
`
`The mapping oflogical channels on transport channels depends on the multiplexing that is configured by RRC.
`
`4.5.3.1
`
`Uplink mapping
`
`The MAC entity is responsible for mapping logical channels for the uplink onto uplink transport channels. The uplink
`logical channels can be mapped as described in Figure 4.5.3.1-I and Table 4.5.3. 1-].
`
`CCCH
`
`DCCH
`
`DTCH
`
`___£.—>____
`
`ll‘
`
`U 1''
`pill
`
`Figure 4.5.3.1-1
`Logicczl chanarefs
`
`_ _ _ _ _ _ _
`
`_ _ _ _ _ _ _ __
`UL-SCH
`
`Q
`RACH
`
`Upfink
`'i"mnsport charms.-’s
`
`Table 4.5.3.1-1: Uplink channel mapping.
`
`Transport channel
`Logical channel
`CCCH
`DCCH
`DTCH
`
`UL-SCH
`
`RACH
`
`X
`X
`X
`
`3GPP
`
`SAMSUNG 1017-0023
`
`

`
`Release 8
`
`11
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`4.5.3.2
`
`Downlink mapping
`
`Tl1e MAC entity is responsible for mapping the downlink logical channels to downlink transport channels. The
`downlink logical channels can be mapped as described in Figure 4.5.3.2-I and Table 4.5.3.2-I.
`
`l')0wm’fmlr
`.’.ogica:’ culranirefs
`
`Drni-riliiik
`Transport cha.-mels
`
`
`
`BCCH
`
`CCCH
`
`DCCH
`
`DTCH
`
`D.
`
`D
`
` —
`
`BCH
`
`D
`DL—SCH
`
`PCCH
`
`{E
`
`PCH
`
`Figure 4.5.3.2-1
`
`Table 4.5.3.2-1: Downlink channel mapping.
`
`Transport channel
`Logical channel
`BCCH
`PCCH
`CCCH
`DCCH
`DTCH
`
`BCH
`
`X
`
`PCH
`
`DL-SCH
`
`X
`
`X
`
`X
`X
`X
`
`5
`
`MAC procedures
`
`5.1
`
`Random Access procedure
`
`5.1.1
`
`Random Access Procedure initialization
`
`The Random Access procedure described in this subclause is initiated by a PDCCH order or by the MAC sublayer
`itself. The PDCCH order or RRC optionally indicate a Random Access Preamble and PRACH resource.
`
`Before the procedure can be initiated. the following information is assumed to be available:
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`the available set of PRACH resources For the transmission ofthe Random Access Preamble and their
`
`corresponding RA-RNTIS.
`
`the groups of Random Access Preambles and the set of available Random Access Preambles in each group.
`
`the thresholds required for selecting one ofthe two groups of Random Access Preambles.
`
`the parameters required to derive the TTI window described in subciause 5.1.4.
`
`the power-ramping factor POW ER_RAM P_STE P.
`
`the parameter PREAMBLE_TRANS_MAX [integerfi 0].
`
`the initial preamble power PREAMBLE_ INITlAL_RECElVED_TARGET_POWER.
`
`the parameter Maximum number of Message3 HARQ transmissions.
`
`[Note that the above parameters may be updated from higher layers before each Random Access procedure is initiated]
`
`3GPP
`
`SAMSUNG 1017-0024
`
`SAMSUNG 1017-0024
`
`

`
`Release 8
`
`12
`
`3GPP TS 36.321 V8.2.0 (2008-05)
`
`The Random Access procedure shall be performed as follows:
`
`-
`
`-
`
`-
`
`-
`
`Flush the [Message3] buffer;
`
`set the PREAMBLE_TRANSMISSION_COUNTER to 1;
`
`set the backoffparameter value in the UE to 0 ms;
`
`proceed to the selection ofthe Random Access Resource (see subclause 5.1.2).
`
`NOTE:
`
`There is only one Random Access procedure ongoing at any point in time. lfthe UE receives a request for
`a new Random