Prosecution Insights
Last updated: July 17, 2026
Application No. 18/845,691

METHOD AND APPARATUS FOR TRANSFORM PRECODING STATE SWITCHING FOR A PUSCH

Non-Final OA §102
Filed
Sep 10, 2024
Priority
Mar 11, 2022 — nonprovisional of PCTCN2022080369
Examiner
GHAFOERKHAN, FAIYAZKHAN
Art Unit
Tech Center
Assignee
Lenovo (United States) Inc.
OA Round
1 (Non-Final)
87%
Grant Probability
Favorable
1-2
OA Rounds
10m
Est. Remaining
96%
With Interview

Examiner Intelligence

Grants 87% — above average
87%
Career Allowance Rate
498 granted / 572 resolved
+27.1% vs TC avg
Moderate +8% lift
Without
With
+8.4%
Interview Lift
resolved cases with interview
Typical timeline
2y 8m
Avg Prosecution
16 currently pending
Career history
587
Total Applications
across all art units

Statute-Specific Performance

§101
0.8%
-39.2% vs TC avg
§103
68.1%
+28.1% vs TC avg
§102
19.4%
-20.6% vs TC avg
§112
6.8%
-33.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 572 resolved cases

Office Action

§102
DETAILED ACTION Claims 5 and 7 have been cancelled. Claims 16-22 have been added. Claims 1-4, 6, and 8-22 have been examined. Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Claim Rejections - 35 USC § 102 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. Claim(s) 1-3, 8-9, 15-17, and 19-21 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by US 20210266887 A1 to Zhang et al. (hereinafter “Zhang”). As per claim 1, Zhang discloses a user equipment (UE) for wireless communication (Zhang Fig. 2, [0005,0175]), comprising: at least one memory (Zhang Fig. 2, [0005,0175]); and at least one processor coupled with the at least one memory (Zhang Fig. 2, [0005,0175]) and configured to cause the UE to: receive first indication information indicating a transform precoding state for a physical uplink shared channel (PUSCH) transmission, wherein the transform precoding state indicates whether a transform precoding is enabled or not (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.); and determine whether to apply the transform precoding state to a first PUSCH transmission (Zhang Fig. 1 and [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 2, Zhang discloses the UE of claim 1, wherein the first indication information comprises downlink control information (DCI), and the at least one processor is further configured to cause the UE to receive configuration information indicating whether a field for indicating the transform precoding state exists or not in the DCI (Zhang Fig. 1 and [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 3, Zhang the UE of claim 2, wherein the configuration information is configured per UE (Zhang [0020] It may be considered that the UE-specific configuration is configured with dedicated signaling to the UE. The dedicate signaling for the UE-specific configuration may be transmitted by a network node.) or per DCI format. As per claim 8, Zhang discloses the UE of claim 1, wherein the at least one processor is further configured to cause the UE to at least one of: report whether the UE supports a transform precoding state switch or not; or receive configuration information indicating whether the UE is allowed to perform the transform precoding state switch (Zhang Fig. 1 and [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 9, Zhang discloses a user equipment (UE) for wireless communication (Zhang Fig. 2, [0005,0175]), comprising: at least one memory (Zhang Fig. 2, [0005,0175]); and at least one processor coupled with the at least one memory and configured (Zhang Fig. 2, [0005,0175]) to cause the UE to: receive first indication information indicating a first transform precoding state, wherein the first transform precoding state indicates whether a transform precoding is enabled or not (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.); and transmit a first physical uplink shared channel (PUSCH) transmission based on the first transform precoding state (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 15, Zhang discloses a base station (BS) for wireless communication (Zhang Fig. 3 and [0127-0128]), comprising: at least one memory (Zhang Fig. 3 and [0127-0128]); and at least one processor coupled with the at least one memory and configured to cause the BS (Zhang Fig. 3 and [0127-0128]) to: transmit, to a user equipment (UE), first indication information indicating a transform precoding state for a physical uplink shared channel (PUSCH) transmission, wherein the transform precoding state indicates whether a transform precoding is enabled or not (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.); and determine whether the transform precoding state is applied to a first PUSCH transmission (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 16, Zhang discloses the UE of claim 9, wherein the first indication information comprises downlink control information (DCI), and the at least one processor is configured to cause the UE to receive configuration information indicating whether a field for indicating the transform precoding state exists or not in the DCI (Zhang Fig. 1 and [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 17, Zhang discloses the UE of claim 16, wherein the configuration information is configured per DCI format (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0060] Modulation order and target code rate determination for PUSCH is discussed in the following. For the PUSCH assigned by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, TC-RNTI, or SP-CSI-RNTI, the transform precoding is enabled if transformPrecoder in PUSCH-Config is set to ‘enabled’, or if transformPrecoder in PUSCH-Config is not configured and msg3-transformPrecoding in rach-ConfigCommon is set to ‘enabled’; otherwise the transform precoding is disabled. [0061] For PUSCH assigned by a DCI format 0_0/0_1 with CRC scrambled by CS-RNTI, or the PUSCH with configured grant using CS-RNTI, the transform precoding is enabled if transformPrecoder in ConfiguredGrantConfig is set to ‘enabled’; otherwise the transform precoding is disabled.). As per claim 19, Zhang discloses a processor for wireless communication (Zhang Fig. 2, [0005,0175]), comprising: at least one controller coupled with at least one memory and configured to cause the processor (Zhang Fig. 2, [0005,0175]) to: receive first indication information indicating a first transform precoding state, wherein the first transform precoding state indicates whether a transform precoding is enabled or not (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.); and transmit a first physical uplink shared channel (PUSCH) transmission based on the first transform precoding state (Zhang Fig. 1 and [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 20, Zhang discloses the processor of claim 19, wherein the first indication information comprises downlink control information (DCI), and the at least one controller is configured to cause the processor to receive configuration information indicating whether a field for indicating the transform precoding state exists or not in the DCI (Zhang Fig. 1 and [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding.). As per claim 21, Zhang discloses the processor of claim 20, wherein the configuration information is configured per DCI format (Zhang [0051] In the context of the UE procedure for applying transform precoding on PUSCH, for Msg3 PUSCH transmission, the UE may consider the transform precoding either ‘enabled’ or ‘disabled’ according to the higher layer configured parameter msg3-transformPrecoding. [0052] For other PUSCH transmission, e.g. scheduled with a DCI/scheduling grant: [0053] If the DCI with the scheduling grant was received with DCI format 0_0, the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0054] If the DCI with the scheduling grant was not received with DCI format 0_0 [0055] If the UE is configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0056] If the UE is not configured with the higher layer parameter [transform-precoding-schedule], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0057] For PUSCH transmission without grant, e.g. based on a semi-static resource allocation: [0058] If the UE is configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to this parameter. [0059] If the UE is not configured with the higher layer parameter [transform-precoding-TWG], the UE may, for this PUSCH transmission, consider the transform precoding either enabled or disabled according to the higher layer configured parameter msg3-transformPrecoding. [0060] Modulation order and target code rate determination for PUSCH is discussed in the following. For the PUSCH assigned by a DCI format 0_0/0_1 with CRC scrambled by C-RNTI, TC-RNTI, or SP-CSI-RNTI, the transform precoding is enabled if transformPrecoder in PUSCH-Config is set to ‘enabled’, or if transformPrecoder in PUSCH-Config is not configured and msg3-transformPrecoding in rach-ConfigCommon is set to ‘enabled’; otherwise the transform precoding is disabled. [0061] For PUSCH assigned by a DCI format 0_0/0_1 with CRC scrambled by CS-RNTI, or the PUSCH with configured grant using CS-RNTI, the transform precoding is enabled if transformPrecoder in ConfiguredGrantConfig is set to ‘enabled’; otherwise the transform precoding is disabled.). Allowable Subject Matter Claims 4, 6, 10-14, 18, and 22 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. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to FAIYAZKHAN GHAFOERKHAN whose telephone number is (571)270-7161. The examiner can normally be reached Flex. 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, Ayaz R Sheikh can be reached at (571) 272-3795. 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. FAIYAZKHAN GHAFOERKHAN Primary Examiner Art Unit 2476 /FAIYAZKHAN GHAFOERKHAN/Primary Examiner, Art Unit 2476
Read full office action

Prosecution Timeline

Sep 10, 2024
Application Filed
Jun 30, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12684445
Methodology of Wi-Fi Access Point Selection for IMS Call over Wi-Fi
2y 5m to grant Granted Jul 14, 2026
Patent 12677213
TRACKING AREA SELECTION METHOD, DEVICE, AND SYSTEM
2y 5m to grant Granted Jul 07, 2026
Patent 12665723
SOUNDING REFERENCE SIGNAL MULTIPLEXING FOR NON-TERRESTRIAL NETWORKS
2y 6m to grant Granted Jun 23, 2026
Patent 12660001
METHOD FOR DATA TRANSMISSION AND TERMINAL DEVICE
3y 1m to grant Granted Jun 16, 2026
Patent 12652123
METHOD FOR TRANSMITTING OR RECEIVING DATA IN WIRELESS COMMUNICATION SYSTEM AND APPARATUS THEREFOR
2y 5m to grant Granted Jun 09, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

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

Prosecution Projections

1-2
Expected OA Rounds
87%
Grant Probability
96%
With Interview (+8.4%)
2y 8m (~10m remaining)
Median Time to Grant
Low
PTA Risk
Based on 572 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

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

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

Free tier: 3 strategy analyses per month