Prosecution Insights
Last updated: July 17, 2026
Application No. 18/285,211

HARQ-ACK TRANSMISSION METHOD AND APPARATUS, AND READABLE STORAGE MEDIUM

Final Rejection §103
Filed
Sep 29, 2023
Priority
Mar 31, 2021 — nonprovisional of PCT/CN2021/084489 +1 more
Examiner
FAN, GUOXING
Art Unit
2462
Tech Center
2400 — Computer Networks
Assignee
Beijing Xiaomi Mobile Software Co., Ltd.
OA Round
2 (Final)
78%
Grant Probability
Favorable
3-4
OA Rounds
5m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 78% — above average
78%
Career Allowance Rate
25 granted / 32 resolved
+20.1% vs TC avg
Strong +26% interview lift
Without
With
+26.2%
Interview Lift
resolved cases with interview
Typical timeline
3y 3m
Avg Prosecution
35 currently pending
Career history
81
Total Applications
across all art units

Statute-Specific Performance

§103
93.4%
+53.4% vs TC avg
§102
5.2%
-34.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 32 resolved cases

Office Action

§103
DETAILED ACTION Applicant’s response filed on 03/11/2026 has been entered and made of record. 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 . Claim Status Claims 1-3, 5-6, 9-11, 15-17, 19 and 23 are amended. Claim 7 is cancelled. No new claim is/are added. Claims 1-6, 9-11, 13-17, 19 and 23-26 are pending for examination. Applicant Argument Applicant’s response has been fully considered. Below are applicant’s main arguments and examiner’s response to those arguments: Applicant’s argument: (remark pages 8-9), filed on 03/11/2026, with respect to claim 1, ‘Amended claim 1 recites in relevant part …However, DCI is a physical layer signaling instead of a higher layer signaling’. Examiner’s response: Examiner respectfully disagrees. First, DCI is a MAC layer (Layer 2) signaling, which is higher than a physical layer (Layer 1) signaling. Moreover, Oteri teaches higher layer parameter (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured”). Applicant’s argument: (remark page 9), filed on 03/11/2026, with respect to claim 1, ‘Further, Oteri expressly discusses priority with … Oteri fails to anticipate the limitation of amended claim I reciting "the second indication information indicates that the HARQ-ACKs having the priority greater than or equal to the first priority’. Examiner’s response: Examiner respectfully disagrees. In response to applicant's arguments against the references individually, examiner would like to mention that one cannot show nonobviousness by attacking references individually where the rejections are based on combinations of references. See In re Keller, 642 F.2d 413, 208 USPQ 871 (CCPA 1981); In re Merck & Co., 800 F.2d 1091, 231 USPQ 375 (Fed. Cir. 1986). Shi expressly teaches priority for HARQ-ACK (Shi: [0076]: “an HARQ-ACK with a priority higher than the first priority”). Applicant’s argument: (remark pages 10-11), filed on 03/11/2026, with respect to claim 1, ‘Second, on page 18 of the Office Action, the examiner acknowledges that Oteri fails to … Accordingly, amended claim 1 is allowable’. Examiner’s response: Examiner respectfully disagrees. Oteri teaches a high layer parameter “prioritylndicatorForDCI-Format1-x” indicates whether each PDSCH should have its own PUCCH, .i.e. whether the first sending mode should be disabled, which would implicitly teach a priority cutoff point whether to disable or not (Oteri: [0130]). Moreover, Shi teaches UE does not send HARQ-ACK in a second PUCCH resource if the flag in the DCI is a disable value (Shi: [0049], [0050]) and a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0076], [0051]). Therefore, combination of Oteri and Shi teaches the subject matters as claimed. See the detailed Office Action bellow under 35 U.S.C. § 103 section. Applicant’s arguments (remark pages 8-11), filed on 03/11/2026, with respect to claims 1-6, 9-11, 13-17, 19 and 23-26 have been considered but are moot in view of the new ground of rejection below which better address the claimed invention as amended. This Office Action is made Final. Claim Rejections - 35 USC § 103 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 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. Claims 1-6, 9-11, 13-17, 19 and 23-26 are rejected under 35 U.S.C. 103 as being unpatentable over Oteri et al. (US 20220400508 A1), hereinafter “Oteri”, in view of Shi et al. (US 20230011110 A1), hereinafter “Shi”. Per claim 1, 10, 23-26: Regarding claim 23, Oteri teaches ‘An HARQ-ACK transmission apparatus’ (Oteri: [FIG.4]: “BS”; [0031]: “FIG. 4 is a block diagram illustrating an example base station”; [0115]: “HARQ-ACK feedback”); ‘comprising; a processor’ (Oteri: [FIG.4]: “Processor(s)”); ‘a memory’ (Oteri: [FIG.4]: “Memory”); ‘wherein the memory is configured to store instructions executable by the processor’ (Oteri: [0101]: “the processor 404 of the base station 102 may be configured to implement part or all of the methods described herein, e.g., by executing program instructions stored on a memory”); ‘wherein the processor is configured to perform acts comprising: sending, to a UE, information indicating an HARQ-ACK sending mode, wherein the HARQ- ACK sending mode comprises a first sending mode or a second sending mode’ (Oteri: [0006]: “The base station may transmit the downlink control message to a user equipment (UE)”; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”; [0133]: “the DCI may include two K1 values”; [0115]: “a PDSCH may provide HARQ-ACK feedback via a PUCCH. The HARQ-ACK feedback may indicate whether the associated PDSCH was successfully received”; [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”, “PUCCH all”, same PUCCH for all PDSCH (second sending mode); [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1” -> “PUCCH1,1”, low priority: “PDSCH3,0”-“PDSCH4,0”-> “PUCCH3,0”, different PUCCHs (first sending mode)); ‘wherein the first sending mode corresponds to sending a plurality of HARQ-ACKs on different PUCCHs’ (FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1” -> “PUCCH1,1”, low priority: “PDSCH3,0”-“PDSCH4,0”-> “PUCCH3,0”, different PUCCH for different priority; [0128]-[0129]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”) … the feedback for the high-priority PDSCH transmissions PDSCH1 and PDSCH2) may be scheduled according to PR110, while the other feedback transmission (e.g., the feedback for the low-priority PDSCH transmissions PDSCH3 and PDSCH4) may be scheduled according to PR111 (or another PRI value)”; [0133]: “the DCI may include two K1 values”; sending HARQ-ACK associated with each “PDSCH1,1”-“PDSCH2,1” and “PDSCH3,0”-“PDSCH4,0” (a plurality of HARQ-ACKs) on a different PUCCHs); ‘wherein the second sending mode corresponds to sending a plurality of HARQ-ACKs on a same PUCCH’ ([FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”, “PUCCH all”, same PUCCH for all PDSCH; [0121]: “A single DCI may include DL grants for each of these PDSCH transmissions … The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback for all PDSCH transmissions in the multi-PDSCH transmission is scheduled to be transmitted in the slot that is K1 slots (e.g., 2 slots) after PDSCH4. Additionally, a single PUCCH resource set may be identified, based on the size of the combined feedback”; [0117]: “for a multi-PDSCH transmission including some number “N” PDSCH transmissions, a single PUCCH feedback resource may be scheduled for all N of the PDSCH transmissions”, sending HARQ-ACK associated with each “PDSCH1”-“PDSCH4” (a plurality of HARQ-ACKs) on a same PUCCH); ‘receiving, from the UE, an HARQ-ACK’ (Oteri: [0017]: “The UE may then transmit the feedback information for each of the payload data messages, via the determined uplink resources”, base station would receive HARQ-ACK from the UE); ‘wherein the information indicating the HARQ-ACK sending mode comprises second indication information conveyed via higher-layer signaling independent of downlink control information (DCI), wherein the second indication information disables a first sending mode for HARQ-ACKs having a priority greater than or equal to a first priority’ (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a flag whether each PDSCH should have its own PUCCH, i.e. whether the first sending mode should be disabled, where the parameter “prioritylndicatorForDCI-Format1-x” would implicitly teach a priority cutoff point whether to disable or not; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode) in DCI; [0128]-[0129]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”) … the feedback for the high-priority PDSCH transmissions PDSCH1 and PDSCH2) may be scheduled according to PR110, while the other feedback transmission (e.g., the feedback for the low-priority PDSCH transmissions PDSCH3 and PDSCH4) may be scheduled according to PR111 (or another PRI value)”, DCI indicating the first sending mode with a priority value 1). Although Oteri’s teaching of prioritylndicatorForDCI-Format1-x would implicitly teach a priority cutoff point whether to disable first sending mode or not, Oteri fails to expressly teach for HARQ-ACKs having a priority greater than or equal to a first priority. Nevertheless, Shi in the same field of endeavor teaches DCI includes a flag and UE does not send HARQ-ACK in a second PUCCH resource if the flag in the DCI is a disable value (Shi: [0049]: “the UE may receive a second DCI (DCI-2) including a numerical K1-2 and a feedback flag”; [0050]: “The UE may determine whether the feedback flag is equal to a preset enable value or is equal to a preset disable value … In response to the feedback flag in the DCI-2 is the preset disable value, the UE may not send the stored HARQ-ACK on PUCCH2”) and a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0076]: “an HARQ-ACK with a priority higher than the first priority”; [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter to indicate to disables a first sending mode for HARQ-ACKs having a priority greater than or equal to a first priority in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Combination of Oteri and Shi teaches ‘wherein the second indication information indicates that the HARQ-ACKs having the priority greater than or equal to the first priority are transmitted on a same physical uplink control channel (PUCCH) using a second sending mode’ (Oteri: [FIG.8]; [0117]: “for a multi-PDSCH transmission including some number “N” PDSCH transmissions, a single PUCCH feedback resource may be scheduled for all N of the PDSCH transmissions”, sending HARQ-ACK associated with each “PDSCH1”-“PDSCH4” (a plurality of HARQ-ACKs) on a same PUCCH. Shi: [0050]: “The UE may determine whether the feedback flag is equal to a preset enable value or is equal to a preset disable value … In response to the feedback flag in the DCI-2 is the preset disable value, the UE may not send the stored HARQ-ACK on PUCCH2”; [0051]: “there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching of preset priority threshold with that of Oteri in order to send HARQ-ACK based on a preset rule (Shi: [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). Regarding claim 10, Oteri teaches ‘A hybrid automatic repeat request acknowledgement (HARQ-ACK) transmission method’ (Oteri: [0017]: “a method is disclosed for signaling feedback scheduling in a wireless communication network”; [0115]: “HARQ-ACK feedback”); ‘comprising: receiving, by a user equipment (UE) from a network device, information indicating an HARQ-ACK sending mode, wherein the HARQ-ACK sending mode comprises a first sending mode or a second sending mode’ (Oteri: [0006]: “The base station may transmit the downlink control message to a user equipment (UE)”, UE would receive control message from base station; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”; [0133]: “the DCI may include two K1 values”; [0115]: “a PDSCH may provide HARQ-ACK feedback via a PUCCH. The HARQ-ACK feedback may indicate whether the associated PDSCH was successfully received”; [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”, “PUCCH all”, same PUCCH for all PDSCH (second sending mode); [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1” -> “PUCCH1,1”, low priority: “PDSCH3,0”-“PDSCH4,0”-> “PUCCH3,0”, different PUCCHs (first sending mode)); ‘wherein the first sending mode corresponds to sending a plurality of HARQ-ACKs on different physical uplink control channels (PUCCHs)’ (FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1” -> “PUCCH1,1”, low priority: “PDSCH3,0”-“PDSCH4,0”-> “PUCCH3,0”, different PUCCH for different priority; [0128]-[0129]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”) … the feedback for the high-priority PDSCH transmissions PDSCH1 and PDSCH2) may be scheduled according to PR110, while the other feedback transmission (e.g., the feedback for the low-priority PDSCH transmissions PDSCH3 and PDSCH4) may be scheduled according to PR111 (or another PRI value)”; [0133]: “the DCI may include two K1 values”; sending HARQ-ACK associated with each “PDSCH1,1”-“PDSCH2,1” and “PDSCH3,0”-“PDSCH4,0” (a plurality of HARQ-ACKs) on a different PUCCHs); ‘wherein the second sending mode corresponds to sending a plurality of HARQ-ACKs on a same PUCCH’ (([FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”, “PUCCH all”, same PUCCH for all PDSCH; [0121]: “A single DCI may include DL grants for each of these PDSCH transmissions … The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback for all PDSCH transmissions in the multi-PDSCH transmission is scheduled to be transmitted in the slot that is K1 slots (e.g., 2 slots) after PDSCH4. Additionally, a single PUCCH resource set may be identified, based on the size of the combined feedback”; [0117]: “for a multi-PDSCH transmission including some number “N” PDSCH transmissions, a single PUCCH feedback resource may be scheduled for all N of the PDSCH transmissions”, sending HARQ-ACK associated with each “PDSCH1”-“PDSCH4” (a plurality of HARQ-ACKs) on a same PUCCH); ‘determining, by the UE, the HARQ-ACK sending mode based on the information used for indicating the HARQ-ACK sending mode’ (Oteri: [0017]: “The UE may determine uplink resources for use in transmitting feedback information for each of the payload data messages, wherein the determining is based on parameters included in the downlink control message”, UE would determine whether send HARQ-ACK feedback on a same PUCCH or different PUCCHs based on DCI); ‘sending, by the UE, the HARQ-ACK to the network device by using the HARQ-ACK sending mode’ (Oteri: [0017]: “The UE may then transmit the feedback information for each of the payload data messages, via the determined uplink resources”); ‘determining, based on information indicating the HARQ-ACK sending mode, that the HARQ-ACK sending mode is the second sending mode’ (Oteri: [FIG.8]: (([FIG.8]: “PDSCH1” – “PDSCH4”, “PUCCH all”, same PUCCH for all PDSCH (second sending mode)); ‘wherein the information indicating the HARQ-ACK sending mode comprises second indication information conveyed via higher-layer signaling independent of downlink control information (DCI), wherein the second indication information disables a first sending mode for HARQ-ACKs having a priority greater than or equal to a first priority’ (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a flag whether each PDSCH should have its own PUCCH, i.e. whether the first sending mode should be disabled, where the parameter “prioritylndicatorForDCI-Format1-x” would implicitly teach a priority cutoff point whether to disable or not; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode) in DCI; [0128]-[0129]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”) … the feedback for the high-priority PDSCH transmissions PDSCH1 and PDSCH2) may be scheduled according to PR110, while the other feedback transmission (e.g., the feedback for the low-priority PDSCH transmissions PDSCH3 and PDSCH4) may be scheduled according to PR111 (or another PRI value)”, DCI indicating the first sending mode with a priority value 1). Although Oteri’s teaching of prioritylndicatorForDCI-Format1-x would implicitly teach a priority cutoff point whether to disable first sending mode or not, Oteri fails to expressly teach for HARQ-ACKs having a priority greater than or equal to a first priority. Nevertheless, Shi in the same field of endeavor teaches DCI includes a flag and UE does not send HARQ-ACK in a second PUCCH resource if the flag in the DCI is a disable value (Shi: [0049]: “the UE may receive a second DCI (DCI-2) including a numerical K1-2 and a feedback flag”; [0050]: “The UE may determine whether the feedback flag is equal to a preset enable value or is equal to a preset disable value … In response to the feedback flag in the DCI-2 is the preset disable value, the UE may not send the stored HARQ-ACK on PUCCH2”) and a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0076]: “an HARQ-ACK with a priority higher than the first priority”; [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter to indicate to disables a first sending mode for HARQ-ACKs having a priority greater than or equal to a first priority in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Combination of Oteri and Shi teaches ‘wherein the second indication information indicates that the HARQ-ACKs having the priority greater than or equal to the first priority are transmitted on a same physical uplink control channel (PUCCH) using a second sending mode’ (Oteri: [FIG.8]; [0117]: “for a multi-PDSCH transmission including some number “N” PDSCH transmissions, a single PUCCH feedback resource may be scheduled for all N of the PDSCH transmissions”, sending HARQ-ACK associated with each “PDSCH1”-“PDSCH4” (a plurality of HARQ-ACKs) on a same PUCCH. Shi: [0050]: “The UE may determine whether the feedback flag is equal to a preset enable value or is equal to a preset disable value … In response to the feedback flag in the DCI-2 is the preset disable value, the UE may not send the stored HARQ-ACK on PUCCH2”; [0051]: “there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching of preset priority threshold with that of Oteri in order to send HARQ-ACK based on a preset rule (Shi: [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). Regarding claim 24, Oteri teaches ‘An HARQ-ACK transmission apparatus’ (Oteri: [FIG.3]: “UE”; [0115]: “HARQ-ACK feedback”); ‘comprising a processor and a memory’ (Oteri: [FIG.3]: “Processor(s)”, “Memory”); ‘wherein the memory is configured to store instructions executable by the processor’ (Oteri: [0095]: “The processor(s) 302 of the UE device 106/107 may be configured to implement part or all of the methods described herein, e.g., by executing program instructions stored on a memory”); ‘wherein the processor is configured to implement’ (this is implied); ‘the method according to claim 10’ (discussed in claim 10 above). Regarding claim 1, claim 1 recites the method implemented by the communication device of claim 23 (see rejection of claim 23 above). Regarding claim 25, claim 25 recites the memory implemented by the communication device of claim 23 (see rejection of claim 23 above). Regarding claim 26, claim 26 recites the memory implemented by the communication device of claim 24 (see rejection of claim 24 above). Per claim 2 and 11: Regarding claim 2, Oteri teaches the method according to claim 1 (discussed above). Oteri teaches ‘first auxiliary information, wherein the first auxiliary information is information, in the higher layer signaling, indicating that the first sending mode is configured for the HARQ-ACK having the first priority’ (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a higher layer parameter (a first auxiliary information) indicating a given DCI format would have different PUCCH for each PDSCH (the first sending mode); [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [FIG.11]: each PDSCH with its own PUCCH; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”). However, Oteri fails to expressly teach the higher layer parameter (a first auxiliary information) indicating a priority. However, Shi in the same field of endeavor teaches a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a priority in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Regarding claim 11, Oteri teaches the method according to claim 10 (discussed above). Oteri teaches ‘receiving, by the UE, first auxiliary information from the network device, wherein the first auxiliary information is information, in the higher layer signaling, indicating that the first sending mode is configured for the HARQ-ACK having a first priority’ (Oteri: [0006]: “The base station may transmit the downlink control message to a user equipment (UE)”; [0010]: “the indicated uplink resources may specify a plurality of uplink messages for transmission of the acknowledgment feedback for respective payload data messages of the plurality of payload data messages”; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode); [0133]: “the DCI may include two K1 values”, two different PUCCHs (the first sending mode); UE would receive DCI from network; [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a higher layer parameter (a first auxiliary information) indicating a given DCI format would have different PUCCH for each PDSCH (the first sending mode); [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [FIG.11]: each PDSCH with its own PUCCH; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”). However, Oteri fails to expressly teach the higher layer parameter (a first auxiliary information) indicating a priority; ‘the HARQ-ACK with a priority higher than the first priority’ (this is optional). However, Shi teaches a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a priority in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Regarding claim 3, Oteri teaches the method according to claim 1 (discussed above). Oteri teaches ‘first auxiliary information, wherein the first auxiliary information is information, in the higher layer signaling, indicating that the first sending mode is configured for the HARQ-ACK having the priority higher than the first priority’ (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a higher layer parameter (a first auxiliary information) indicating a given DCI format would have different PUCCH for each PDSCH (the first sending mode); [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [FIG.11]: each PDSCH with its own PUCCH; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”). However, Oteri fails to expressly teach the higher layer parameter (a first auxiliary information) indicating the priority higher than the first priority. However, Shi teaches a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a preset priority threshold in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Per claim 4 and 13: Regarding claim 4, combination of Oteri and Shi teaches the method according to claim 2 (discussed above). Oteri teaches ‘second auxiliary information, wherein the second auxiliary information is priority information indicated by a priority indication information field in a downlink control information (DCI), wherein the priority information indicates priorities of HARQ-ACKs corresponding to a plurality of physical downlink shared channels (PDSCHs) scheduled by the DCI’ (Oteri: [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”, DCI could include priority indication (second auxiliary information) for a plurality of PDSCHs). Regarding claim 13, combination of Oteri and Shi teaches the method according to claim 11 (discussed above). Oteri teaches ‘receiving, by the UE, second auxiliary information from the network device, wherein the second auxiliary information is priority information indicated by a priority indication information field in a downlink control information (DCI), wherein the priority information indicates priorities of HARQ-ACKs corresponding to a plurality of physical downlink shared channels (PDSCHs) scheduled by the DCI’ (Oteri: [0006]: “The base station may transmit the downlink control message to a user equipment (UE)”; [0010]: “the indicated uplink resources may specify a plurality of uplink messages for transmission of the acknowledgment feedback for respective payload data messages of the plurality of payload data messages”; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode); [0133]: “the DCI may include two K1 values”, two different PUCCHs (the first sending mode); UE would receive DCI from network; [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”, DCI could include priority indication (second auxiliary information) for a plurality of PDSCHs). Per claim 5 and 16: Regarding claim 5, Oteri teaches the method according to claim 1 (discussed above). Oteri teaches ‘first indication information in the higher layer signaling, wherein the first indication information indicates that the first sending mode is configured for an HARQ-ACK having any priority’ (Oteri: [FIG.8]; [FIG.11]: no priority associated with “PDSCH1” – “PDSCH4” ”, each PDSCH has its own PUCCH (the first sending mode); [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”). Regarding claim 16, Oteri teaches the method according to claim 10 (discussed above). Oteri teaches ‘determining, in response to that the information indicating the HARQ-ACK sending mode is first indication information in the higher layer signaling, wherein the first indication information indicates that the first sending mode is configured for an HARQ-ACK baving any priority,’ (Oteri: [0133]: “the DCI may include two K1 values”, two different PUCCHs (the first sending mode); [0133]: “the DCI may include two K1 values”; indication information in a DCI (a higher layer signaling); [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”); ‘the HARQ-ACK sending mode is the first sending mode’ (Oteri: [0129]: “the feedback for the high-priority PDSCH transmissions PDSCH1 and PDSCH2) may be scheduled according to PR110, while the other feedback transmission (e.g., the feedback for the low-priority PDSCH transmissions PDSCH3 and PDSCH4) may be scheduled according to PR111 (or another PRI value)”; [FIG.11]: each PDSCH has its own PUCCH; sending on different PUCCHs (the first sending mode)). Per claim 6 and 17: Regarding claim 6, Oteri teaches the method according to claim 1 (discussed above). Oteri teaches ‘wherein the second indication information in the higher layer signaling does not carry first auxiliary information’ (Oteri: [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode); [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; indicate the second sending mode in DCI (higher layer signaling) which does not include priority indicator; [0130]: a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a higher layer parameter may be not configured if PDSCHs with different priority could share a MCS field); ‘wherein the first auxiliary information indicates that the first sending mode is configured for the HARQ-ACK having the first priority or for the HARQ-ACK having the priority higher than the first priority’ (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a higher layer parameter (a first auxiliary information) indicating a given DCI format would have different PUCCH for each PDSCH (the first sending mode); [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [FIG.11]: each PDSCH with its own PUCCH; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”). However, Oteri fails to expressly teach the higher layer parameter (a first auxiliary information) indicating a priority higher than a first priority. However, Shi teaches a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a preset priority threshold in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Regarding claim 17, Oteri teaches the method according to claim 10 (discussed above). Oteri teaches ‘determining, in response to that the information indicating the HARQ-ACK sending mode is the higher layer signaling without carrying first auxiliary information’ (Oteri: [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode); [FIG.8]: no priority associated with “PDSCH1” – “PDSCH4”; indicate the second sending mode in DCI (higher layer signaling) which does not include priority indicator (auxiliary information)); ‘wherein the first auxiliary information indicates that the first sending mode is configured for the HARQ- ACK having the first priority’ (Oteri: [0010]: “the indicated uplink resources may specify a plurality of uplink messages for transmission of the acknowledgment feedback for respective payload data messages of the plurality of payload data messages”; [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode); [0133]: “the DCI may include two K1 values”, two different PUCCHs (the first sending mode); [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”, a higher layer parameter (a first auxiliary information) indicating a given DCI format would have different PUCCH for each PDSCH (the first sending mode); [FIG.9]: high priority: “PDSCH1,1”-“PDSCH2,1”; low priority: “PDSCH3,0”-“PDSCH4,0”; [FIG.11]: each PDSCH with its own PUCCH; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”). However, Oteri fails to expressly teach the higher layer parameter (a first auxiliary information) indicating a priority; ‘the HARQ-ACK having the priority higher than the first priority’ (this is optional). ‘the HARQ-ACK sending mode is the second sending mode’ (Oteri: [0121]:”The DCI may also include a K1 value”; [FIG.8]: “PDSCH1”-“PDSCH4” -> “PUCCH all”; [0117]: “for a multi-PDSCH transmission including some number “N” PDSCH transmissions, a single PUCCH feedback resource may be scheduled for all N of the PDSCH transmissions”, one same PUCCH (the second sending mode)). However, Shi teaches a preset priority threshold to determine priority indication in a DCI being high-priority value if the priority indicator is larger than the preset priority threshold (Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a priority in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Regarding claim 9, Oteri teaches the method according to claim 1 (discussed above). Oteri teaches ‘third indication information in the higher layer signaling, wherein the third indication indicates that the first sending mode is disabled for the HARQ-ACK having any priority’ (Oteri: [FIG.8], [FIG.11]: no priority associated with “PDSCH1” – “PDSCH4”; indicate the second sending mode in DCI; [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”). However, Oteri fails to expressly teach indicating the first sending mode is disabled. However, Shi teaches DCI includes a flag and UE does not send HARQ-ACK in a second PUCCH resource if the flag in the DCI is a disable value (Shi: [0049]: “the UE may receive a second DCI (DCI-2) including a numerical K1-2 and a feedback flag”; [0050]: “The UE may determine whether the feedback flag is equal to a preset enable value or is equal to a preset disable value … In response to the feedback flag in the DCI-2 is the preset disable value, the UE may not send the stored HARQ-ACK on PUCCH2”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching with that of Oteri for the third indication information is used for indicating that the first sending mode is disabled for an HARQ-ACK with any priority in order to send HARQ-ACK based on a preset rule (see reference quotes in element above). Regarding claim 14, combination of Oteri and Shi teaches the method according to claim 13 (discussed above). Combination of Oteri and Shi teaches ‘determining the HARQ-ACK sending mode based on the first auxiliary information and the second auxiliary information’ (Oteri: [0121]: “The DCI may also include a K1 value (e.g., 2)”; [0133]: “the DCI may include two K1 values”; [0017]: “The UE may determine uplink resources for use in transmitting feedback information for each of the payload data messages, wherein the determining is based on parameters included in the downlink control message”; [0128]-[0129]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”) … the feedback for the high-priority PDSCH transmissions PDSCH1 and PDSCH2) may be scheduled according to PR110, while the other feedback transmission (e.g., the feedback for the low-priority PDSCH transmissions PDSCH3 and PDSCH4) may be scheduled according to PR111 (or another PRI value)”, would determine sending mode based on second auxiliary information; [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”. Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”; [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”, would determine sending mode based on the first auxiliary information). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching of preset priority threshold with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a preset priority threshold in order to send HARQ-ACK based on a preset rule (Shi: [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). Regarding claim 15, combination of Oteri and Shi teaches the method according to claim 14 (discussed above). Combination of Oteri and Shi teaches ‘determining, in response to that the first auxiliary information indicates that the first sending mode is configured for the HARQ-ACK having the first priority, and the second auxiliary information indicates the first priority, the HARQ-ACK sending mode is the first sending mode’ (Oteri: [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag”; [0128]: “the DCI may include an indication that PDSCH1 and PDSCH2 are high-priority (e.g., illustrated as priority value “1”). The DCI may also include an indication that PDSCH3 and PDSCH4 are low-priority (e.g., illustrated as priority value “0”)”. Shi: [0051]: “the DCI-2 may include a K1-2 and a priority indicator … there may be a preset priority threshold, and the UE determine that the priority indicator is high priority when the priority indicator is larger than the preset priority threshold, and the priority indicator is low priority when the priority indicator is not larger than the preset priority threshold”); ‘determining, in response to that the first auxiliary information indicates that the first sending mode is configured for the HARQ-ACK with the first priority, and the second auxiliary information does not indicate the first priority, the HARQ-ACK sending mode is the second sending mode; determining, in response to that the first auxiliary information indicates that the first sending mode is configured for the HARQ-ACK with the priority higher than the first priority, and the second auxiliary information indicates the priority higher than the first priority, the HARQ-ACK sending mode is the first sending mode; or determining, in response to that the first auxiliary information indicates that the first sending mode is configured for the HARQ-ACK with the priority higher than the first priority, and the second auxiliary information indicates a priority lower than or equal to the first priority, the HARQ-ACK sending mode is the second sending mode’ (these are optional). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine Shi’s teaching of preset priority threshold with that of Oteri for the higher layer parameter (the first auxiliary information) to indicate a priority in order to send HARQ-ACK based on a preset rule (Shi: [Abstract]: “The method includes sending a hybrid automated repeat request-acknowledgement (HARQ-ACK) in response to a preset rule being satisfied”). Regarding claim 19, Oteri teaches the method according to claim 10 (discussed above). Oteri teaches ‘determining, in response to that the information indicating the HARQ-ACK sending mode is the higher layer signaling without carrying first indication information’ (Oteri: [0121]: “The DCI may also include a K1 value (e.g., 2), which indicates that HARQ-ACK feedback”, indicating one PUCCH (the second sending mode); [FIG.8], [FIG.11]: no priority associated with “PDSCH1” – “PDSCH4”; indicate the second sending mode in DCI (higher layer signaling) which does not include priority indicator (first indication information)); ‘wherein the first indication information indicates that the first sending mode is configured for an HARQ-ACK having any priority’ (Oteri: [FIG.8]; [FIG.11]: no priority associated with “PDSCH1” – “PDSCH4”; [0130]: “a particular higher layer parameter (e.g., prioritylndicatorForDCI-Format1-x) may be configured as a flag that the UE may not be expected to receive a multi-PDSCH scheduling DCI with different values of the priority indicator field. This may be useful in that PDSCH transmissions with different priority may have different block error ratio (BLER) requirements, which may make sharing an MCS field difficult”); ‘the HARQ-ACK sending mode is the second sending mode’ (Oteri: [0121]:”The DCI may also include a K1 value”; [FIG.8]: “PDSCH1”-“PDSCH4” -> “PUCCH all”; [0117]: “for a multi-PDSCH transmission including some number “N” PDSCH transmissions, a single PUCCH feedback resource may be scheduled for all N of the PDSCH transmissions”, sending one same PUCCH (the second sending mode)). Conclusion 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 action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) 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 mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to GUOXING FAN whose telephone number is (703)756-1310. The examiner can normally be reached Monday - Friday 9:00 am - 5:30 pm ET. 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, Yemane Mesfin can be reached at (571)272-3927. 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. /G.F./Examiner, Art Unit 2462 /YEMANE MESFIN/Supervisory Patent Examiner, Art Unit 2462
Read full office action

Prosecution Timeline

Sep 29, 2023
Application Filed
Dec 11, 2025
Non-Final Rejection mailed — §103
Mar 11, 2026
Response Filed
May 05, 2026
Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12676806
SELECTION OF CANDIDATE DATA FLOWS FOR EVALUATING PERFORMANCE METRICS USING PASSIVE MEASUREMENTS
4y 2m to grant Granted Jul 07, 2026
Patent 12647240
SELECTING AN ANTENNA ARRAY FOR BEAM MANAGEMENT
3y 8m to grant Granted Jun 02, 2026
Patent 12647804
SIGNAL MEASUREMENT METHOD, MEASUREMENT GAP CONFIGURATION METHOD, TERMINAL, AND NETWORK DEVICE
3y 8m to grant Granted Jun 02, 2026
Patent 12641558
NETWORK SYNCHRONIZATION FOR MBS SFN
3y 7m to grant Granted May 26, 2026
Patent 12621831
CLIENT DEVICE AND NETWORK ACCESS NODE FOR MANAGEMENT OF CCH MONITORING CAPABILITIES
3y 7m to grant Granted May 05, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
78%
Grant Probability
99%
With Interview (+26.2%)
3y 3m (~5m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 32 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month