DETAILED ACTION
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 .
Priority
Receipt is acknowledged of certified copies of papers required by 37 CFR 1.55.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 10/24/2024, 10/03/2025, 11/17/2025 and 02/27/2026 are considered. The submission is in compliance with the provisions of 37 CFR 1.97.
However, the following references cited in IDS 10/24/2024 are not considered as certain sections/paragraphs are not legible.
Moderator (Vivo), "Feature Lead Summary#3 on Enhancements on Multi-TRP Inter-Cell Operation", R1-2202887, 3GPP TSG RAN WG1 #108-e, February 21 - March 3, 2022, 46 pages; and
Intel Corporation, "MIMO Enhancements for Multi-TRP Deployments", R1-2204764, 3GPP TSG RAN WG1 #109-e, May 9-20, 2022, 6 pages.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 16-17, 20-22, 25-27, 30-32 and 35 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Huang et al. (US 2023/0048026; hereinafter Huang).
Regarding claim 16, Huang shows a method performed by a user equipment (UE) (Figure 13 shows a method performed in part by a UE of Figure 2.) in a wireless communication system, the method comprising:
transmitting, to a base station (Figures 2 and 13; gNB.), UE capability information including first information (Figure 13; Par. 0375; transmitting, to the gNB, UE capability information.) indicating whether the UE supports multi-downlink control information (DCI) based physical uplink shared channels (PUSCHs) overlapped in time domain (Figure 13; Par. 0238, 0349, 0375; the UE capability information associated with multiple (e.g., two) UE panels of the UE and/or UE capability information associated with concurrent (e.g., simultaneous) uplink transmissions (e.g., PUSCHs) that are at least partially overlapping in time domain. The concurrent uplink transmissions are scheduled using one or more DCIs.);
receiving, from the base station, higher layer signaling including a configuration associated with multi panel simultaneous uplink transmission of a PUSCH (Figure 13; Par. 0374-0375; the UE may receive, from the network, a configuration 1306 of multiple (e.g., two) SRS resource sets. In some examples, the first SRS resource set may be associated with a first UE panel (e.g., one UE panel) and the second SRS resource set may be associated with a second UE panel (e.g., one UE panel other than the first UE panel).);
receiving, from the base station, first DCI scheduling a first PUSCH on a first control resource set (CORESET) configured based on a first CORESET pool index and second DCI scheduling a second PUSCH on a second CORESET configured based on a second CORESET pool index (Figure 13; Par. 0375, 0447-0448; receiving, from the gNB, the one or more DCIs. The one or more DCIs may comprise a first DCI that schedules a first PUSCH and a second DCI schedules a second PUSCH. In an example, the first uplink transmission is scheduled by DCI in the first CORESET which is associated with the first CORESET pool index. The second uplink transmission may be scheduled by DCI in the second CORESET which is associated with the second CORESET pool index.); and
transmitting the first PUSCH based on the first DCI, and the second PUSCH based on the second DCI, wherein the first PUSCH and the second PUSCH overlap in at least a part of the time domain (Figure 13 ; Par. 0375; based on the first and second DCIs, the UE performs concurrent uplink transmission 1314 of the multiple uplink transmissions (e.g., the multiple uplink transmissions may comprise transmission of PUSCH 1 via a UE panel 1 of the UE and transmission of PUSCH 2 via a UE panel 2 of the UE), wherein the first PUSCH and the second PUSCH may at least partially overlap in time domain.).
Regarding claim 17, Huang shows wherein the UE capability information further includes second information indicating whether the UE supports two sounding reference signal (SRS) resource sets associated with two CORESET pool index values (Figure 13; Par. 0371-0372, 0374-0375, 0447; The UE may report a capability associated with a number of groups of SRS resources that the UE can maintain. The UE reports two groups of SRS resources to network. The first SRS resource set is associated with the transmission of PUSCH 1 via a UE panel 1 and the second SRS resource set is associated with transmission of PUSCH 2 via a UE panel 2. The first uplink transmission is scheduled by DCI in the first CORESET which is associated with the first CORESET pool index. The second uplink transmission may be scheduled by DCI in the second CORESET which is associated with the second CORESET pool index.).
Regarding claim 20, Huang shows wherein the first information indicates whether the UE supports the multi-DCI based PUSCHs overlapped in the time domain partially or fully, and wherein the first information indicates whether the UE supports the multi-DCI based PUSCHs overlapped in a frequency domain fully, partially, or non-overlapping (Par. 0389-0391; none of PRB or resource element of a first uplink channel/signal (e.g., one uplink channel/signal) of the multiple (e.g., two) uplink channels/signals is overlapped with a second uplink channel/signal (e.g., one uplink channel/signal other than the first uplink channel/signal) of the multiple (e.g., two) uplink channels/signals (in frequency domain). In some examples, at least one PRB or resource element of a first uplink channel/signal (e.g., one uplink channel/signal) of the multiple (e.g., two) uplink channels/signals is overlapped with a second uplink channel/signal (e.g., one uplink channel/signal other than the first uplink channel/signal) of the multiple (e.g., two) uplink channels/signals (in frequency domain). In some examples, all PRBs or resource elements of a first uplink channel/signal (e.g., one uplink channel/signal) of the multiple (e.g., two) uplink channels/signals is overlapped with a second uplink channel/signal (e.g., one uplink channel/signal other than the first uplink channel/signal) of the multiple (e.g., two) uplink channels/signals (in frequency domain).).
Regarding claim 21, Huang shows a method performed by a base station (Figure 13 shows a method performed in part by a gNB of Figure 2.) in a wireless communication system, the method comprising:
receiving, from a user equipment (UE) (Figures 2 and 13; UE.), UE capability information including first information (Figure 13; Par. 0375; receiving, from the UE, capability information.) indicating whether the UE supports multi-downlink control information (DCI) based physical uplink shared channels (PUSCHs) overlapped in time domain (Figure 13; Par. 0238, 0349, 0375; the UE capability information associated with multiple (e.g., two) UE panels of the UE and/or UE capability information associated with concurrent (e.g., simultaneous) uplink transmissions (e.g., PUSCHs) that are at least partially overlapping in time domain. The concurrent uplink transmissions are scheduled using one or more DCIs.);
transmitting, to the UE, higher layer signaling including a configuration associated with multi panel simultaneous uplink transmission of a PUSCH (Figure 13; Par. 0374-0375; the gNB transmits a configuration 1306 of multiple (e.g., two) SRS resource sets. In some examples, the first SRS resource set may be associated with a first UE panel (e.g., one UE panel) and the second SRS resource set may be associated with a second UE panel (e.g., one UE panel other than the first UE panel).);
transmitting, to the UE, first DCI scheduling a first PUSCH on a first control resource set (CORESET) configured based on a first CORESET pool index, and second DCI scheduling a second PUSCH on a second CORESET configured based on a second CORESET pool index (Figure 13; Par. 0375, 0447-0448; the gNB transmitting the one or more DCIs. The one or more DCIs may comprise a first DCI that schedules a first PUSCH and a second DCI schedules a second PUSCH. In an example, the first uplink transmission is scheduled by DCI in the first CORESET which is associated with the first CORESET pool index. The second uplink transmission may be scheduled by DCI in the second CORESET which is associated with the second CORESET pool index.); and
receiving, from the UE, the first PUSCH based on the first DCI, and the second PUSCH based on the second DCI, wherein the first PUSCH and the second PUSCH overlap in at least a part of the time domain (Figure 13 ; Par. 0375; based on the first and second DCIs, the UE performs concurrent uplink transmission 1314 of the multiple uplink transmissions (e.g., the multiple uplink transmissions may comprise transmission of PUSCH 1 via a UE panel 1 of the UE and transmission of PUSCH 2 via a UE panel 2 of the UE), wherein the first PUSCH and the second PUSCH may at least partially overlap in time domain.).
Regarding claims 22 and 25, these claims are rejected based on the same reasoning as presented in the rejection of claims 17 and 20, respectively.
Regarding claim 26, Huang shows a user equipment (UE) (Figure 2 shows a UE performing in part the method of Figure 13.) in a wireless communication system, the UE comprising:
a transceiver (Figure 2; UE includes a transceiver.); and
at least one processor coupled with the transceiver (Figure 2; UE includes a processor coupled to the transceiver.)and configured to:
transmit, to a base station (Figures 2 and 13; gNB.), UE capability information including first information (Figure 13; Par. 0375; transmitting, to the gNB, UE capability information.) indicating whether the UE supports multi-downlink control information (DCI) based physical uplink shared channels (PUSCHs) overlapped in time domain (Figure 13; Par. 0238, 0349, 0375; the UE capability information associated with multiple (e.g., two) UE panels of the UE and/or UE capability information associated with concurrent (e.g., simultaneous) uplink transmissions (e.g., PUSCHs) that are at least partially overlapping in time domain. The concurrent uplink transmissions are scheduled using one or more DCIs.),
receive, from the base station, higher layer signaling including a configuration associated with multi panel simultaneous uplink transmission of a PUSCH (Figure 13; Par. 0374-0375; the UE may receive, from the network, a configuration 1306 of multiple (e.g., two) SRS resource sets. In some examples, the first SRS resource set may be associated with a first UE panel (e.g., one UE panel) and the second SRS resource set may be associated with a second UE panel (e.g., one UE panel other than the first UE panel).),
receive, from the base station, first DCI scheduling a first PUSCH on a first control resource set (CORESET) configured based on a first CORESET pool index, and second DCI scheduling a second PUSCH on a second CORESET configured based on a second CORESET pool index (Figure 13; Par. 0375, 0447-0448; receiving, from the gNB, the one or more DCIs. The one or more DCIs may comprise a first DCI that schedules a first PUSCH and a second DCI schedules a second PUSCH. In an example, the first uplink transmission is scheduled by DCI in the first CORESET which is associated with the first CORESET pool index. The second uplink transmission may be scheduled by DCI in the second CORESET which is associated with the second CORESET pool index.), and
transmit the first PUSCH based on the first DCI, and the second PUSCH based on the second DCI, wherein the first PUSCH and the second PUSCH overlap in at least a part of the time domain (Figure 13 ; Par. 0375; based on the first and second DCIs, the UE performs concurrent uplink transmission 1314 of the multiple uplink transmissions (e.g., the multiple uplink transmissions may comprise transmission of PUSCH 1 via a UE panel 1 of the UE and transmission of PUSCH 2 via a UE panel 2 of the UE), wherein the first PUSCH and the second PUSCH may at least partially overlap in time domain.).
Regarding claims 27 and 30, these claims are rejected based on the same reasoning as presented in the rejection of claims 17 and 20, respectively.
Regarding claim 31, Huang shows a base station (Figure 2 shows a gNB performing in part the method of Figure 13.) in a wireless communication system, the base station comprising:
a transceiver (Figure 2; gNB includes a transceiver.); and
at least one processor coupled with the transceiver (Figure 2; gNB includes a processor coupled to the transceiver.) and configured to:
receive, from a user equipment (UE), UE capability information including first information (Figure 13; Par. 0375; receiving, from the UE, capability information.) indicating whether the UE supports multi-downlink control information (DCI) based physical uplink shared channels (PUSCHs) overlapped in time domain (Figure 13; Par. 0238, 0349, 0375; the UE capability information associated with multiple (e.g., two) UE panels of the UE and/or UE capability information associated with concurrent (e.g., simultaneous) uplink transmissions (e.g., PUSCHs) that are at least partially overlapping in time domain. The concurrent uplink transmissions are scheduled using one or more DCIs.),
transmit, to the UE, higher layer signaling including a configuration associated with multi panel simultaneous uplink transmission of a PUSCH (Figure 13; Par. 0374-0375; the gNB transmits a configuration 1306 of multiple (e.g., two) SRS resource sets. In some examples, the first SRS resource set may be associated with a first UE panel (e.g., one UE panel) and the second SRS resource set may be associated with a second UE panel (e.g., one UE panel other than the first UE panel).),
transmit, to the UE, first DCI scheduling a first PUSCH on a first control resource set (CORESET) configured based on a first CORESET pool index, and second DCI scheduling a second PUSCH on a second CORESET configured based on a second CORESET pool index (Figure 13; Par. 0375, 0447-0448; the gNB transmitting the one or more DCIs. The one or more DCIs may comprise a first DCI that schedules a first PUSCH and a second DCI schedules a second PUSCH. In an example, the first uplink transmission is scheduled by DCI in the first CORESET which is associated with the first CORESET pool index. The second uplink transmission may be scheduled by DCI in the second CORESET which is associated with the second CORESET pool index.), and
receive, from the UE, the first PUSCH based on the first DCI, and the second PUSCH based on the second DCI, wherein the first PUSCH and the second PUSCH overlap in at least a part of the time domain (Figure 13 ; Par. 0375; based on the first and second DCIs, the UE performs concurrent uplink transmission 1314 of the multiple uplink transmissions (e.g., the multiple uplink transmissions may comprise transmission of PUSCH 1 via a UE panel 1 of the UE and transmission of PUSCH 2 via a UE panel 2 of the UE), wherein the first PUSCH and the second PUSCH may at least partially overlap in time domain.).
Regarding claims 32 and 35, these claims are rejected based on the same reasoning as presented in the rejection of claims 17 and 20, respectively
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.
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) 18, 23, 28 and 33 are rejected under 35 U.S.C. 103 as being unpatentable over Huang in view of Soriaga et al. (US 2020/0322944; hereinafter Soriaga).
Regarding claim 18, Huang shows all of the elements except wherein the UE capability information further includes third information indicating whether the UE supports out-of-order operation for the multiple DCI based PUSCHs, and wherein the out-of-order operation includes performing, before a transmission of a PUSCH scheduled by DCI received earlier among the first DCI and the second DCI is completed, a transmission of a PUSCH scheduled by DCI received later among the first DCI and the second DCI.
However, the above-mentioned claim limitations are well-established in the art as evidenced by Soriaga. Specifically, Soriaga shows wherein the UE capability information further includes third information indicating whether the UE supports out-of-order operation for the multiple DCI based PUSCHs (Figures 2 and 5; Par. 0115; To accommodate the out-of-order operation, as described with reference to FIG. 2, the UE 115 may indicate a processing capability to the base station 105 to enable the base station 105 to configure the UE 115 to transmit and/or receive communications based on the different priority classes that the UE 115 supports.), and
wherein the out-of-order operation includes performing, before a transmission of a PUSCH scheduled by DCI received earlier among the first DCI and the second DCI is completed, a transmission of a PUSCH scheduled by DCI received later among the first DCI and the second DCI (Figure 2; Par. 0095-0097; UE 115-a may receive and process the first DCI message 215-a first to transmit in the first PUSCH 220-a (e.g., when the first DCI message 215-a includes an uplink grant). Then, UE 115-a may receive and begin processing the second DCI message 215-b to transmit in the second PUSCH 220-b, when the third DCI message 215-c is received and UE 115-a needs to process the third DCI message 215-c to transmit in the third PUSCH 220-c (e.g., based on the shorter processing timeline) prior to transmitting in the second PUSCH 220-b. UE 115-a may then finish processing the second DCI message 215-b and transmit in the second PUSCH 220-b. Subsequently, UE 115-a may also receive and process the fourth DCI message 215-d and transmit in the fourth PUSCH 220-d. In some cases, rather than transmitting in an associated PUSCH 220, UE 115-a may receive an associated downlink channel (e.g., PDSCH or PDCCH) after receiving a DCI message 215 (e.g., when a DCI message 215 includes a downlink grant).).
In view of the above, having the system of Huang, then given the well-established teaching of Soriaga, it would have been obvious before the effective filing date of the claimed invention to modify the system of Huang as taught by Soriaga, in order to provide motivation to support efficient techniques for a capability-based solution for handling an out-of-order operation for processing multiple downlink channels (Par. 0090 of Soriaga).
Regarding claims 23, 28 and 33, these claims are rejected based on the same reasoning as presented in the rejection of claim 18.
Allowable Subject Matter
Claims 19, 24, 29 and 34 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Examiner submits that none of the prior art references cited in this action teaches the claimed subject matter as specifically presented in the above dependent claims. The allowance of this application is based on an examination wherein the claim limitations recited in the dependent claims were not taken alone but in view of the scope of the claim(s) as a whole including any proceeding and/or preceding claim limitation(s) present within the claims and by their respective dependencies on other claims.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 12713445 B2 - METHODS AND SYSTEMS FOR MULTI-CELL TRANSMISSION
US 20260059524 A1 - METHOD AND DEVICE FOR TRANSMITTING OR RECEIVING PUSCH IN WIRELESS COMMUNICATION SYSTEM
US 20250168783 A1 - POWER CONTROL FOR SIMULTANEOUS PHYSICAL UPLINK SHARED CHANNEL (PUSCH) TRANSMISSION IN A CELL
US 20240187200 A1 - DOWNLINK CONTROL CHANNEL MONITORING ADAPTATION
US 20230125953 A1 - MULTI-TRANSMISSION AND RECEPTION POINT (TRP) REDUNDANCY AND SOFT COMBINING WITH REDUCED LATENCY
US 20220256571 A1 - METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING DOWNLINK CONTROL CHANNEL IN A WIRELESS COMMUNICATION SYSTEM
US 20220225247 A1 - METHOD AND APPARATUS FOR POWER HEADROOM REPORT REGARDING MULTI-TRP IN A WIRELESS COMMUNICATION SYSTEM
US 20220150839 A1 - CLOSED LOOP POWER CONTROL FOR PUSCH
Any inquiry concerning this communication or earlier communications from the examiner should be directed to REDENTOR M PASIA whose telephone number is (571)272-9745. The examiner can normally be reached Mondays-Fridays 5am-245pm.
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, Un Cho can be reached at (571)272-7919. 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.
/REDENTOR PASIA/Primary Examiner, Art Unit 2413
Prosecution Insights