`Exhibit 1005
`
`ZTE Corporation and ZTE (USA) Inc.
`ZTE Corporation and ZTE (USA) Inc.
`
`
`
`TSG-RAN Working Group 1 #22
`Torino, Italy, Aug. 27-31 2001
`
`R1-01-0810
`
`Source:
`
`Title:
`
`InterDigital Comm. Corp.
`
`Implicit UE Identification for HSDPA Downlink Signaling
`
`Document for:
`
`Discussion
`
`Introduction
`1.0
`Reference [2] proposed two encoding strategies for the HS-PDSCCH that eliminate the need
`for explicit UE ID when an HS-DSCH Indicator (HI) is present.
`These were:
`¯ A UE specific scrambling code
`¯ A UE-specific CRC
`
`In the second strategy, a UE-specific CRC may be constructed by requiring that the 16-bit
`MAC UE ID be concatenated with the control information and passed through the CRC
`generator polynomial. As a result, the CRC generated will be a function of the UE ID.
`However, the UE ID is never transmitted over the air.
`
`This document supports the use of the UE-specific CRC because it is simple and effective
`and applicable equally to FDD and TDD.
`
`In the discussion of reference [2] in Espoo, InterDigital Comm. Corp. supported the basic
`approach of UE-specific CRC, but suggested that there are other implementations that may
`provide the same fundamental benefit with somewhat simpler implementation.
`
`This contribution identifies two alternative implementations for the UE-specific CRC.
`
`2.0 Review of Concatenation Approach
`
`The UE-specific CRC method described in [2] is implemented by using the MAC UE ID
`concatenated with control information to generate CRC as depicted in the figure below:
`X
`M
`N
`
`HS-DSCCH
`
`CRC
`Generator
`
`The common control channel HS-DSCCH carries UE specific control information as shown
`below:
`
`X
`
`N
`
`HS-DSCCH
`
`NK8681TC015906751
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005-00001
`
`
`
`3.0 Alternative Implementations
`
`This section defines two alternative implementations, which provide benefits of the UE-
`specific CRC.
`
`Alternative 1 - First generate the N bit CRC, independent of UE ID. Then, modulo 2 add the
`N-bit CRC with the M-bit MAC UE ID. If M<N, the UE ID is zero padded with M-N leading O’s
`or trailing O’s. Here, the CRC is used to provide higher protection for the UE-specific control
`information carried on HS-DPSCCH. If M >N, the M-N least significant bits of the UE ID are
`truncated prior to the module 2 addition with the CRC field
`M
`
`X
`
`HS-DSCCH
`
`CRC
`Generator
`
`The code multiplexed HS-DSCCH carrying UE specific control information contains
`embedded UE ID as shown:
`X
`N
`Mask
`HS-DSCCH CRC
`
`Alternative 2 - In step 2, initialize the CRC generator (i.e., the shift-register) by UE ID value
`prior to CRC generation for the HS-PDSCCH as shown:
`
`X
`
`HS-DSCCH
`
`N
`
`CRC
`Generator
`
`The code multiplexed HS-DSCCH carrying UE specific control information in alternatives 2
`contains embedded UE ID as shown:
`X
`N
`
`HS-DSCCH
`
`All three UE-specific CRC approaches have the same error protection capability; proportional
`to 2-a, where N is the length of the CRC. However, considering the complexity, we propose
`use of implicit UE identification described as alternative 2, due to the fact that this method
`does not require assembly and disassembly of UE ID with the HS-DSCCH, at transmitting or
`receiving end, as required by UE-specific CRC method described in [2].
`
`4.0 Performance
`
`NK8681TC015906752
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005-00002
`
`
`
`For all the candidates discussed, the error detection protection is on the order of 2-N, where N
`is the size of the CRC.
`
`5.0 Conclusion
`
`Implicit UE ID encoding via a UE-specific CRC is recommended. It is simple, effective, and
`equally applicable to FDD and TDD.
`
`Three alternative implementations have been discussed, one from reference [2] and two
`additional alternatives in this contribution.
`
`All will provide the same level of protection, and the least complex version should be
`selected.
`
`InterDigital’s complexity analysis has judged that the simplest, and therefore preferred
`approach is to initialize the N-stage CRC shift register with N bits from the UE ID.
`
`[1] TSGR1#21(01) 0745, "Reliability Issues for Downlink Signaling in High Speed Downlink
`Packet Access (HSDPA)", Motorola
`[2] TSGR1#21(01) 0758, "Comments on the Requirement for UE ID when HI bit is present",
`Motorola
`
`NK8681TC015906753
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005-00003
`
`
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
