DETAILED ACTION
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
In the event the determination of the status of the application as subject to AIA 35U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, anycorrection of the statutory basis for the rejection will not be considered a new ground ofrejection if the prior art relied upon, and the rationale supporting the rejection, would bethe same under either status.
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 02/02/2026 has been entered.
Claim Rejections - 35 USC § 103
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 non-obviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claim(s) 1, 11, 16 and 26 is/are rejected under 35 U.S.C. 103 as being unpatentable over Wang et al. (US 2023/0370209 A1) in view of Lei et al. (US 2022/0385411 A1).
Regarding claim 1, Wang et al. teach an apparatus of a user equipment (UE) for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory includes instructions executable by the one or more processors to cause the UE to (Figs. 2 and 12, [0217-0218, ], device 1200 can be considered as a further example embodiment of the network device 110, the terminal device 120, or the terminal device 130 as shown in fig. 2. Accordingly, the device 1200 can be implemented at or as at least a part of the network device 110, the terminal device 120, or the terminal device 130. The device 1200 includes a processor 1210, a memory 1220 coupled to the processor 1210, a suitable transmitter (TX) and receiver (RX) 1240 coupled to the processor 1210. The memory 1220 stores at least a part of a program 1230. The program 1230 is assumed to include program instructions that, when executed by the associated processor 1210, enable the device 1200 to operate in accordance with the embodiments of the present disclosure),
Wang et al. teach receive, from a base station, a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) (Figs. 2 and 11, [0216], the network device 110 transmits to the terminal device a second radio resource control message, the second radio resource control message comprising information concerning a resource configured for transmission of the second plurality of HARQ feedbacks. In such example embodiments, the network device 110 receives the HARQ-ACK codebook on a resource that is determined based on the information),
Wang et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 2 and 7A-B, [0122, 0124, 0127], an example 710 in which the Type-3 HARQ-ACK codebook comprises at least part of HARQ feedbacks for the SPS PDSCHs having the indicated priority in accordance with some embodiments of the present disclosure. In the example 710, the request from the network device 110 indicates the high priority of HARQ feedbacks for the SPS PDSCHs in CC #1. In this case, the Type-3 HARQ-ACK codebook comprises a first group of HARQ feedbacks 710A for the SPS PDSCHs for the SPS configuration #2 having the high priority, and a second group of HARQ feedbacks 710B for the SPS PDSCHs for the SPS configuration #3 having the high priority. In the first group of HARQ feedbacks 710A, HARQ feedbacks 711 to 714 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #2. In the second group of HARQ feedbacks 710B, HARQ feedbacks 715 to 718 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #3. The HARQ-ACK codebook comprises the total number of non-overlapped DL HARQ process ID for activated, configured or indicated SPS configurations associated with the indicated priority in serving CC(s). Thus, a size of the HARQ-ACK codebook may be reduced),
Wang et al. teach and transmit, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB (Figs. 2, and 7A-B, [0142, ], the Type-3 HARQ-ACK codebook may comprise the total number of non-overlapped DL HARQ process ID for the one or more activated, configured or indicated SPS configurations in the serving CC(s). The terminal device 120 may transmit the HARQ-ACK codebook on the determined resource).
Wang et al. is teaching of a UE receiving, from a base station, a radio RRC) configuration for a HARQ codebook with process ID and component carrier. Alfarhan et al., however, fail to expressly disclose that the RRC configuration indicates the HARQ process ID and component carrier associated with HARQ codebook. (Emphasis added).
Regarding claim 1, Lei et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 1-3, [0041, 0043, 0047, 0058-0059], requesting feedback of a HARQ-ACK codebook containing all DL HARQ processes, e.g., one-shot feedback, for all Component Carriers (CCs) configured for a UE. Assuming 16 component carriers in one PUCCH group are configured for the UE and the number of DL HARQ processes is 16 and16 component carriers are CC1, CC2, CC16, and the 16 DL HARQ processes are 0, 1, . . . , 15. As illustrated in fig. 3, the x axis represents the DL HARQ processes, and the y axis represents the serving cell indexes configured for the carriers. There are 16 DL HARQ processes, and their IDs are 0, 1, . . . , 15, respectively; there are 16 component carriers, and the serving cell indexes configured for the component carriers are 1, 2, 3, . . . , 16, respectively. Alternatively, the serving cell indexes configured for the component carriers can be 0, 1, 2, 3, . . . , 15, respectively. Suppose the HARQ-ACK information bits in the HARQ-ACK codebook are denoted with b.sub.x,y, wherein x is the HARQ process ID, and y is the serving cell index of the carrier. Upon reception of the triggering DCI, the UE shall generate the HARQ-ACK codebook. The presence of the bitmap in the triggering DCI is configured by RRC signaling).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. by incorporating the features as taught by Lei et al. in order to provide a more effective and efficient system that is capable of indicating, with the RRC configuration, HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB. The motivation is to support an improved method for reducing the size of a HARQ-ACK codebook. (see [0001]).
Regarding claim 11, Wang et al. teach an apparatus of a base station for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory includes instructions executable by the one or more processors to cause the base station to (Figs. 2 and 12, [0217-0218, ], device 1200 can be considered as a further example embodiment of the network device 110, the terminal device 120, or the terminal device 130 as shown in fig. 2. Accordingly, the device 1200 can be implemented at or as at least a part of the network device 110, the terminal device 120, or the terminal device 130. The device 1200 includes a processor 1210, a memory 1220 coupled to the processor 1210, a suitable transmitter (TX) and receiver (RX) 1240 coupled to the processor 1210. The memory 1220 stores at least a part of a program 1230. The program 1230 is assumed to include program instructions that, when executed by the associated processor 1210, enable the device 1200 to operate in accordance with the embodiments of the present disclosure),
Wang et al. teach transmit, to a user equipment (UE), a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) (Figs. 2 and 11, [0216], the network device 110 transmits to the terminal device a second radio resource control message, the second radio resource control message comprising information concerning a resource configured for transmission of the second plurality of HARQ feedbacks. In such example embodiments, the network device 110 receives the HARQ-ACK codebook on a resource that is determined based on the information),
Wang et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 2 and 7A-B, [0122, 0124, 0127], an example 710 in which the Type-3 HARQ-ACK codebook comprises at least part of HARQ feedbacks for the SPS PDSCHs having the indicated priority in accordance with some embodiments of the present disclosure. In the example 710, the request from the network device 110 indicates the high priority of HARQ feedbacks for the SPS PDSCHs in CC #1. In this case, the Type-3 HARQ-ACK codebook comprises a first group of HARQ feedbacks 710A for the SPS PDSCHs for the SPS configuration #2 having the high priority, and a second group of HARQ feedbacks 710B for the SPS PDSCHs for the SPS configuration #3 having the high priority. In the first group of HARQ feedbacks 710A, HARQ feedbacks 711 to 714 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #2. In the second group of HARQ feedbacks 710B, HARQ feedbacks 715 to 718 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #3. The HARQ-ACK codebook comprises the total number of non-overlapped DL HARQ process ID for activated, configured or indicated SPS configurations associated with the indicated priority in serving CC(s). Thus, a size of the HARQ-ACK codebook may be reduced),
Wang et al. teach and receive, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB (Figs. 2, and 7A-B, [0142, ], the Type-3 HARQ-ACK codebook may comprise the total number of non-overlapped DL HARQ process ID for the one or more activated, configured or indicated SPS configurations in the serving CC(s). The terminal device 120 may transmit the HARQ-ACK codebook on the determined resource).
Wang et al. is teaching of a UE receiving, from a base station, a radio RRC) configuration for a HARQ codebook with process ID and component carrier. Alfarhan et al., however, fail to expressly disclose that the RRC configuration indicates the HARQ process ID and component carrier associated with HARQ codebook. (Emphasis added).
Regarding claim 11, Lei et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 1-3, [0041, 0043, 0047, 0058-0059], requesting feedback of a HARQ-ACK codebook containing all DL HARQ processes, e.g., one-shot feedback, for all Component Carriers (CCs) configured for a UE. Assuming 16 component carriers in one PUCCH group are configured for the UE and the number of DL HARQ processes is 16 and16 component carriers are CC1, CC2, CC16, and the 16 DL HARQ processes are 0, 1, . . . , 15. As illustrated in fig. 3, the x axis represents the DL HARQ processes, and the y axis represents the serving cell indexes configured for the carriers. There are 16 DL HARQ processes, and their IDs are 0, 1, . . . , 15, respectively; there are 16 component carriers, and the serving cell indexes configured for the component carriers are 1, 2, 3, . . . , 16, respectively. Alternatively, the serving cell indexes configured for the component carriers can be 0, 1, 2, 3, . . . , 15, respectively. Suppose the HARQ-ACK information bits in the HARQ-ACK codebook are denoted with b.sub.x,y, wherein x is the HARQ process ID, and y is the serving cell index of the carrier. Upon reception of the triggering DCI, the UE shall generate the HARQ-ACK codebook. The presence of the bitmap in the triggering DCI is configured by RRC signaling).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. by incorporating the features as taught by Lei et al. in order to provide a more effective and efficient system that is capable of indicating, with the RRC configuration, HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB. The motivation is to support an improved method for reducing the size of a HARQ-ACK codebook. (see [0001]).
Regarding claim 16, Wang et al. teach a method of wireless communication performed by a user equipment (UE), comprising (Figs. 2 and 12, [0217-0218, ], device 1200 can be considered as a further example embodiment of the network device 110, the terminal device 120, or the terminal device 130 as shown in fig. 2. Accordingly, the device 1200 can be implemented at or as at least a part of the network device 110, the terminal device 120, or the terminal device 130. The device 1200 includes a processor 1210, a memory 1220 coupled to the processor 1210, a suitable transmitter (TX) and receiver (RX) 1240 coupled to the processor 1210. The memory 1220 stores at least a part of a program 1230. The program 1230 is assumed to include program instructions that, when executed by the associated processor 1210, enable the device 1200 to operate in accordance with the embodiments of the present disclosure),
Wang et al. teach receiving, from a base station, a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) (Figs. 2 and 11, [0216], the network device 110 transmits to the terminal device a second radio resource control message, the second radio resource control message comprising information concerning a resource configured for transmission of the second plurality of HARQ feedbacks. In such example embodiments, the network device 110 receives the HARQ-ACK codebook on a resource that is determined based on the information),
Wang et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 2 and 7A-B, [0122, 0124, 0127], an example 710 in which the Type-3 HARQ-ACK codebook comprises at least part of HARQ feedbacks for the SPS PDSCHs having the indicated priority in accordance with some embodiments of the present disclosure. In the example 710, the request from the network device 110 indicates the high priority of HARQ feedbacks for the SPS PDSCHs in CC #1. In this case, the Type-3 HARQ-ACK codebook comprises a first group of HARQ feedbacks 710A for the SPS PDSCHs for the SPS configuration #2 having the high priority, and a second group of HARQ feedbacks 710B for the SPS PDSCHs for the SPS configuration #3 having the high priority. In the first group of HARQ feedbacks 710A, HARQ feedbacks 711 to 714 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #2. In the second group of HARQ feedbacks 710B, HARQ feedbacks 715 to 718 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #3. The HARQ-ACK codebook comprises the total number of non-overlapped DL HARQ process ID for activated, configured or indicated SPS configurations associated with the indicated priority in serving CC(s). Thus, a size of the HARQ-ACK codebook may be reduced),
Wang et al. teach and transmitting, to the base station, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB (Figs. 2, and 7A-B, [0142, ], the Type-3 HARQ-ACK codebook may comprise the total number of non-overlapped DL HARQ process ID for the one or more activated, configured or indicated SPS configurations in the serving CC(s). The terminal device 120 may transmit the HARQ-ACK codebook on the determined resource).
Wang et al. is teaching of a UE receiving, from a base station, a radio RRC) configuration for a HARQ codebook with process ID and component carrier. Alfarhan et al., however, fail to expressly disclose that the RRC configuration indicates the HARQ process ID and component carrier associated with HARQ codebook. (Emphasis added).
Regarding claim 16, Lei et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 1-3, [0041, 0043, 0047, 0058-0059], requesting feedback of a HARQ-ACK codebook containing all DL HARQ processes, e.g., one-shot feedback, for all Component Carriers (CCs) configured for a UE. Assuming 16 component carriers in one PUCCH group are configured for the UE and the number of DL HARQ processes is 16 and16 component carriers are CC1, CC2, CC16, and the 16 DL HARQ processes are 0, 1, . . . , 15. As illustrated in fig. 3, the x axis represents the DL HARQ processes, and the y axis represents the serving cell indexes configured for the carriers. There are 16 DL HARQ processes, and their IDs are 0, 1, . . . , 15, respectively; there are 16 component carriers, and the serving cell indexes configured for the component carriers are 1, 2, 3, . . . , 16, respectively. Alternatively, the serving cell indexes configured for the component carriers can be 0, 1, 2, 3, . . . , 15, respectively. Suppose the HARQ-ACK information bits in the HARQ-ACK codebook are denoted with b.sub.x,y, wherein x is the HARQ process ID, and y is the serving cell index of the carrier. Upon reception of the triggering DCI, the UE shall generate the HARQ-ACK codebook. The presence of the bitmap in the triggering DCI is configured by RRC signaling).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. by incorporating the features as taught by Lei et al. in order to provide a more effective and efficient system that is capable of indicating, with the RRC configuration, HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB. The motivation is to support an improved method for reducing the size of a HARQ-ACK codebook. (see [0001]).
Regarding claim 26, Wang et al. teach method of wireless communication performed by a base station, comprising (Figs. 2 and 12, [0217-0218, ], device 1200 can be considered as a further example embodiment of the network device 110, the terminal device 120, or the terminal device 130 as shown in fig. 2. Accordingly, the device 1200 can be implemented at or as at least a part of the network device 110, the terminal device 120, or the terminal device 130. The device 1200 includes a processor 1210, a memory 1220 coupled to the processor 1210, a suitable transmitter (TX) and receiver (RX) 1240 coupled to the processor 1210. The memory 1220 stores at least a part of a program 1230. The program 1230 is assumed to include program instructions that, when executed by the associated processor 1210, enable the device 1200 to operate in accordance with the embodiments of the present disclosure),
Wang et al. teach transmitting, to a user equipment (UE), a radio resource control (RRC) configuration for a hybrid automatic repeat request (HARQ) codebook (CB) (Figs. 2 and 11, [0216], the network device 110 transmits to the terminal device a second radio resource control message, the second radio resource control message comprising information concerning a resource configured for transmission of the second plurality of HARQ feedbacks. In such example embodiments, the network device 110 receives the HARQ-ACK codebook on a resource that is determined based on the information),
Wang et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 2 and 7A-B, [0122, 0124, 0127], an example 710 in which the Type-3 HARQ-ACK codebook comprises at least part of HARQ feedbacks for the SPS PDSCHs having the indicated priority in accordance with some embodiments of the present disclosure. In the example 710, the request from the network device 110 indicates the high priority of HARQ feedbacks for the SPS PDSCHs in CC #1. In this case, the Type-3 HARQ-ACK codebook comprises a first group of HARQ feedbacks 710A for the SPS PDSCHs for the SPS configuration #2 having the high priority, and a second group of HARQ feedbacks 710B for the SPS PDSCHs for the SPS configuration #3 having the high priority. In the first group of HARQ feedbacks 710A, HARQ feedbacks 711 to 714 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #2. In the second group of HARQ feedbacks 710B, HARQ feedbacks 715 to 718 represent HARQ feedbacks for SPS PDSCHs with the HARQ process ID set {0,1,2,3} for the SPS configuration #3. The HARQ-ACK codebook comprises the total number of non-overlapped DL HARQ process ID for activated, configured or indicated SPS configurations associated with the indicated priority in serving CC(s). Thus, a size of the HARQ-ACK codebook may be reduced),
Wang et al. teach and receiving, from the UE, the HARQ CB based at least in part on the RRC configuration that indicates the HARQ process IDs associated with the HARQ CB (Figs. 2, and 7A-B, [0142, ], the Type-3 HARQ-ACK codebook may comprise the total number of non-overlapped DL HARQ process ID for the one or more activated, configured or indicated SPS configurations in the serving CC(s). The terminal device 120 may transmit the HARQ-ACK codebook on the determined resource).
Wang et al. is teaching of a UE receiving, from a base station, a radio RRC) configuration for a HARQ codebook with process ID and component carrier. Alfarhan et al., however, fail to expressly disclose that the RRC configuration indicates the HARQ process ID and component carrier associated with HARQ codebook. (Emphasis added).
Regarding claim 26, Lei et al. teach wherein the RRC configuration indicates HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB (Figs. 1-3, [0041, 0043, 0047, 0058-0059], requesting feedback of a HARQ-ACK codebook containing all DL HARQ processes, e.g., one-shot feedback, for all Component Carriers (CCs) configured for a UE. Assuming 16 component carriers in one PUCCH group are configured for the UE and the number of DL HARQ processes is 16 and16 component carriers are CC1, CC2, CC16, and the 16 DL HARQ processes are 0, 1, . . . , 15. As illustrated in fig. 3, the x axis represents the DL HARQ processes, and the y axis represents the serving cell indexes configured for the carriers. There are 16 DL HARQ processes, and their IDs are 0, 1, . . . , 15, respectively; there are 16 component carriers, and the serving cell indexes configured for the component carriers are 1, 2, 3, . . . , 16, respectively. Alternatively, the serving cell indexes configured for the component carriers can be 0, 1, 2, 3, . . . , 15, respectively. Suppose the HARQ-ACK information bits in the HARQ-ACK codebook are denoted with b.sub.x,y, wherein x is the HARQ process ID, and y is the serving cell index of the carrier. Upon reception of the triggering DCI, the UE shall generate the HARQ-ACK codebook. The presence of the bitmap in the triggering DCI is configured by RRC signaling).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. by incorporating the features as taught by Lei et al. in order to provide a more effective and efficient system that is capable of indicating, with the RRC configuration, HARQ process identifiers (IDs) associated with the HARQ CB and indicates a set of component carriers associated with the HARQ CB. The motivation is to support an improved method for reducing the size of a HARQ-ACK codebook. (see [0001]).
Claim(s) 2-3, 6, 10, 12, 15, 17-18, 21, 25, 27 and 30 is/are rejected under 35 U.S.C. 103 as being unpatentable over Wang et al. (US 2023/0370209 A1) in view of Lei et al. (US 2022/0385411 A1) as applied to claims 1, 11, 16 and 26 above, and further in view of Alfarhan et al. (US 2023/0074723 A1).
Wang et al. and Lei et al. disclose the claimed limitations as described in paragraph 6 above. Wang et al. and Lei et al. do not expressly disclose the following features: regarding claim 2, wherein the memory includes instructions executable by the one or more processors to further cause the UE to: receive, from the base station, downlink control information (DCI) that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI; regarding claim 3, wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB; regarding claim 6, wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ; regarding claim 10, wherein the HARQ CB is a Type 3 HARQ CB; regarding claim 12, wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB; regarding claim 15, wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ; regarding claim 17, further comprising: receiving, from the base station, downlink control information (DCI) that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI; regarding claim 18, wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB; regarding claim 21, wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ; regarding claim 25, wherein the HARQ CB is a Type 3 HARQ CB; regarding claim 27, wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB; regarding claim 30, wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ.
Regarding claim 2, Alfarhan et al. teach wherein the memory includes instructions executable by the one or more processors to further cause the UE to: receive, from the base station, downlink control information (DCI) that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI (Fig. 2, [0071, 0149] in addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. The WTRU may receive a request 235 for one-shot HARQ feedback with an indication of a priority level (e.g. priority 1) from the BS. The request 235 for the one-shot HARQ feedback may be included, for example, in scheduling DCI or non-scheduling DCI with the indication of the priority level. Specifically, a flag indicating the one-shot HARQ feedback and another flag indicating the priority level may be transmitted to the WTRU in the scheduling DCI or the non-scheduling DCI).
Regarding claim 3, Alfarhan et al. teach wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB (Fig. 2, [0078, 0080, 0084], there may be an explicit indication for the HARQ feedback. A HARQ process may be included in or associated with a priority subset if it is indicated by L1, MAC, or RRC signaling. The WTRU may receive a bitmap of HARQ process IDs where 1 or 0 indicate whether the HARQ process ID is included in part of the priority subset. The WTRU may then include HARQ feedback only for the indicated HARQ process to be part of the priority subset, such as upon triggering one-shot HARQ feedback. There may be HARQ processes associated with certain serving cell(s). In one example, the WTRU may receive a one-shot HARQ feedback request for a group for HARQ processes associated with a subset of serving cell(s). The WTRU may receive a cross carrier request for HARQ feedback. For example, the WTRU may receive a one-shot HARQ feedback request with a carrier index or a control format indicator (CFI) field indicated for a different carrier than the one on which the request was received. Upon reception of such a request, the WTRU may include HARQ PIDs associated with the requested cells (e.g., part of the priority subset));
Regarding claim 6, Alfarhan et al. teach wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ (Fig. 2, [0071, 0077] WTRU may fail to transmit the HARQ feedback 230 for the TB3/PID3 due to listen before talk (LBT) failure or dropped feedback due to collision with higher priority transmission. Alternatively or additionally, the BS may fail to receive the HARQ feedback 230 for any reason. The WTRU may receive a request 235 for one-shot HARQ feedback with an indication of a priority level (e.g. priority 1) from the BS. There may also be a benefit to bundle HARQ feedback for lower priority transmissions, given their relaxed latency timeline, while keeping unbundled (e.g., normal) HARQ feedback for prioritized transmissions. This may reduce the number of HARQ feedback collisions with other higher priority Uplink Control Information (UCI) or Physical Uplink Shared Channel (PUSCH) transmissions. In addition, this may reduce the number of dropped HARQ feedback, while leaving room for the network to request the WTRU for HARQ feedback for less latency stringent transmissions. This may also be a useful tool for the network to request feedback for dropped low priority HARQ-ACK transmissions (e.g., due to the conflict with higher priority transmissions) without the need to retransmit the associated TBs again, as the BS (e.g., gNB) is aware that some HARQ-ACK feedback is missing, due to intra-WTRU or inter-WTRU prioritization, for example).
Regarding claim 10, Alfarhan et al. teach wherein the HARQ CB is a Type 3 HARQ CB (Fig. 2, [0068-0069], there may be mechanisms that better enable transmission of HARQ-ACK when operating in NR unlicensed spectrum (NR-U). A first mechanism, referred to as “enhanced Type 2 codebook”, may enable the scheduler to request transmission of HARQ-ACK information for certain physical downlink shared channel (PDSCH) transmissions identified by a PDSCH group. A second mechanism, referred to as “Type 3 codebook” or “one-shot feedback”, may enable the scheduler to request HARQ-ACK information for all HARQ processes and serving cells. When the WTRU reports HARQ-ACK information using a Type 3 codebook (e.g., one-shot feedback), the WTUR transmits HARQ-ACK information for all HARQ processes and cells. This may result in excessive interference and/or power scaling, in which case the Type 3 codebook reporting may be effectively unusable).
Regarding claim 12, Alfarhan et al. teach wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB (Fig. 2, [0078, 0080, 0084], there may be an explicit indication for the HARQ feedback. A HARQ process may be included in or associated with a priority subset if it is indicated by L1, MAC, or RRC signaling. The WTRU may receive a bitmap of HARQ process IDs where 1 or 0 indicate whether the HARQ process ID is included in part of the priority subset. The WTRU may then include HARQ feedback only for the indicated HARQ process to be part of the priority subset, such as upon triggering one-shot HARQ feedback. There may be HARQ processes associated with certain serving cell(s). In one example, the WTRU may receive a one-shot HARQ feedback request for a group for HARQ processes associated with a subset of serving cell(s). The WTRU may receive a cross carrier request for HARQ feedback. For example, the WTRU may receive a one-shot HARQ feedback request with a carrier index or a control format indicator (CFI) field indicated for a different carrier than the one on which the request was received. Upon reception of such a request, the WTRU may include HARQ PIDs associated with the requested cells (e.g., part of the priority subset));
Regarding claim 15, Alfarhan et al. teach wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ (Fig. 2, [0071, 0077], WTRU may fail to transmit the HARQ feedback 230 for the TB3/PID3 due to listen before talk (LBT) failure or dropped feedback due to collision with higher priority transmission. Alternatively or additionally, the BS may fail to receive the HARQ feedback 230 for any reason. The WTRU may receive a request 235 for one-shot HARQ feedback with an indication of a priority level (e.g. priority 1) from the BS. There may also be a benefit to bundle HARQ feedback for lower priority transmissions, given their relaxed latency timeline, while keeping unbundled (e.g., normal) HARQ feedback for prioritized transmissions. This may reduce the number of HARQ feedback collisions with other higher priority Uplink Control Information (UCI) or Physical Uplink Shared Channel (PUSCH) transmissions. In addition, this may reduce the number of dropped HARQ feedback, while leaving room for the network to request the WTRU for HARQ feedback for less latency stringent transmissions. This may also be a useful tool for the network to request feedback for dropped low priority HARQ-ACK transmissions (e.g., due to the conflict with higher priority transmissions) without the need to retransmit the associated TBs again, as the BS (e.g., gNB) is aware that some HARQ-ACK feedback is missing, due to intra-WTRU or inter-WTRU prioritization, for example).
Regarding claim 17, Alfarhan et al. teach further comprising: receiving, from the base station, downlink control information (DCI) that indicates a request for the HARQ CB, wherein the HARQ CB is transmitted based at least in part on the DCI (Fig. 2, [0071, 0149], in addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. The WTRU may receive a request 235 for one-shot HARQ feedback with an indication of a priority level (e.g. priority 1) from the BS. The request 235 for the one-shot HARQ feedback may be included, for example, in scheduling DCI or non-scheduling DCI with the indication of the priority level. Specifically, a flag indicating the one-shot HARQ feedback and another flag indicating the priority level may be transmitted to the WTRU in the scheduling DCI or the non-scheduling DCI).
Regarding claim 18, Alfarhan et al. teach wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB (Fig. 2, [0078, 0080, 0084], there may be an explicit indication for the HARQ feedback. A HARQ process may be included in or associated with a priority subset if it is indicated by L1, MAC, or RRC signaling. The WTRU may receive a bitmap of HARQ process IDs where 1 or 0 indicate whether the HARQ process ID is included in part of the priority subset. The WTRU may then include HARQ feedback only for the indicated HARQ process to be part of the priority subset, such as upon triggering one-shot HARQ feedback. There may be HARQ processes associated with certain serving cell(s). In one example, the WTRU may receive a one-shot HARQ feedback request for a group for HARQ processes associated with a subset of serving cell(s). The WTRU may receive a cross carrier request for HARQ feedback. For example, the WTRU may receive a one-shot HARQ feedback request with a carrier index or a control format indicator (CFI) field indicated for a different carrier than the one on which the request was received. Upon reception of such a request, the WTRU may include HARQ PIDs associated with the requested cells (e.g., part of the priority subset)).
Regarding claim 21, Alfarhan et al. teach wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ (Fig. 2, [0071, 0077], WTRU may fail to transmit the HARQ feedback 230 for the TB3/PID3 due to listen before talk (LBT) failure or dropped feedback due to collision with higher priority transmission. Alternatively or additionally, the BS may fail to receive the HARQ feedback 230 for any reason. The WTRU may receive a request 235 for one-shot HARQ feedback with an indication of a priority level (e.g. priority 1) from the BS. There may also be a benefit to bundle HARQ feedback for lower priority transmissions, given their relaxed latency timeline, while keeping unbundled (e.g., normal) HARQ feedback for prioritized transmissions. This may reduce the number of HARQ feedback collisions with other higher priority Uplink Control Information (UCI) or Physical Uplink Shared Channel (PUSCH) transmissions. In addition, this may reduce the number of dropped HARQ feedback, while leaving room for the network to request the WTRU for HARQ feedback for less latency stringent transmissions. This may also be a useful tool for the network to request feedback for dropped low priority HARQ-ACK transmissions (e.g., due to the conflict with higher priority transmissions) without the need to retransmit the associated TBs again, as the BS (e.g., gNB) is aware that some HARQ-ACK feedback is missing, due to intra-WTRU or inter-WTRU prioritization, for example).
Regarding claim 25, Alfarhan et al. teach wherein the HARQ CB is a Type 3 HARQ CB (Fig. 2, [0068-0069], there may be mechanisms that better enable transmission of HARQ-ACK when operating in NR unlicensed spectrum (NR-U). A first mechanism, referred to as “enhanced Type 2 codebook”, may enable the scheduler to request transmission of HARQ-ACK information for certain physical downlink shared channel (PDSCH) transmissions identified by a PDSCH group. A second mechanism, referred to as “Type 3 codebook” or “one-shot feedback”, may enable the scheduler to request HARQ-ACK information for all HARQ processes and serving cells. When the WTRU reports HARQ-ACK information using a Type 3 codebook (e.g., one-shot feedback), the WTUR transmits HARQ-ACK information for all HARQ processes and cells. This may result in excessive interference and/or power scaling, in which case the Type 3 codebook reporting may be effectively unusable).
Regarding claim 27, Alfarhan et al. teach wherein the RRC configuration indicates: a list of component carriers, corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; and a bitmap indicating a list of the HARQ process IDs to be included in the HARQ CB (Fig. 2, [0078, 0080, 0084], there may be an explicit indication for the HARQ feedback. A HARQ process may be included in or associated with a priority subset if it is indicated by L1, MAC, or RRC signaling. The WTRU may receive a bitmap of HARQ process IDs where 1 or 0 indicate whether the HARQ process ID is included in part of the priority subset. The WTRU may then include HARQ feedback only for the indicated HARQ process to be part of the priority subset, such as upon triggering one-shot HARQ feedback. There may be HARQ processes associated with certain serving cell(s). In one example, the WTRU may receive a one-shot HARQ feedback request for a group for HARQ processes associated with a subset of serving cell(s). The WTRU may receive a cross carrier request for HARQ feedback. For example, the WTRU may receive a one-shot HARQ feedback request with a carrier index or a control format indicator (CFI) field indicated for a different carrier than the one on which the request was received. Upon reception of such a request, the WTRU may include HARQ PIDs associated with the requested cells (e.g., part of the priority subset)).
Regarding claim 30, Alfarhan et al. teach wherein: the HARQ CB is based at least in part on a semi-persistent scheduling HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing; or the HARQ CB is based at least in part on a cancellation indication of an uplink channel containing HARQ (Fig. 2, [0071, 0077], WTRU may fail to transmit the HARQ feedback 230 for the TB3/PID3 due to listen before talk (LBT) failure or dropped feedback due to collision with higher priority transmission. Alternatively or additionally, the BS may fail to receive the HARQ feedback 230 for any reason. The WTRU may receive a request 235 for one-shot HARQ feedback with an indication of a priority level (e.g. priority 1) from the BS. There may also be a benefit to bundle HARQ feedback for lower priority transmissions, given their relaxed latency timeline, while keeping unbundled (e.g., normal) HARQ feedback for prioritized transmissions. This may reduce the number of HARQ feedback collisions with other higher priority Uplink Control Information (UCI) or Physical Uplink Shared Channel (PUSCH) transmissions. In addition, this may reduce the number of dropped HARQ feedback, while leaving room for the network to request the WTRU for HARQ feedback for less latency stringent transmissions. This may also be a useful tool for the network to request feedback for dropped low priority HARQ-ACK transmissions (e.g., due to the conflict with higher priority transmissions) without the need to retransmit the associated TBs again, as the BS (e.g., gNB) is aware that some HARQ-ACK feedback is missing, due to intra-WTRU or inter-WTRU prioritization, for example).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. with Lei et al. by incorporating the features as taught by Alfarhan et al. in order to provide a more effective and efficient system that is capable of receiving, from the base station, DCI that indicates a request for the HARQ CB, indicating, with RRC configuration, a list of component carriers having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB based at least in part on a SPS. HARQ collision with a downlink; the HARQ CB is based at least in part on a low priority HARQ being dropped due to an intra-UE multiplexing. The motivation is to support an improved method for one-shot hybrid automatic repeat request (HARQ) feedback by a priority level (see [0003]).
Claim(s) 4-5, 13-14, 19-20 and 28-29 is/are rejected under 35 U.S.C. 103 as being unpatentable over Wang et al. (US 2023/0370209 A1) in view of Lei et al. (US 2022/0385411 A1) as applied to claims 1, 11, 16 and 26 above, and further in view of Kim et al. (US 2022/0174707 A1).
Wang et al. and Lei et al. disclose the claimed limitations as described in paragraph 6 above. Wang et al. and Lei et al. do not expressly disclose the following features: regarding claim 4, wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB; claim 5, wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers corresponding to the set of component carriers, into a total quantity of configured HARQ CBs; regarding claim 13, wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB; and a size associated with consecutive HARQ process IDs in the HARQ CB; claim 14, wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers corresponding to the set of component carriers, into a total quantity of configured HARQ CBs; regarding claim 19, wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB; regarding claim 20, wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers corresponding to the set of component carriers, into a total quantity of configured HARQ CBs; regarding claim 28, wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB; regarding claim 29, wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers, corresponding to the set of component carriers, into a total quantity of configured HARQ CBs.
Regarding claim 4, Kim et al. teach wherein the RRC configuration indicates: a list of component carriers having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB (Fig. 13, [0065, 0083], a User Equipment (UE)) may receive information on the number M of code block groups per transport block from a Base Station (BS) via a higher layer signal (e.g., RRC signal). Thereafter, the UE may receive data initial transmission from the BS (on PDSCH)]. Here, data includes a transport block, the transport block includes a plurality of code blocks, and a plurality of the code blocks may be classified into one or more code block groups. C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)).
Regarding claim 5, Kim et al. teach wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers corresponding to the set of component carriers, into a total quantity of configured HARQ CBs (Fig. 13, [0083], C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1 in FIG. 13, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)).
Regarding claim 13, Kim et al. teach wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB; and a size associated with consecutive HARQ process IDs in the HARQ CB (Fig. 13, [0065, 0083], a User Equipment (UE)) may receive information on the number M of code block groups per transport block from a Base Station (BS) via a higher layer signal (e.g., RRC signal). Thereafter, the UE may receive data initial transmission from the BS (on PDSCH)]. Here, data includes a transport block, the transport block includes a plurality of code blocks, and a plurality of the code blocks may be classified into one or more code block groups. C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)).
Regarding claim 14, Kim et al. teach wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers corresponding to the set of component carriers, into a total quantity of configured HARQ CBs (Fig. 13, [0083], C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1 in FIG. 13, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)”).
Regarding claim 19, Kim et al. teach wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB (Fig. 13, [0065, 0083] a User Equipment (UE)) may receive information on the number M of code block groups per transport block from a Base Station (BS) via a higher layer signal (e.g., RRC signal). Thereafter, the UE may receive data initial transmission from the BS (on PDSCH)]. Here, data includes a transport block, the transport block includes a plurality of code blocks, and a plurality of the code blocks may be classified into one or more code block groups. C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)).
Regarding claim 20, Kim et al. teach wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers corresponding to the set of component carriers, into a total quantity of configured HARQ CBs (Fig. 13, [0083], C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1 in FIG. 13, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)).
Regarding claim 28, Kim et al. teach wherein the RRC configuration indicates: a list of component carriers corresponding to the set of component carriers, having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB (Fig. 13, [0065, 0083], a User Equipment (UE)) may receive information on the number M of code block groups per transport block from a Base Station (BS) via a higher layer signal (e.g., RRC signal). Thereafter, the UE may receive data initial transmission from the BS (on PDSCH)]. Here, data includes a transport block, the transport block includes a plurality of code blocks, and a plurality of the code blocks may be classified into one or more code block groups. C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s));
Regarding claim 29, Kim et al. teach wherein the RRC configuration indicates an equal split of a plurality of HARQ processes from a plurality of component carriers, corresponding to the set of component carriers, into a total quantity of configured HARQ CBs (Fig. 13, [0083], C-DAI and T-DAI may increase by 1 for each (single-CC or multi-CC DL) DCI. In this case, an HARQ-ACK codebook size may be determined based on the maximum number N of CCs that can be scheduled by a corresponding DCI. Here, the N value may be predefined or configured by higher layer (e.g., RRC) signaling. Since a T-DAI value is 1 in FIG. 13, an (2*N)-bit HARQ-ACK codebook may be configured. Meanwhile, regarding N-bit HARQ-ACK corresponding to each DAI value, if the number of actually scheduled CCs is K (<N), HARQ-ACK information (e.g., ‘1’ in case of ACK or ‘0’ in case of NACK) corresponding to PDSCH on scheduled CC(s) is carried on first (i.e., MSB) K bits among N bits and NACK information (e.g., ‘0’) may be carried on the rest of (i.e., LSB) (N-K) bit(s). If the N value is equal to the maximum HARQ process ID number configured for the corresponding cell, N-bit HARQ-ACK corresponding to each DAI value may be configured as a bitmap corresponding to HARQ process index. Namely, each bit of the N-bit HARQ-ACK may indicate HARQ-ACK information on the corresponding HARQ process ID. In this case, with respect to N-bit HARQ-ACK, if the number of actually scheduled PDSCHs is K (≤N), corresponding HARQ-ACK information may be carried not on the first K bits but on K bits corresponding to the actually scheduled HARQ process ID and NACK information may be carried on the rest of (N-K) bit(s)”).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. with Lei et al. by incorporating the features as taught by Kim et al. in order to provide a more effective and efficient system that is capable of indicating, with RRC configuration, a list of component carriers having HARQ process IDs included in the HARQ CB; a starting HARQ process ID; and a size associated with consecutive HARQ process IDs in the HARQ CB. The motivation is to support an improved method for transmitting and receiving a wireless signal (see [0002]).
Claim(s) 7 and 22 is/are rejected under 35 U.S.C. 103 as being unpatentable over Wang et al. (US 2023/0370209 A1) in view of Lei et al. (US 2022/0385411 A1) as applied to claims 1, 11, 16 and 26 above, and further in view of Alfarhan et al. (US 20230097142 A1) (Alfarhan’142 hereinafter).
Wang et al. and Lei et al. disclose the claimed limitations as described in paragraph 6 above. Wang et al. and Lei et al. do not expressly disclose the following features: regarding claim 7, wherein the RRC configuration is based at least in part on a channel quality; regarding claim 22, wherein the RRC configuration is based at least in part on a channel quality.
Regarding claim 7, Alfarhan’142 teaches wherein the RRC configuration is based at least in part on a channel quality (Fig. 2, [0179-0180], WTRU 102 has several Configured grants (CGs) on which the WTRU 102 may report CQI, the WTRU 102 may measure CQI prior to selecting a CG. The WTRU 102 may select the CG that maps to the measured CQI (e.g., the CG that has a measured CQI in a CQI range associated with the CG). The CQI range may be configured by RRC signaling. For example, the WTRU 102 may have a number of CGs (e.g., CG1, CG2 and CG3). A URLLC packet may arrive at a buffer (e.g., a buffer of the WTRU 102). Based on the measured CQI, the UE may map the URLLC packet to CG2. As shown in FIG. 2, a measured CQI in a first range (e.g., range 1-6) may map to CG1. The measured CQI in a second range (e.g., range 7-9) may map to CG2. The measured CQI in a third range (e.g., range 10-15) may map to CG3).
Regarding claim 22, Alfarhan’142 teaches wherein the RRC configuration is based at least in part on a channel quality (Fig. 2, [0179-0180] WTRU 102 has several Configured grants (CGs) on which the WTRU 102 may report CQI, the WTRU 102 may measure CQI prior to selecting a CG. The WTRU 102 may select the CG that maps to the measured CQI (e.g., the CG that has a measured CQI in a CQI range associated with the CG). The CQI range may be configured by RRC signaling. For example, the WTRU 102 may have a number of CGs (e.g., CG1, CG2 and CG3). A URLLC packet may arrive at a buffer (e.g., a buffer of the WTRU 102). Based on the measured CQI, the UE may map the URLLC packet to CG2. As shown in FIG. 2, a measured CQI in a first range (e.g., range 1-6) may map to CG1. The measured CQI in a second range (e.g., range 7-9) may map to CG2. The measured CQI in a third range (e.g., range 10-15) may map to CG3)
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. with Lei et al. by incorporating the features as taught by Alfarhan’142 in order to provide a more effective and efficient system that is capable of configuring the RRC based at least in part on a channel quality. The motivation is to support an improved method for channel state information reporting (see [0002]).
Claim(s) 8 and 23 is/are rejected under 35 U.S.C. 103 as being unpatentable over Wang et al. (US 2023/0370209 A1) in view of Lei et al. (US 2022/0385411 A1) as applied to claims 1 and 16 above, and further in view of Alfarhan et al. (US 2022/0400396 A1) (Alfarhan’396 hereinafter).
Wang et al. and Lei et al. disclose the claimed limitations as described in paragraph 6 above. Wang et al. and Lei et al. do not expressly disclose the following features: regarding claim 8, wherein the memory includes instructions executable by the one or more processors to further cause the UE to: transmit, to the base station, a request for a type of RRC configuration based at least in part on a reference signal received power associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request; regarding claim 23, further comprising: transmitting, to the base station, a request for a type of RRC configuration based at least in part on a reference signal received power associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request.
Regarding claim 8, Alfarhan’396 teaches wherein the memory includes instructions executable by the one or more processors to further cause the UE to: transmit, to the base station, a request for a type of RRC configuration based at least in part on a reference signal received power associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request (Fig. 2, [0150, 0158, 0172, 0174] the method may further comprise storing the SR configuration in the WTRU; and changing or adjusting the stored SR configuration via Radio Resource Control (RRC) signaling. The failure reporting MAC-CE may comprise any of: [0159] a cell index of said first cell on which said UL-BLT failure or said beam failure is detected; [0160] a Bandwidth Part, BWP, of a BWP on which said UL-BLT failure or said beam failure is detected; [0161] a sub-band on which said UL-BLT failure or said beam failure is detected; [0162] a Radio Resource Control, RRC, message; [0163] at least one measurement which may comprise any of Reference Signal Received Power, RSRP, Signal-to-Reference-and-Noise Ratio, SINR, Received Signal Strength Indicator, RSSI, channel occupancy, for the first cell, on which said UL-BLT failure or said beam failure is detected. Where the WTRU considers a HARQ entity applicable per TRP, TRP group, or group of TRPs transmitting the same PDCCH. Alternatively, the MAC entity may be configured with different HARQ Process ID (PID) spaces, where each PID space may be applicable to a specific TRP, TRP group, or group of TRPs transmitting the same PDCCH. The WTRU may determine which TRP is applicable for transmission/reception from the HARQ process ID indicated in the PDCCH. The WTRU may be configured with more than one HARQ-ACK codebook for different schedulers/PDCCHs in the cell; the WTRU may select a codebook for feeding back HARQ Ack/Nack as a function of the PDCCH from which the DL assignment was received from).
Regarding claim 23, Alfarhan’396 teaches further comprising: transmitting, to the base station, a request for a type of RRC configuration based at least in part on a reference signal received power associated with a signal received from the base station, wherein the RRC configuration received from the base station is based at least in part on the request (Fig. 2, [0150, 0158, 0172, 0174] the method may further comprise storing the SR configuration in the WTRU; and changing or adjusting the stored SR configuration via Radio Resource Control (RRC) signaling. The failure reporting MAC-CE may comprise any of: [0159] a cell index of said first cell on which said UL-BLT failure or said beam failure is detected; [0160] a Bandwidth Part, BWP, of a BWP on which said UL-BLT failure or said beam failure is detected; [0161] a sub-band on which said UL-BLT failure or said beam failure is detected; [0162] a Radio Resource Control, RRC, message; [0163] at least one measurement which may comprise any of Reference Signal Received Power, RSRP, Signal-to-Reference-and-Noise Ratio, SINR, Received Signal Strength Indicator, RSSI, channel occupancy, for the first cell, on which said UL-BLT failure or said beam failure is detected. Where the WTRU considers a HARQ entity applicable per TRP, TRP group, or group of TRPs transmitting the same PDCCH. Alternatively, the MAC entity may be configured with different HARQ Process ID (PID) spaces, where each PID space may be applicable to a specific TRP, TRP group, or group of TRPs transmitting the same PDCCH. The WTRU may determine which TRP is applicable for transmission/reception from the HARQ process ID indicated in the PDCCH. The WTRU may be configured with more than one HARQ-ACK codebook for different schedulers/PDCCHs in the cell; the WTRU may select a codebook for feeding back HARQ Ack/Nack as a function of the PDCCH from which the DL assignment was received from).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. with Lei et al. by incorporating the features as taught by Alfarhan’396 in order to provide a more effective and efficient system that is capable of transmitting to the base station a request for a type of RRC configuration based on a reference signal received power. The motivation is to support an improved method for reporting channel failure in new radio operation (see [0008]).
Claim(s) 9 and 24 is/are rejected under 35 U.S.C. 103 as being unpatentable over Wang et al. (US 2023/0370209 A1) in view of Lei et al. (US 2022/0385411 A1) as applied to claims 1 and 16 above, and further in view of Bae et al. (US 20220231798 A1).
Wang et al. and Lei et al. disclose the claimed limitations as described in paragraph 6 above. Wang et al. and Lei et al. do not expressly disclose the following features: regarding claim 9, wherein a plurality of active HARQ process IDs are not all included in the HARQ CB; regarding claim 24, wherein a plurality of active HARQ process IDs are not all included in the HARQ CB.
Regarding claim 9, Bae et al. teach wherein a plurality of active HARQ process IDs are not all included in the HARQ CB (Fig. 12, [0222-0225], in a given scheduled cell, the UE is not expected to (simultaneously) receive a first PDSCH and a second PDSCH, which starts later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted on a resource ending before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH if the HARQ-ACKs for the two PDSCHs are associated with HARQ-ACK codebooks of different priorities. For transmission of a HARQ-ACK response dropped due to collision with a DL symbol and/or a HARQ-ACK response of low priority canceled due to collision with UL control information of high priority (and a HARQ process ID related thereto), the UE may be exceptionally 1): allowed to perform operation(s) of PDSCH (re-)transmission/reception for the same HARQ process ID and related HARQ-ACK transmission even before a corresponding HARQ-ACK transmission is performed over a PUCCH or Type-3 codebook into which the dropped and/or canceled HARQ-ACK transmission is delayed to be loaded; and 2) relaxed to determine the out-of-order HARQ restriction predefined for a HARQ process ID based on a HARQ-ACK transmission time indicated/configured before the dropping/cancellation (rather than the actual HARQ-ACK transmission time (e.g., the delayed HARQ-ACK transmission time)). In other words, in some implementations of the present disclosure, for transmission of a HARQ-ACK response dropped due to collision with a DL symbol and/or a HARQ-ACK response of low priority canceled due to collision with UL control information of high priority (and a HARQ process ID related thereto), the following may be exceptionally considered: 1) operations(s) of performing PDSCH (re-)transmission/reception for the same HARQ process ID and related A/N feedback transmission are allowed even before a corresponding A/N feedback is transmitted over a PUCCH or Type-3 codebook into which the dropped and/or canceled A/N feedback is delayed to be loaded; and 2) determination of whether HARQs for the same HARQ process ID are out of order is relaxed such that the determination is made based on a A/N transmission time indicated/configured before the dropping/cancellation (rather than the actual A/N transmission time (e.g., the delayed HARQ-ACK transmission time)).
Regarding claim 24, Bae et al. teach wherein a plurality of active HARQ process IDs are not all included in the HARQ CB (Fig. 12, [0222-0225], in a given scheduled cell, the UE is not expected to (simultaneously) receive a first PDSCH and a second PDSCH, which starts later than the first PDSCH, with its corresponding HARQ-ACK assigned to be transmitted on a resource ending before the start of a different resource for the HARQ-ACK assigned to be transmitted for the first PDSCH if the HARQ-ACKs for the two PDSCHs are associated with HARQ-ACK codebooks of different priorities. For transmission of a HARQ-ACK response dropped due to collision with a DL symbol and/or a HARQ-ACK response of low priority canceled due to collision with UL control information of high priority (and a HARQ process ID related thereto), the UE may be exceptionally 1): allowed to perform operation(s) of PDSCH (re-)transmission/reception for the same HARQ process ID and related HARQ-ACK transmission even before a corresponding HARQ-ACK transmission is performed over a PUCCH or Type-3 codebook into which the dropped and/or canceled HARQ-ACK transmission is delayed to be loaded; and 2) relaxed to determine the out-of-order HARQ restriction predefined for a HARQ process ID based on a HARQ-ACK transmission time indicated/configured before the dropping/cancellation (rather than the actual HARQ-ACK transmission time (e.g., the delayed HARQ-ACK transmission time)). In other words, in some implementations of the present disclosure, for transmission of a HARQ-ACK response dropped due to collision with a DL symbol and/or a HARQ-ACK response of low priority canceled due to collision with UL control information of high priority (and a HARQ process ID related thereto), the following may be exceptionally considered: 1) operations(s) of performing PDSCH (re-)transmission/reception for the same HARQ process ID and related A/N feedback transmission are allowed even before a corresponding A/N feedback is transmitted over a PUCCH or Type-3 codebook into which the dropped and/or canceled A/N feedback is delayed to be loaded; and 2) determination of whether HARQs for the same HARQ process ID are out of order is relaxed such that the determination is made based on a A/N transmission time indicated/configured before the dropping/cancellation (rather than the actual A/N transmission time (e.g., the delayed HARQ-ACK transmission time)).
It would have been obvious to one of the ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Wang et al. with Lei et al. by incorporating the features as taught by Bae et al. in order to provide a more effective and efficient system that is capable of not including a plurality of active HARQ process IDs in the HARQ CB. The motivation is to support an improved method for efficiently using high-density UEs for communication (see [0006]).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SYED M BOKHARI whose telephone number is (571)270-3115. The examiner can normally be reached Monday through Friday.
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, Kwang B Yao can be reached at 5712723182. 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.
/SYED M BOKHARI/Examiner, Art Unit 2473 2/11/2026
/KWANG B YAO/Supervisory Patent Examiner, Art Unit 2473