Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 12-3-25 has been entered.
Priority
Applicant' s claim for the benefit of a prior-filed application PCT/JP2020/013153 filed 3-24-20 under 35 U.S.C. 119(e) or under 35 U.S.C. 120, 121, 365(c), or 386(c) is acknowledged.
Information Disclosure Statement
The information disclosure statements (IDSs) submitted on 9-23-22, 6-5-24 & 10-25-24. The submissions are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statements are being considered by the examiner.
Specification
The lengthy specification has not been checked to the extent necessary to determine the presence of all possible minor errors. Applicant’s cooperation is requested in correcting any errors of which applicant may become aware in the specification.
Claim Rejections - 35 USC § 102
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 (i.e., changing from AIA to pre-AIA ) 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.
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
(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.
Claim(s) 1-4, 6-7 & 9 is/are rejected under 35 U.S.C. 102(a)(1-2) as being anticipated by Khoshnevisan (US 2021/0266943 A1).
Regarding Claim 1. (Currently Amended)
A terminal {Khoshnevisan (US 2021/0266943 A1): UE 115-Figs.1-2 & 12} comprising:
a transceiver {Khoshnevisan: transceiver 1220-Fig.12} that transmits, to a network {Khoshnevisan: base station 105-Figs.1-2 & 16}, an information element {Khoshnevisan: HARQ ACK/NACK, ¶0124 wherein “when the UE 115 is configured to provide HARQ feedback (e.g., a HARQ ACK, a HARQ NACK) for multiple physical channels (e.g., multiple PDSCH) scheduled via cross component carrier”} indicating whether or not the terminal has a capability {Khoshnevisan: ¶0126-¶0127 wherein “the UE 115 may determine a resource (e.g., a PDSCH resource) associated with the PUCCH 720 based in part on a PRI associated with one or more of the DCI messages 710. For example, the UE 115 may determine resources of the PUCCH 720 for providing HARQ feedback for the multiple scheduled PDSCH 715 based on a PRI in a last received DCI message (e.g., the DCI message 710-d)”; In other words, by providing a feedback for a determined resource (the PDSCH resource 715) on PUCCH 720 as scheduled in DCI 710d, the UE inherently indicated that it is capable of executed the scheduled DCI 710d, emphasis added} of executing a predetermined communication {Khoshnevisan: DCI message 710d-Fig.7 for PUCCH 720-Fig.7}; and
a processor {Khoshnevisan: processor 1240-Fig.12} that executes, as the predetermined communication {Khoshnevisan: DCI message 710d-Fig.7 scheduled PUCCH 720-Fig.7 for UE to transmit HARQ/feedback from UE, emphasis added}, a reception of a transport block across a plurality of component carriers {Khoshnevisan: Fig.7 wherein the UE receives DCI 710d scheduling for PDSCH 715 and PUCCH 720d on component carriers 705a & 705c, ¶0126}.
Regarding Claim 3. (Currently Amended) The terminal according to claim 1, wherein the processor determines whether to apply the predetermined communication {Khoshnevisan: DCI message 710d-Fig.7 scheduled PUCCH 720-Fig.7 for UE to transmit HARQ/feedback from UE, emphasis added} based on an information element included in an RRC message received from the network (the base station 105-Figs.1-2) {Khoshnevisan: ¶0098 wherein “the base station 105-a may provide the HARQ feedback timing semi-statically (e.g., via an RRC message or a MAC-CE)” & ¶0099 wherein “the DCI message 210 may include a composite value that conveys information for providing HARQ feedback for the multiple scheduled PDSCH (e.g., a pattern or bitmap, a value that maps to an RRC configuration for providing HARQ feedback for the multiple scheduled PDSCH, etc.).” Also ¶0111 wherein “the base station 105-a may configure the UE 115-a, via an RRC configuration (e.g., pdsch-HARQ-ACK-Codebook=semi-static), to support a Type-1 codebook.”}.
Regarding Claim 4. (Currently Amended) The terminal according to claim 1, wherein the processor determines whether to apply the predetermined communication {Khoshnevisan: DCI message 710d-Fig.7 scheduled PUCCH 720-Fig.7 for UE to transmit HARQ/feedback from UE, emphasis added} based on an information element {Khoshnevisan: PDSCH 715 & PUCCH 720} included in downlink control information {Khoshnevisan: DCI 710d} received from the network (the base station 105-Figs.1-2) {Khoshnevisan: ¶0126-¶0127 wherein “the UE 115 may determine a resource (e.g., a PDSCH resource) associated with the PUCCH 720 based in part on a PRI associated with one or more of the DCI messages 710. For example, the UE 115 may determine resources of the PUCCH 720 for providing HARQ feedback for the multiple scheduled PDSCH 715 based on a PRI in a last received DCI message (e.g., the DCI message 710-d)”; In other words, by providing a feedback for a determined resource (the PDSCH resource 715) on the PUCCH 720 as scheduled in DCI 710d, the UE inherently indicated that it is applied the scheduled DCI 710d of PDSCH 715d and PUCCH 720 from the base station (the claimed network), emphasis added}.
Regarding Claims 5 & 8. (Canceled)
Regarding Claim 9. (Previously Presented) With the same reasons as set forth in the terminal according to claim 1, wherein the transport block (the PDSCH resource 715) is mapped on a guard subcarrier between the plurality of component carriers (component carriers 705a-705c) {Khoshnevisan: ¶0069 wherein “UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.”}
Regarding Claim 2. (Currently Amended) The terminal according to claim 1, wherein the processor determines to apply the predetermined communication {Khoshnevisan: DCI message 710d-Fig.7 scheduled PUCCH 720-Fig.7 for UE to transmit HARQ/feedback from UE, emphasis added}, when downlink control information (the DCI 710d) is received via a predetermined component carrier (component carrier 705c) {Khoshnevisan: ¶0126-¶0127 wherein “the UE 115 may determine a resource (e.g., a PUCCH resource) associated with the PUCCH 720 based in part on a PRI associated with one or more of the DCI messages 710. For example, the UE 115 may determine resources of the PUCCH 720 for providing HARQ feedback for the multiple scheduled PDSCH 715 based on a PRI in a last received DCI message (e.g., the DCI message 710-d)” and ¶0099 wherein “the DCI message 210 may include a composite value that conveys information for providing HARQ feedback for the multiple scheduled PDSCH (e.g., a pattern or bitmap, a value that maps to an RRC configuration for providing HARQ feedback for the multiple scheduled PDSCH, etc.)”; In other words, by providing a feedback for a determined resource (the PDSCH resource) associated with PUCCH 720 as scheduled in DCI 710d (as the claimed RRC message, ¶0098 wherein “the base station 105-a may provide the HARQ feedback timing semi-statically (e.g., via an RRC message or a MAC-CE)”), the UE inherently indicated that it is applied the scheduled DCI 710d of PDSCH 715d and PUCCH 720 received on Component Carrier 705-a from the base station (the claimed network), emphasis added}.
Regarding Claim 6. (Currently Amended) The terminal according to claim 2, wherein the processor determines whether to apply the predetermined communication {Khoshnevisan: DCI message 710d-Fig.7 scheduled PUCCH 720-Fig.7 for UE to transmit HARQ/feedback from UE, emphasis added} based on an information element {Khoshnevisan: PDSCH 715 & PUCCH 720} included in an RRC message received from the network {Khoshnevisan: ¶0126-¶0127 wherein “the UE 115 may determine a resource (e.g., a PDSCH resource) associated with the PUCCH 720 based in part on a PRI associated with one or more of the DCI messages 710. For example, the UE 115 may determine resources of the PUCCH 720 for providing HARQ feedback for the multiple scheduled PDSCH 715 based on a PRI in a last received DCI message (e.g., the DCI message 710-d)”, ¶0098 wherein “the base station 105-a may provide the HARQ feedback timing semi-statically (e.g., via an RRC message or a MAC-CE)” and ¶0099 wherein “the DCI message 210 may include a composite value that conveys information for providing HARQ feedback for the multiple scheduled PDSCH (e.g., a pattern or bitmap, a value that maps to an RRC configuration for providing HARQ feedback for the multiple scheduled PDSCH, etc.)”; In other words, by providing a feedback for a determined resource on the PUCCH 720 as scheduled in DCI 710d, the UE inherently indicated that it is applied the scheduled DCI 710d (the claimed RRC message) of PDSCH 715d and PUCCH 720 (the claimed information element) from the base station (the claimed network), emphasis added}.
Regarding Claim 7. (Currently Amended) The terminal according to claim 2, wherein the processor determines whether to apply the predetermined communication based on an information element included in downlink control information received from the network.
-Claim 7 is rejected with the same reasons as set forth in claim 4.
Response to Arguments
Applicant’s arguments with respect to claim(s) 14, 6-7 & 9 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Muruganathan (US 2022/0376844 A1) discloses Systems and methods for dynamic Hybrid Automatic Repeat Request (HARQ) codebook construction with enabling or disabling of HARQ Acknowledgment (HARQ-ACK) feedback per HARQ process. In one embodiment, a method performed by a wireless communication device comprises receiving, from a network node, information that configures the wireless communication device with a first set of HARQ processes for which HARQ-ACK feedback is disabled and a second set of HARQ processes for which HARQ-ACK feedback is enabled. The method further comprises receiving first downlink control information that schedules a first downlink shared channel transmission and determining that the transmission corresponds to one of the first set of HARQ processes for which HARQ-ACK feedback is disabled. The method further comprises, upon making this determination, performing a first set of actions for HARQ-ACK feedback generation for HARQ processes with HARQ-ACK feedback disabled {Figs.4-11}.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to PHUONGCHAU BA NGUYEN whose telephone number is (571) 272-3148. The examiner can normally be reached Monday-Thursday 7:30 AM -5:30 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, RICKY NGO can be reached on 571-272-3139. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format.
For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/PHUONGCHAU BA NGUYEN/ Primary Examiner, Art Unit 2464