throbber
Tdoc "R2-084455
`
`Commented [H1]: Document numbers are allocated by the
`Working Group Secretary.
`
`3GPP TSG-RAN2#63 meeting
`Jeju, South Korea, 18th– 22nd August 2008
`
`Agenda Item: 6.1.1.3
`
`Souce:
`
`Title:
`
`
`
`
`
`
`
`
`
`
`
` Samsung
`
` SPS resource release
`
`Document for: Discussion and decision
`
`1 Introduction
`
`This paper discusses how to release the SPS resource. One can consider the robustness to the false release as the most important
`thing to be ensured in the release mechanism. We think the false release could be detected by ENB from the fact that UE does not
`use the SPS resource anymore after flase release command occurs. Hence a simple release mechanism is enough.
`
`We propose here a mechanism using a code point of RB assignment field in DCI.
`
`2 Discussion
`
`As shown in table 1 only part of code points are used in RB assignment field of all system bandwidth if the frequency hopping is
`disabled. Since we are talking about resource release, there is no reason to enable the frequency hopping.
`
`Table 1. Number of unused code points in RB assignment field.
`
`System BW
`
`#of RBs
`
`# of required code point
`
`# of code points
`
`Unused code points
`
`1.4
`
`5
`
`10
`
`20
`
`6
`
`25
`
`50
`
`100
`
`21
`
`325
`
`1275
`
`5050
`
`32
`
`512
`
`2048
`
`8192
`
`11
`
`187
`
`773
`
`3142
`
`Any of the unused code point could indicate the SPS resource release. To make the relevant text simple, all 1s could be a good
`candidate. It is proposed to agree on the followings and send LS to RAN1 to inform RAN2 decision.
`
`Proposal: all 1s in RB assignment field in SPS resource allocation DCI releases the SPS resource currently configured.
`
`3 Conclusion & recommendation
`
`This paper proposes to use all 1s in RB assignment field in SPS resource allocation DCI to release the SPS resource. Since the
`basic text for SPS resource handling is missing in the current MAC spec, it is proposed to agree on the principle now and to
`capture the relevant text in the future.
`
`Note that the proposal is valid for DCI format 0/1A. Even though DCI format 1 is allowed for DL SPS resource signaling, we
`don’t see any reason to use DCI format 1 in releasing the resource. Hence we believe the proposal works both for the uplink and
`for the downlink.
`
`Page 1
`
`Ex. 1005 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 1 of 1
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

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.

throbber

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.

Become a Member

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

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket