`
`3GPP TSG-RAN WG2 #58bis
`25th – 29th June 2007
`Orlando, USA
`
`Agenda item:
`Source:
`Title:
`Document for:
`
`5.3.1
`LG Electronics Inc.
`Discussion on BCCH Update
` Discussion, Decision
`
`Introduction
`1.
`A mechanism for efficient reading of BCCH is beneficial in UE’s battery performance point of view. In WCDMA, a
`value tag is used to indicate whether there is any change in SIBs. Because this will impact UE battery performance
`anyway, reception of even value tags should be further reduced.
`
`Discussion
`2.
`P-BCH and DL-SCH can be used to deliver BCCH. On DL-SCH, SU-1 indicates the scheduling information for other
`SUs.
`
`Upper layer data or signalling is transferred over U/D-SCH and the resource for U/D-SCH transmission is indicated
`over L1/L2 control channel. This will be also the case for the reading of SU-1. In other words, the information on the
`radio resources used for SU-1 also will be indicated by L1/L2 control channel. Then, using the L1/L2 control can be
`one solution for notification. With this, the UE does not need to decode DL-SCH when there is no need. We foresee two
`possible approaches.
`
`First approach is to allocate several identifiers for BCCH. For example, let’s assume that two SU-1-RNTIs are allocated
`for the transmission of SU-1. Then, by alternating the used SU-1-RNTI, eNB can indicate to the UE that information
`over SU-1 has changed or not. At UE side, just simple comparison of current RNTI with previous RNTI, the UE knows
`whether there is a change in BCCH or there is a need to read BCCH.
`
`Following figure 1 shows an example of first approach.
`
` 1
`
`ERICSSON EXHIBIT 2005
`Apple, Inc. v. Telefonaktiebolaget LM Ericsson
`IPR2022-00338, Page 1
`
`
`
` 2
`
`
`
` 3
`
`
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
