CTNF 18/726,846 CTNF 85746 Notice of Pre-AIA or AIA Status 07-03-aia AIA 15-10-aia The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. DETAILED ACTION This Office Action is in response to the Applicants' communication filed on 7/5/2024. In virtue of this communication, claims 1-3 are currently presented in the instant application. Claim Rejections - 35 USC § 102 07-06 AIA 15-10-15 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. 07-07-aia AIA 07-07 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 – 07-12-aia AIA (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. 07-15-03-aia AIA Claim s 1-3 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by US Patent Application Publication 20220353891 (hereinafter referred to as Kang) . Consider claim 1, Kang teaches a user equipment (UE) (see at least ¶ [0475], “…UE…”), comprising: a processor (see at least ¶ [0475], “…processors 102…”) and a memory storing instructions (see at least ¶ [0475], “…memories 104…”), wherein the instructions, when run by the processor, cause the UE to: in a case that a high priority (HP) physical uplink control channel (PUCCH) for more than 2 bits of HP hybrid automatic repeat request-acknowledgement (HARQ-ACK) with PUCCH format 2 or PUCCH format 3 or PUCCH format 4 overlaps with K PUCCHs for respective K HP scheduling requests (SRs) (see at least ¶ [0348], “…PUCCH Format 2…” and see at least ¶ [0351], “…PUCCH Format 3…” and see at least ¶ [0352], “…PUCCH Format 4 may support UCI having two bits or more along with multiplexing…” and see at least ¶ [0444], “…HARQ-ACK PUCCH is a PUCCH having high priority…” and see at least ¶ [0457], “…a HARQ-ACK PUCCH (configured as the PUCCH format 1) and a BFRQ-PUCCH (configured as the PUCCH format 0) collide against each other, a corresponding BFRQ is a high priority BFRQ (i.e., high priority BFRQ), a UE may drop a HARQ-ACK PUCCH (with respect to HARQ-ACK having specific priority (e.g., low priority))…”) and a low priority (LP) physical uplink shared channel (PUSCH), and if HP HARQ-ACK multiplexing on the LP PUSCH is configured (see at least ¶ [0457], “…a HARQ-ACK PUCCH (configured as the PUCCH format 1) and a BFRQ-PUCCH (configured as the PUCCH format 0) collide against each other, a corresponding BFRQ is a high priority BFRQ (i.e., high priority BFRQ), a UE may drop a HARQ-ACK PUCCH (with respect to HARQ-ACK having specific priority (e.g., low priority))…”), append [log 2 (K+1)] bits for HP scheduling request (SR) to the HP HARQ-ACK (see at least ¶ [0366], “…CSI PUCCH format 2/3/4+SR PUCCH format 0/1: in the case of a configured K SR PUCCH, UCI in which ceil (log 2 (K+1)) bits…”); and if there is no positive HP SR to be reported, drop the [log 2 (K+1)] bits and multiplex only HP HARQ-ACK bits on the LP PUSCH (see at least ¶ [0366], “…CSI PUCCH format 2/3/4+SR PUCCH format 0/1: in the case of a configured K SR PUCCH, UCI in which ceil (log 2 (K+1)) bits indicating (all) negative or positive SR (ID) are added and combined with CSI feedback bits may be transmitted in the CSI PUCCH format 2/3/4 resource…” also see table 11). Consider claim 2, Kang teaches a base station (gNB) (see at least ¶ [0469], “…base station…”), comprising: a processor (see at least ¶ [0469], “…processor…”) and a memory storing instructions, wherein the instructions (see at least ¶ [0469], “…a memory (e.g., 104, 204 in FIG. 18) in the form of an instruction/program (e.g., instruction, executable code) for driving at least one processor…”), when run by the processor, cause the UE to: in a case that a high priority (HP) physical uplink control channel (PUCCH) for more than 2 bits of HP hybrid automatic repeat request-acknowledgement (HARQ-ACK) with PUCCH format 2 or PUCCH format 3 or PUCCH format 4 overlaps with K PUCCHs for respective K HP scheduling requests (SRs) (see at least ¶ [0348], “…PUCCH Format 2…” and see at least ¶ [0351], “…PUCCH Format 3…” and see at least ¶ [0352], “…PUCCH Format 4 may support UCI having two bits or more along with multiplexing…” and see at least ¶ [0444], “…HARQ-ACK PUCCH is a PUCCH having high priority…” and see at least ¶ [0457], “…a HARQ-ACK PUCCH (configured as the PUCCH format 1) and a BFRQ-PUCCH (configured as the PUCCH format 0) collide against each other, a corresponding BFRQ is a high priority BFRQ (i.e., high priority BFRQ), a UE may drop a HARQ-ACK PUCCH (with respect to HARQ-ACK having specific priority (e.g., low priority))…”) and a low priority (LP) physical uplink shared channel (PUSCH), and if HP HARQ-ACK multiplexing on the LP PUSCH is configured, if there is positive HP SR to be reported, receive a combination of HP HARQ-ACK bits and HP scheduling request (SR) bits multiplexed on the LP PUSCH as HP HARQ-ACK bits (see at least ¶ [0457], “…a HARQ-ACK PUCCH (configured as the PUCCH format 1) and a BFRQ-PUCCH (configured as the PUCCH format 0) collide against each other, a corresponding BFRQ is a high priority BFRQ (i.e., high priority BFRQ), a UE may drop a HARQ-ACK PUCCH (with respect to HARQ-ACK having specific priority (e.g., low priority))…”), wherein [log 2 (K+1)] bits for HP SR are appended to the HP HARQ-ACK (see at least ¶ [0366], “…CSI PUCCH format 2/3/4+SR PUCCH format 0/1: in the case of a configured K SR PUCCH, UCI in which ceil (log 2 (K+1)) bits…”), and if there is no positive HP SR to be reported, receive only HP HARQ-ACK bits multiplexed on the LP PUSCH (see at least ¶ [0366], “…CSI PUCCH format 2/3/4+SR PUCCH format 0/1: in the case of a configured K SR PUCCH, UCI in which ceil (log 2 (K+1)) bits indicating (all) negative or positive SR (ID) are added and combined with CSI feedback bits may be transmitted in the CSI PUCCH format 2/3/4 resource…” also see table 11).. Consider claim 3, Kang teaches a method performed by user equipment (UE), the method comprising: in a case that a high priority (HP) physical uplink control channel (PUCCH) for more than 2 bits of HP hybrid automatic repeat request-acknowledgement (HARQ-ACK) with PUCCH format 2 or PUCCH format 3 or PUCCH format 4 overlaps with K PUCCHs for respective K HP scheduling requests (SRs) (see at least ¶ [0348], “…PUCCH Format 2…” and see at least ¶ [0351], “…PUCCH Format 3…” and see at least ¶ [0352], “…PUCCH Format 4 may support UCI having two bits or more along with multiplexing…” and see at least ¶ [0444], “…HARQ-ACK PUCCH is a PUCCH having high priority…” and see at least ¶ [0457], “…a HARQ-ACK PUCCH (configured as the PUCCH format 1) and a BFRQ-PUCCH (configured as the PUCCH format 0) collide against each other, a corresponding BFRQ is a high priority BFRQ (i.e., high priority BFRQ), a UE may drop a HARQ-ACK PUCCH (with respect to HARQ-ACK having specific priority (e.g., low priority))…”) and a low priority (LP) physical uplink shared channel (PUSCH), and if HP HARQ-ACK multiplexing on the LP PUSCH is configured (see at least ¶ [0457], “…a HARQ-ACK PUCCH (configured as the PUCCH format 1) and a BFRQ-PUCCH (configured as the PUCCH format 0) collide against each other, a corresponding BFRQ is a high priority BFRQ (i.e., high priority BFRQ), a UE may drop a HARQ-ACK PUCCH (with respect to HARQ-ACK having specific priority (e.g., low priority))…”), appending [log.sub.2(K+1)] bits for HP scheduling request (SR) to the HP HARQ-ACK (see at least ¶ [0366], “…CSI PUCCH format 2/3/4+SR PUCCH format 0/1: in the case of a configured K SR PUCCH, UCI in which ceil (log 2 (K+1)) bits…”); and if there is no positive HP SR to be reported, dropping the [log 2 (K+1)] bits and multiplexing only HP HARQ-ACK bits on the LP PUSCH (see at least ¶ [0366], “…CSI PUCCH format 2/3/4+SR PUCCH format 0/1: in the case of a configured K SR PUCCH, UCI in which ceil (log 2 (K+1)) bits indicating (all) negative or positive SR (ID) are added and combined with CSI feedback bits may be transmitted in the CSI PUCCH format 2/3/4 resource…” also see table 11). Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHUONG A NGO whose telephone number is (571)270-7264. The examiner can normally be reached Monday-Thursday from 5:30AM-3:30PM. 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, Anthony S Addy can be reached at (571) 272-7795. 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. /CHUONG A NGO/Primary Examiner, Art Unit 2645 Application/Control Number: 18/726,846 Page 2 Art Unit: 2645 Application/Control Number: 18/726,846 Page 3 Art Unit: 2645 Application/Control Number: 18/726,846 Page 4 Art Unit: 2645 Application/Control Number: 18/726,846 Page 5 Art Unit: 2645 Application/Control Number: 18/726,846 Page 6 Art Unit: 2645 Application/Control Number: 18/726,846 Page 7 Art Unit: 2645
Prosecution Insights