throbber
Application No. 15/810,589
`Reply to Office Action Dated October 5, 2021
`
`REMARKS
`
`Applicant respectfully requests reconsideration of this application in view of the above
`
`amendments and the following remarks. Claims 1, 10, 12-13, and 16-25 will be pending upon
`
`entry of this amendment. Claims 1, 10, 12-13, and 19-20 have been amended. Claims 2-9, 11,
`
`and 14-15 were canceled by way of previous amendment. Claims 24 and 25 are new. Support for
`
`the amendments maybe found, for example, in §][0064]-[0066] and Figure 18 of the application
`
`as filed. No new matter has been addedto the application.
`
`This response is being submitted with an After Final Consideration Pilot Program
`
`request.
`
`Applicant thanks the Examinerfor the telephone conference conducted on November1,
`
`2021, with the undersigned counsel. No agreement was reached during the conference.
`
`In the Office Action, claims 1, 10, 12-13, and 16-20 were rejected under 35 U.S.C. §103
`
`as being unpatentable over 3GPP TSG RAN WGI #81 (RI-153567) in view of 3GPP TSG RAN
`
`WGI #81 (RI-152954), Kim et al. (U.S. 2015/0036609 A1), the Background section of Horiuchi
`
`et al. (U.S. 2018/0070339 A1), and Hong (U.S. 2014/0307692 A1). In response, Applicant has
`
`amended claims 1, 10, 12-13, and 19-20 to moreparticularly recite the subject matter that
`
`Applicant considers as their invention and to moreclearly distinguish the claims from RI-
`
`153567, RI-152954, Kim, the Backgroundsection of Horiuchi, and Hong.
`
`Amendedclaim 1 recites a base station comprising:
`
`control circuitry which, in operation, allocates a physical downlink shared channel
`
`(PDSCH)on a plurality of resource blocks (RBs); and
`a transmitter which, in operation, transmits control information including a
`resource indication value (RIV) which indicates the plurality of RBs,
`wherein a same value of the RIV indicates different frequency positions of RBs
`on an allocated narrowband based on a frequency position of the allocated narrowband
`within a system band and a frequency position of resource block groups (RBGs) of the
`system band,
`a frequency boundary of the frequency position of the allocated narrowbandis
`different from a frequency boundary of the frequency position of the RBGs,
`the frequency position of the allocated narrowbandis determined based on a size
`of each of the RBGs, the size of each of the RBGs being smaller than a size of the
`allocated narrowband, and
`
`

`

`Application No. 15/810,589
`Reply to Office Action Dated October 5, 2021
`
`the size of each of the RBGsis specified according to a number of RBs thatis
`included in the system band.
`
`RI-153567 fails to teach or suggest control information including a resource indication
`
`value (RIV) which indicates the plurality of RBs, wherein a same value of the RIV indicates
`
`different frequency positions of RBs on an allocated narrowband based on a frequency position
`
`of the allocated narrowband within a system band and a frequency position of resource block
`
`groups (RBGs)of the system band. RI-153567 describes that a narrowband for MTC UEsis
`
`defined as a set of contiguous PRBs. See page 2. For example, a narrowband may be 6 PRBs
`
`defined continuously starting from one edge of the system BW. See page 4. The portions of RI-
`
`153567 cited by the Examinerare silent to control information including a resource indication
`
`value (RIV) which indicates the plurality of RBs, wherein a same value of the RIV indicates
`
`different frequency positions of RBs on an allocated narrowband based on a frequency position
`
`of the allocated narrowband within a system band and a frequency position of resource block
`
`groups (RBGs) of the system band.
`
`RI-152954 fails to cure the deficiencies of RI-153567. RI-152954 describes DCIthat
`
`indicates a narrow-bandandresource allocation within narrow-band. See section 3.1. In a Type 1
`
`allocation type, a resource allocated to a UE 1s continuous. In a Type 2 allocation type, a
`
`resource allocated to a UE is continuousor discontinuous. The portions of RI-152954 cited by
`
`the Examinerare silent to control information including a resource indication value (RIV) which
`
`indicates the plurality of RBs, wherein a same value of the RIV indicates different frequency
`
`positions of RBs on an allocated narrowbandbased on a frequency position of the allocated
`
`narrowbandwithin a system band and a frequency position of resource block groups (RBGs) of
`
`the system band.
`
`Kim fails to cure the deficiencies of RI-153567 and RI-152954. Kim describes a RBG
`
`1300 including RB 1300-2 and RB 1300-1. See §[0167]. The user equipment specific reference
`
`signals (URS) transmitted through the RBs may have different URS patterns. The portions of
`
`Kim cited by the Examinerare silent to control information including a resource indication value
`
`(RIV) which indicates the plurality of RBs, wherein a same value of the RIV indicates different
`
`frequency positions of RBs on an allocated narrowband based on a frequency position ofthe
`
`

`

`Application No. 15/810,589
`Reply to Office Action Dated October 5, 2021
`
`allocated narrowband within a system band anda frequencyposition of resource block groups
`
`(RBGs)of the system band.
`
`The portions of the Background section of Horiuchi cited by the Examineralso fails to
`
`cure the deficiencies of RI-153567, RI-152954, and Kim.
`
`Hongfails to cure the deficiencies of RI-153567, RI-152954, Kim, and the Background
`
`section of Horiuchi. Hong describes that resource allocation information expressed based on the
`
`resource blocks or the resource block groups may be transmitted in a form of Resource
`
`Indication Value (RIV)in a resource allocation field included in a PDCCH.See §[0051].
`
`However, a same value of the RIV of Hong does notindicate different frequency positions of
`
`RBs on an allocated narrowband,let alone indicate the different frequency positions of RBs
`
`based on a frequency position of the allocated narrowband within a system band and a frequency
`
`position of resource block groups (RBGs) of the system band. Rather, the portions of Hong cited
`
`by the Examiner simply describes that resource allocation information expressed based on the
`
`resource blocks or the resource block groups may be transmitted in a form of RIV.
`
`Applicant submits claim 1 is allowable over RI-153567, RI-152954, Kim, the
`
`Background section of Horiuchi, and Hong. Dependentclaims 16-23 are allowable for the
`
`features recited therein as well as for the reasons discussed above with respect to claim 1.
`
`Although the language of claims 10 and 12-13 are not identical to the language of claim
`
`1, the allowability of claims 10 and 12-13 will become apparentin light of the discussion above
`
`with respect to claim 1. Applicant submits claims 10 and 12-13 are allowable over RI-153567,
`
`RI-152954, Kim, the Background section of Horiuchi, and Hong.
`
`Applicant has added new claims 24 and 25. Claims 24 and 25 depend from claim 1.
`
`Applicant submits claims 24 and 25 are allowable for the features recited therein as well as for
`
`the reasons discussed above with respect to claim 1.
`
`Closing
`
`All of the claims remaining in the application are now clearly allowable. Favorable
`
`consideration and a Notice of Allowanceare earnestly solicited.
`
`

`

`Application No. 15/810,589
`Reply to Office Action Dated October 5, 2021
`
`In the event the Examiner finds minor informalities that can be resolved by telephone
`
`conferenceor if the Examinerbelieves a telephone conference would facilitate prosecution of this
`
`application, the Examineris urged to contact Applicant’s undersigned representative by telephone
`
`at (206) 622-4900 in order to expeditiously resolve prosecution of this application.
`
`Respectfully submitted,
`
`Seed Intellectual Property Law Group Lip
`
`/Blake K. Kumabe/
`Blake K. Kumabe
`Registration No. 68,240
`
`701 Fifth Avenue, Suite 5400
`Seattle, Washington 98104
`Phone: (206) 622-4900 | Fax:
`
`(206) 682-6031
`
`BK1:dmk
`82364741
`
`10
`
`

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