3GPP TSG RAN WG1 Meeting #54bis
`Prague, Czech Republic, September 29 - October 3, 2008
`September 29 - October 3, 2008 I NTT DOCOMO, INC.
`
`R1-083679
`
`UL Layered Control Signal Structure
`in LTE-Advanced
`
`NTT DOCOMO, INC.
`
`Agenda item: 11
`Document for: Discussion and Decision
`
`docomo
`
`Samsung Ex. 1008
`
`1
`
`
`Prague, Czech Republic, September 29 - October 3, 2008
`September 29 - October 3, 2008 I NTT DOCOMO, INC.
`
`R1-083679
`
`UL Layered Control Signal Structure
`in LTE-Advanced
`
`NTT DOCOMO, INC.
`
`Agenda item: 11
`Document for: Discussion and Decision
`
`docomo
`
`Samsung Ex. 1008
`
`1
`
`
`
`Objective
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
` Proposed layered control signal structure in LTE-Advanced
`• Achieves high commonality with control signal formats in Rel-8 LTE
`• Uses layered control signal formats according to assigned
`transmission bandwidth to achieve efficient control signal
`transmission
`
` Investigate UL control signal structure for LTE-Advanced UE with
`wider Tx/Rx bandwidth capability
`
`docomo
`
`2
`
`Samsung Ex. 1008
`
`
`
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
`
`PUCCH Transmission Scheme
`for Rel-8 LTE UE
`
`docomo
`
`3
`
`Samsung Ex. 1008
`
`
`
`PUCCH Transmission Scheme for Rel-8 LTE UE
`September 29 - October 3, 2008 I NTT DOCOMO, INC.
`(cid:127) Should support PUCCH for Rel-8 LTE UE in symmetric and
`asymmetric bandwidth assignments (ref. R1-082999)
`• Symmetric bandwidth assignments
`Component carrier
`
`DL
`
`DL-U L Ii n ka_ge ,: :_-_- _-:_-_-_-_-::_-,-_-_-_-_-_-_-_-_- _-_-_-_-_-_-_-_-_-,,-_-_-_-_-_-_-_-_-_ -_-_-___ _
`
`I \
`I
`\
`
`I \
`I
`\
`
`I \
`I
`\
`
`/,..\
`I
`\
`
`: 1
`:
`:
`UL f
`\_~,: ___ ____...,_..__,- - - -_,~--------'T-''j
`• Asymmetric bandwidth assignments
`Component carrier
`
`(': PUCCH for
`\) Rel-8 LTE UE
`
`DL
`
`--------
`DL-UL 1·1nkage ,_-:_-__ -__ -_-----
`----- ---------~--------- -----
`' '
`' '
`
`'
`
`\
`
`I \
`
`I
`
`I
`
`:'\ PUCCH for
`\j Rel-8 LTE UE
`
`Application of different shifts
`(R1-082999)
`Samsung Ex.1008
`d ·~-.---.......----- - - - - - - - - - - - - - - - - - - - -~ 4
`
`
`
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
`
`PUCCH Transmission Scheme Candidates
`for LTE-Advanced UE
`
`docomo
`
`5
`
`Samsung Ex. 1008
`
`
`
`PUCCH Transmission Scheme Assumptions
`for LTE-Advanced UE
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
` In LTE-Advanced, PUCCH carries feedback signaling (CQI/PMI and
`ACK/NACK) for multiple assigned DL component carriers
` Investigate PUCCH transmission scheme for LTE-Advanced UE
`with wider Tx/Rx bandwidth capability
` Proposed scheme uses same PUCCH structure as that for Rel-8
`LTE
`• Basically, single-carrier transmission
`• 1 RB transmission bandwidth
`• Apply intra-subframe frequency hopping etc.
`
`docomo
`
`6
`
`Samsung Ex. 1008
`
`
`
`PUCCH Transmission Scheme
`for LTE-Advanced UE (1)
`• Two major approaches -
`(cid:127) Approach 1: Reuse PUCCH transmission scheme in Rel-8 LTE
`• Require multi-carrier (resource) transmission to transmit control signals for
`multiple DL component carriers within TTI
`Component carrier
`
`DL
`
`DL/UL linkage _ __.._-_-___ -_--
`
`----
`
`Multi-carrier
`UL
`transmission
`(cid:127) Approach 2: Use optimum transmission scheme for wider bandwidth
`• Single-carrier transmission can be applied, although new DL/UL linkage is
`required
`• New format (e.g., block spreading) is effective in carrying a large number of
`control signaling bits
`Component carrier
`
`DL
`
`llf
`11 Employing optimum
`~
`UL W~ ____ fil~ ___ :==Ff~
`transmission schemfamsung Ex. 100a
`
`
`
`PUCCH Transmission Scheme
`for LTE-Advanced UE (2)
`Sel11fJmber 29 - October 3. 2008 I NTT DOCOMO. INC.
`-
`- -
`PUCCH transmission scheme candidates in Approach 2
`• Option 1: Single-carrier (SC) transmission (with inter-subframe hopping)
`• Option 2: SC transmission with intra-subframe hopping using wider
`transmission bandwidth
`• Option 3: Multi-carrier (MC) transmission
`Option 1
`Option 2
`Commonality to High when current Medium + Unused
`Rel-8 LTE UE
`PUCCH format is
`PUCCH remains in
`applied
`the middle position
`Good
`Good
`Hopping
`Hopping (wider than
`Option 1)
`
`PAPR
`Frequency
`diversity gain
`
`- - -
`
`Option 3
`High when current
`PUCCH format is
`applied
`Poor
`MRC
`
`Option 2
`Intra-subframe hopping
`
`' J
`~
`(Inter-subframe
`hopping)
`
`____,_~ -~::::!I
`
`I
`
`-. TE-Advan~ed)
`
`I
`I
`
`I
`
`. t-TE-Adva~ed)
`
`I
`I
`
`lntra-s
`hoppi .,__._ _
`
`I
`I
`
`doco~o
`
`Option 3
`MC transmission
`
`--
`
`- --
`
`-
`
`8
`
`
`
`PUCCH Transmission Scheme
`for LTE-Advanced UE (3)
`September 29 - October 3, 2008 I NTT DOCOMO, INC.
`
`(cid:127) Another issue
`~ Joint or separate coding of control signaling bits for each DL
`component carrier
`(A) Joint coding: Increase in coding gain
`Control bits for DL
`component carrier #1
`
`Control bits for DL
`component carrier #2
`
`• • •
`
`Channel coding
`and modulation
`
`Multiplexing
`
`Control bits for DL
`component carrier #N 0
`(B) Separate coding: Prioritize backward compatibility
`
`Can be applied to both
`Approaches 1 and 2
`
`Control bits for DL
`component carrier #1
`
`Control bits for DL
`component carrier #2
`•
`•
`•
`Control bits for DL
`component carrier #N 0
`
`Channel coding
`and modulation
`
`Channel coding
`and modulation
`•
`•
`•
`Channel coding
`and modulation
`
`Multiplexing
`
`docomo
`
`No gain in Approach 2
`+ Considered for
`Approach 1 only
`
`Samsung Ex. 1008
`
`9
`
`
`
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
`
`Views on PUCCH Transmission Scheme
`for LTE-Advanced UE
`
`docomo
`
`10
`
`Samsung Ex. 1008
`
`
`
`Views on CQI Feedback for LTE-Advanced UE
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
` CQI feedback for LTE-Advanced UE with wider bandwidth
`• For CQI feedback, UE-specific dedicated radio resource is
`persistently allocated
`• Optimum PUCCH transmission scheme for wider bandwidth can
`easily be applied while taking advantage of same PUCCH structure
`as that for Rel-8 LTE
`
` Prefer Approach 2 with joint coding to provide optimum PUCCH
`transmission scheme for LTE-Advanced UE with wider bandwidth
` Detail format (Options 1 – 3 in page 8) is FFS
`
`docomo
`
`11
`
`Samsung Ex. 1008
`
`
`
`Views on ACK/NACK Feedback
`for LTE-Advanced UE (1)
`September 29 - October 3, 2008 I NTT DOCOMO, INC.
`ACK/NACK feedback for LTE-Advanced UE with wider bandwidth
`(cid:127) Approach 1 ~ Straightforward scheme
`(cid:141) Pros
`✓ Reuse linkage from CCE index in Rel-8 LTE. Note that UL ACK/NACK
`resources are Ii nked to CCE index in Rel-8 L TE
`✓ No additional increase in overhead
`(cid:141) Cons
`✓ When multiple transport blocks (code words) are applied to DL
`component carriers, multi-carrier (resource) transmission is required
`to send multiple ACK/NACK bits within the same TTI
`
`Component carrier
`
`DL
`
`TB1
`
`TB2
`
`TB3
`
`TB4
`
`D L/U L Ii n kage ·----_-_ ------ -----
`UL
`
`------- ----------- --------_-_ -------
`Multi-carrier transmission
`of ACK/NACK signal
`
`docomo
`
`Samsung Ex. 1008
`
`12
`
`
`
`Views on ACK/NACK Feedback
`for LTE-Advanced UE (2)
`Se tember 29 - October 3, 2008 I NTT DOCOMO, INC.
`ACK/NACK feedback for LTE-Advanced UE with wider bandwidth
`(cid:127) Approach 2 + Optimized scheme for wider bandwidth
`(cid:141) Pros
`✓ Retains single-carrier feature for transmitting multiple ACK/NACK
`signals for multiple code word transmission in DL + Achieves low
`PAPR
`✓ Joint coding of multiple ACK/NACK bits can be used
`(cid:141) Cons
`✓ Transmission scheme different from Rel-8 L TE is specified for LTE(cid:173)
`Advanced UE
`✓ Increase in overhead + Requires separate resources
`
`Component carrier
`
`DL
`
`TB1
`
`TB2
`
`I
`
`TB3
`
`TB4
`
`UL ~l :Jffil :J~
`
`\,....---="" ~
`Employing optimum transmission scheme using
`separate resources than those for Rel-8 LTE UE
`
`docomo
`
`Samsung Ex. 1008
`
`13
`
`
`
`Conclusion
`September 29 – October 3, 2008 / NTT DOCOMO, INC.
` Investigate PUCCH transmission scheme for LTE-Advanced UE with wider
`Tx/Rx bandwidth capability
`Note that we assume the same PUCCH structure as that of Rel-8 LTE
` Presented two major approaches
`• Approach 1: Reuse of PUCCH transmission scheme in Rel-8 LTE
`• Approach 2: Apply optimum transmission scheme for wider bandwidth
`(Options 1 – 3 in page 8)
`
` CQI feedback for wider bandwidth
`• Prefer Approach 2 with joint coding to provide optimum PUCCH
`transmission scheme for LTE-Advanced UE with wider bandwidth
` Detail format is FFS
`
` ACK/NACK feedback for wider bandwidth
`• Both Approach 1 and 2 have pros and cons
` Further investigation is necessary
`
`docomo
`
`14
`
`Samsung Ex. 1008
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
