`
`c) Print
`
`Dear all,
`
`LISTSERV 16.5 - 3GPP_TSG_IRAN_WG1 Archives
`
`In our understanding, exact rule of multiplexing ACK/NACK and CQI on PUSCH should be define in order to
`complete the part of the uplink control discussion. If we consider CQI alone, current description of
`multiplexing CQI on PUSCH follows the working assumption 'Control signalling mapped to SC-FDMA
`symbols next to RS:es.' agreed in RAN1#50. However, the 'near-RS mapping rule' should take care of
`both CQI and ACK/NACK. Especially, we think ACK/NACK protection is more important than CQI protection
`in high speed cases. Currently, we are considering 4 alternatives.
`
`Alternative 1: CQI mapping consecutive to RS + ACK/NACK mapping consecutive to RS by puncturing CQI
`symbols
`
`Alternative 2: CQI mapping consecutive to RS + ACK/NACK mapping next to CQI by puncturing Data
`symbols (farther from RS)
`
`Alternative 3: ACK/NACK mapping consecutive to RS + CQI time-first mapping (near-RS mapping is not
`considered)
`
`Among those 3 alternatives, we currently think the alternative 3 is preferable way considering ACK/NACK
`protection and simplicity in specifications (R1-080267 has detailed description). Alternative 1B and 2 are
`also described in detail in R1-080483.
`It would be nice if we can start some discussion on control signal multiplexing on PUSCH to get a
`conclusion during Sorrento meeting.
`
`Best Regards,
`Daewon
`
`Daewon Lee
`Research Engineer, 3G Standardization Group
`Mobile Communication Technology Research Lab
`LG Electronics, Inc., S.Korea
`E-mail : [log in to unmask]
`
`https://list.etsi.org/scripts/wa.exe?A3=ind0801D&L=3GPP_TSG_RAN_WG1&E=guoted-printable&P=14319150&B-
`
`%3D_NextPart_000_000F_01... 1/1
`
`APL-UPPO 002584815
`
`Optis Cellular Ex 2016-p. 1
`Apple v Optis Cellular
`IPR2020-00465
`
`
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
