throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`UNITED STATES DEPARTMENT OF COMMERCE
`United States Patent and Trademark Office
`Address: COMMISSIONER FOR PATENTS
`PO. Box 1450
`Alexandria, Virginia 2231371450
`www.uspto.gov
`
`15/746,742
`
`01/22/2018
`
`TETSUYA YAMAMOTO
`
`731456.460USPC
`
`5655
`
`Seed IP Law Group LLP/Panason1e (PIPCA)
`701 5th Avenue, Suite 5400
`Seattle, WA 98104
`
`LEE” JAE YOUNG
`
`PAPER NUMBER
`
`ART UNIT
`
`2466
`
`NOTIFICATION DATE
`
`DELIVERY MODE
`
`07/25/2019
`
`ELECTRONIC
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any, is set in the attached communication.
`
`Notice of the Office communication was sent electronically on above—indicated "Notification Date" to the
`
`following e—mail address(es):
`US PTOeACtion @ SeedIP .Com
`
`pairlinkdktg @ seedip .eom
`
`PTOL-90A (Rev. 04/07)
`
`

`

`0/7709 A0170” Summary
`
`Application No.
`15/746,742
`Examiner
`JAE Y LEE
`
`Applicant(s)
`YAMAMOTO et al.
`Art Unit
`AIA (FITF) Status
`2466
`Yes
`
`- The MAILING DA TE of this communication appears on the cover sheet wit/7 the correspondence address -
`Period for Reply
`
`A SHORTENED STATUTORY PERIOD FOR REPLY IS SET TO EXPIRE g MONTHS FROM THE MAILING
`DATE OF THIS COMMUNICATION.
`Extensions of time may be available under the provisions of 37 CFR 1.136(a). In no event, however, may a reply be timely filed after SIX (6) MONTHS from the mailing
`date of this communication.
`|f NO period for reply is specified above, the maximum statutory period will apply and will expire SIX (6) MONTHS from the mailing date of this communication.
`-
`- Failure to reply within the set or extended period for reply will, by statute, cause the application to become ABANDONED (35 U.S.C. § 133).
`Any reply received by the Office later than three months after the mailing date of this communication, even if timely filed, may reduce any earned patent term
`adjustment. See 37 CFR 1.704(b).
`
`Status
`
`1). Responsive to communication(s) filed on 21 May 2019.
`[:1 A declaration(s)/affidavit(s) under 37 CFR 1.130(b) was/were filed on
`
`2a). This action is FINAL.
`
`2b) C] This action is non-final.
`
`3)[:] An election was made by the applicant in response to a restriction requirement set forth during the interview on
`; the restriction requirement and election have been incorporated into this action.
`
`4)[:] Since this application is in condition for allowance except for formal matters, prosecution as to the merits is
`closed in accordance with the practice under Expat/7e Quay/e, 1935 CD. 11, 453 O.G. 213.
`
`Disposition of Claims*
`
`5)
`
`Claim(s) fl is/are pending in the application.
`
`5a) Of the above claim(s)
`
`is/are withdrawn from consideration.
`
`E] Claim(s)
`
`is/are allowed.
`
`Claim(s) fl is/are rejected.
`
`[:1 Claim(s) _ is/are objected to.
`
`) ) ) )
`
`6 7
`
`8
`
`
`
`are subject to restriction and/or election requirement
`[j Claim(s)
`9
`* If any claims have been determined aflowabie. you may be eligible to benefit from the Patent Prosecution Highway program at a
`
`participating intellectual property office for the corresponding application. For more information, please see
`
`http://www.uspto.gov/patents/init events/pph/index.jsp or send an inquiry to PPeredback@uspto.gov.
`
`Application Papers
`10)[:] The specification is objected to by the Examiner.
`
`11)[:] The drawing(s) filed on
`
`is/are: a)D accepted or b)l:] objected to by the Examiner.
`
`Applicant may not request that any objection to the drawing(s) be held in abeyance. See 37 CFR 1.85(a).
`Replacement drawing sheet(s) including the correction is required if the drawing(s) is objected to. See 37 CFR 1.121 (d).
`
`Priority under 35 U.S.C. § 119
`12):] Acknowledgment is made of a claim for foreign priority under 35 U.S.C. § 119(a)-(d) or (f).
`Certified copies:
`
`a)D All
`
`b)I:l Some**
`
`c)C] None of the:
`
`1.[:] Certified copies of the priority documents have been received.
`
`2.[:] Certified copies of the priority documents have been received in Application No.
`
`3.[:] Copies of the certified copies of the priority documents have been received in this National Stage
`application from the International Bureau (PCT Rule 17.2(a)).
`
`** See the attached detailed Office action for a list of the certified copies not received.
`
`Attachment(s)
`
`1)
`
`Notice of References Cited (PTO-892)
`
`2) D Information Disclosure Statement(s) (PTO/SB/08a and/or PTO/SB/08b)
`Paper No(s)/Mail Date_
`U.S. Patent and Trademark Office
`
`3) C] Interview Summary (PTO-413)
`Paper No(s)/Mail Date
`4) CI Other-
`
`PTOL-326 (Rev. 11-13)
`
`Office Action Summary
`
`Part of Paper No./Mai| Date 20190706
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 2
`
`Notice of Pre-AIA or AIA Status
`
`1.
`
`The present application, filed on or after March 16, 2013, is being examined under the first
`
`inventor to file provisions of the AIA.
`
`2.
`
`Applicant's arguments filed on 5/21/2019 have been fully considered but they are not
`
`Response to Arguments
`
`persuasive.
`
`3.
`
`On page 8 of applicant’s argument, the applicant argues that ”Takeda fails to teach any details
`
`of the PUCCH resources’ ”association with the PDSCH’s PRB index”. Not every association between
`
`PUCCH resources and a PDSCH’s PRB index results in a one-to-one correspondence between the PUCCH
`
`resources and the PDSCH’s PRB index”.
`
`4.
`
`Examiner respectfully disagrees with the applicant’s argument. Claim 1 discloses ”the uplink
`
`resource being associated in one-to-one correspondence with a number of a downlink resource to
`
`which the downlink data is allocated in the last subframe” without further limitation i.e., how the uplink
`
`is resource is associated with one-to-one correspondence, what the one-to-one correspondence, etc.
`
`Instead, the uplink resource is merely associated in one-to-one relationship with a number of a downlink
`
`resource.
`
`Takeda discloses ”the relationship between the downlink narrow band in which a PDSCH is
`
`received and the uplink narrow band in which a PUCCH is transmitted in response to the PDSCH are
`
`determined in advance” (par. 40), ”the PUCCH resources for transmitting an ACK/NACK in response to
`
`the PDSCH can be specified in association with the PDSCH's PRB index” (par. 45) and ”a predetermined
`
`period of time (for example, 4 subframes) after the last subframe in which the PDSCH was received, UE
`
`#1 and UE #2 each transmit an ACK/NACK in response to this PDSCH, by using predetermined PUCCH
`
`resources” (par. 58). In other words, PUCCH resource (i.e., uplink subframe) is associated in a
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 3
`
`predetermined period of time (for example, 4 subframes) after the last subframe in which the PDSCH
`
`being specified in association with the PDSCH’s PRB index was received (i.e., one-to-one correspondence
`
`with a number of downlink resource to which the downlink data is allocated in the last subframe) for
`
`transmitting ACK/NACK in response to the PDSCH by using the predetermined PUCCH resource.
`
`For at least the foregoing reasons, Takeda teaches the every feature of independent claim land
`
`thus can anticipate this claim.
`
`Claim Rejections - 35 USC § 102
`
`5.
`
`In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102
`
`and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory
`
`basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and
`
`the rationale supporting the rejection, would be the same under either status.
`
`6.
`
`The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis
`
`for the rejections under this section made in this Office action:
`
`A person shall be entitled to a patent unless —
`
`(a)(2) the claimed invention was described in a patent issued under section 151, or in an application
`for patent published or deemed published under section 122(b), in which the patent or application, as
`the case may be, names another inventor and was effectively filed before the effective filing date of
`the claimed invention.
`
`7.
`
`Claims 1-7 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Takeda et al. (US
`
`2017/0353272).
`
`Regarding claim 1, Takeda discloses
`
`o
`
`a terminal comprising: a receiver (Fig. 14) which, in operation, that receives the same
`
`downlink data over one or more subframes (par. 58: UE #1 and UE #2 each receive the PDSCH
`
`in a plurality of subframes, in repetitions, by using resources that are specified by the EPDCCH
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 4
`
`for the subject terminal) through a downlink resource within a machine-type communication
`
`(MTC) narrow band (par. 44: The information to represent the locations of PDSCH resources
`
`may be, for example, a PRB index (for example, one of 0 to 5) within a predetermined narrow
`
`band (for example, 6 RES), or may be a relative frequency offset to the locations of EPDCCH
`
`resources);
`
`0
`
`circuitry (Fig. 14) which, in operation, generates a response signal as a response to the
`
`downlink data (par. 35: The user terminal receives the PDSCH in the allocated resources
`
`specified by the EPDCCH, and transmits an HARQ-ACK in response to this PDSCH by using a
`
`PUCCH (Physical Uplink Control Channel); and
`
`o
`
`a transmitter (Fig. 14) which, in operation, transmits the response signal through an uplink
`
`resource a predetermined number of subframes after a last subframe of the one or more
`
`subframes, the uplink resource being associated in one-to-one correspondence with a number
`
`of a downlink resource to which the downlink data is allocated in the last subframe (par. 40:
`
`the relationship between the downlink narrow band in which a PDSCH is received and the uplink
`
`narrow band in which a PUCCH is transmitted in response to the PDSCH are determined in
`
`advance; par. 45: the PUCCH resources for transmitting an ACK/NACK in response to the PDSCH
`
`can be specified in association with the PDSCH's PRB index; par. 58: UE #1 and UE #2 each
`
`receive the PDSCH in a plurality of subframes, in repetitions, by using resources that are
`
`specified by the EPDCCH for the subject terminal. Also, a predetermined period of time (for
`
`example, 4 subframes) after the last subframe in which the PDSCH was received, UE #1 and UE
`
`#2 each transmit an ACK/NACK in response to this PDSCH, by using predetermined PUCCH
`
`resources).
`
`Regarding claim 2, Takeda discloses
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 5
`
`0 wherein the number of the downlink resource is the number of a physical resource block
`
`(PRB) that constitutes the narrow band (par. 45: An MTC terminal specifies the PRB of a PDSCH
`
`received in a predetermined narrow band (PDSCH set). To specify the PRB, for example, the PRB
`
`index can be used. Furthermore, the PUCCH resources for transmitting an ACK/NACK in
`
`response to the PDSCH can be specified in association with the PDSCH's PRB index).
`
`Regarding claim 3, Takeda discloses
`
`0 wherein the number of the downlink resource is a number of that identifies the narrow band
`
`(par. 40: the relationship between the downlink narrow band in which a PDSCH is received and
`
`the uplink narrow band in which a PUCCH is transmitted in response to the PDSCH are
`
`determined in advance; par. 45: the PUCCH resources for transmitting an ACK/NACK in response
`
`to the PDSCH can be specified in association with the PDSCH's PRB index).
`
`Regarding claim 4, Takeda discloses
`
`0 wherein the uplink resource through which the response signal is transmitted includes
`
`different regions that are used by a first MTC terminal for which less than a predetermined
`
`number of subframes are used to transmit the downlink data and a second MTC terminal for
`
`which the predetermined number of subframes or more is used to transmit the downlink data
`
`(par. 57: the number of times to repeat the PDSCH for UE #1 is 4, and the number of times to
`
`repeat the PDSCH for UE #2 is 2; par. 58: Also, a predetermined period of time (for example, 4
`
`subframes) after the last subframe in which the PDSCH was received, UE #1 and UE #2 each
`
`transmit an ACK/NACK in response to this PDSCH, by using predetermined PUCCH resources).
`
`Regarding claim 5, Takeda discloses
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 6
`
`0 wherein the number of the downlink resource associated in one-to-one correspondence with
`
`the uplink resource in the region of the uplink resource used by the first MTC terminal is the
`
`number of a physical resource block (PRB) that constitutes the narrow band (par. 40: the
`
`relationship between the downlink narrow band in which a PDSCH is received and the uplink
`
`narrow band in which a PUCCH is transmitted in response to the PDSCH are determined in
`
`advance; par. 45: the PUCCH resources for transmitting an ACK/NACK in response to the PDSCH
`
`can be specified in association with the PDSCH's PRB index), and
`
`o
`
`the number of the downlink resource associated in one-to-one correspondence with the
`
`uplink resource in the region of the uplink resource used by the second MTC terminal is the
`
`number of the narrow band (par. 57: the number of times to repeat the PDSCH for UE #1 is 4,
`
`and the number of times to repeat the PDSCH for UE #2 is 2; par. 58: Also, a predetermined
`
`period of time (for example, 4 subframes) after the last subframe in which the PDSCH was
`
`received, UE #1 and UE #2 each transmit an ACK/NACK in response to this PDSCH, by using
`
`predetermined PUCCH resources).
`
`Regarding claim 6, Takeda discloses
`
`o
`
`a base station comprising: a transmitter (Fig. 12) which, in operation, transmits the same
`
`downlink data over one or more subframe (par. 58: UE #1 and UE #2 each receive the PDSCH in
`
`a plurality of subframes, in repetitions, by using resources that are specified by the EPDCCH for
`
`the subject terminal) through a downlink resource within a machine-type communication
`
`(MTC) narrow band (par. 44: The information to represent the locations of PDSCH resources
`
`may be, for example, a PRB index (for example, one of 0 to 5) within a predetermined narrow
`
`band (for example, 6 RES), or may be a relative frequency offset to the locations of EPDCCH
`
`resources); and
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 7
`
`o
`
`a receiver (Fig. 12) which, in operation, receives a response signal as a response to the
`
`downlink data through an uplink resource a predetermined number of subframes after a last
`
`subframe of the one or more subframes, the uplink resource being associated in one-to-one
`
`correspondence with a number of a downlink resource to which the downlink data is allocated
`
`in the last subframe (par. 40: the relationship between the downlink narrow band in which a
`
`PDSCH is received and the uplink narrow band in which a PUCCH is transmitted in response to
`
`the PDSCH are determined in advance; par. 45: the PUCCH resources for transmitting an
`
`ACK/NACK in response to the PDSCH can be specified in association with the PDSCH's PRB index;
`
`par. 58: UE #1 and UE #2 each receive the PDSCH in a plurality of subframes, in repetitions, by
`
`using resources that are specified by the EPDCCH for the subject terminal. Also, a
`
`predetermined period of time (for example, 4 subframes) after the last subframe in which the
`
`PDSCH was received, UE #1 and UE #2 each transmit an ACK/NACK in response to this PDSCH, by
`
`using predetermined PUCCH resources).
`
`Regarding claim 7, Takeda discloses
`
`o
`
`a transmission method comprising: receiving the same downlink data over one or more
`
`subframes (par. 58: UE #1 and UE #2 each receive the PDSCH in a plurality of subframes, in
`
`repetitions, by using resources that are specified by the EPDCCH for the subject terminal)
`
`through a downlink resource within a machine-type communication (MTC) narrow band (par.
`
`44: The information to represent the locations of PDSCH resources may be, for example, a PRB
`
`index (for example, one of 0 to 5) within a predetermined narrow band (for example, 6 RES), or
`
`may be a relative frequency offset to the locations of EPDCCH resources);
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 8
`
`o
`
`generating a response signal as a response to the downlink data (par. 35: The user terminal
`
`receives the PDSCH in the allocated resources specified by the EPDCCH, and transmits an HARQ-
`
`ACK in response to this PDSCH by using a PUCCH (Physical Uplink Control Channel); and
`
`o
`
`transmitting the response signal through an uplink resource a predetermined number of
`
`subframes after a last subframe of the one or more subframes, the uplink resource being
`
`associated in one-to-one correspondence with a number of a downlink resource to which the
`
`downlink data is allocated in the last subframe (par. 40: the relationship between the downlink
`
`narrow band in which a PDSCH is received and the uplink narrow band in which a PUCCH is
`
`transmitted in response to the PDSCH are determined in advance; par. 45: the PUCCH resources
`
`for transmitting an ACK/NACK in response to the PDSCH can be specified in association with the
`
`PDSCH's PRB index; par. 58: UE #1 and UE #2 each receive the PDSCH in a plurality of subframes,
`
`in repetitions, by using resources that are specified by the EPDCCH for the subject terminal.
`
`Also, a predetermined period of time (for example, 4 subframes) after the last subframe in
`
`which the PDSCH was received, UE #1 and UE #2 each transmit an ACK/NACK in response to this
`
`PDSCH, by using predetermined PUCCH resources).
`
`Conclusion
`
`8.
`
`Applicant's amendment necessitated the new ground(s) of rejection presented in this Office
`
`action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the
`
`extension of time policy as set forth in 37 CFR 1.136(a).
`
`A shortened statutory period for reply to this final action is set to expire THREE MONTHS from
`
`the mailing date of this action.
`
`In the event a first reply is filed within TWO MONTHS of the mailing date
`
`of this final action and the advisory action is not mailed until after the end of the THREE-MONTH
`
`shortened statutory period, then the shortened statutory period will expire on the date the advisory
`
`

`

`Application/Control Number: 15/746,742
`Art Unit: 2466
`
`Page 9
`
`action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing
`
`date of the advisory action.
`
`In no event, however, will the statutory period for reply expire later than
`
`SIX MONTHS from the date of this final action.
`
`9.
`
`Any inquiry concerning this communication or earlier communications from the examiner
`
`should be directed to Jae Y. Lee whose telephone number is (571) 270-3936. The examiner can normally
`
`be reached on Monday through Friday from 7:30 AM to 5:00 PM EST.
`
`If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor,
`
`Faruk Hamza can be reached on (571) 272-7969. The fax phone number for the organization where this
`
`application or proceeding is assigned is 571-273-8300. Information regarding the status of an
`
`application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status
`
`information for published applications may be obtained from either Private PAIR or Public PAIR. Status
`
`information for unpublished applications is available through Private PAIR only. For more information
`
`about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the
`
`Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you
`
`would like assistance from a USPTO Customer Service Representative or access to the automated
`
`information
`
`system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
`
`/JAE Y LEE/
`
`Primary Examiner, Art Unit 2466
`
`

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