Prosecution Insights
Last updated: October 26, 2026
Application No. 18/702,554

TERMINAL, RADIO COMMUNICATION METHOD, AND BASE STATION

Final Rejection §102
Filed
Apr 18, 2024
Priority
Oct 21, 2021 — nonprovisional of PCTJP2021038952
Examiner
NGUYEN, LIEM HONG
Art Unit
2416
Tech Center
2400 — Computer Networks
Assignee
Nippon Telegraph and Telephone Corporation
OA Round
2 (Final)
73%
Grant Probability
Favorable
3-4
OA Rounds
4m
Est. Remaining
97%
With Interview

Examiner Intelligence

Grants 73% — above average
73%
Career Allowance Rate
182 granted / 248 resolved
+15.4% vs TC avg
Strong +23% interview lift
Without
With
+23.4%
Interview Lift
resolved cases with interview
Typical timeline
2y 10m
Avg Prosecution
18 currently pending
Career history
278
Total Applications
across all art units

Statute-Specific Performance

§101
1.5%
-38.5% vs TC avg
§103
56.3%
+16.3% vs TC avg
§102
20.8%
-19.2% vs TC avg
§112
19.5%
-20.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 248 resolved cases

Office Action

§102
DETAILED ACTION This communication is in response to applicant's response filed under 37 C.F.R. §1.111, dated July 10, 2026, in response to a non-final office action. Claims 7, 9, and 11-13 have been amended. Claims 8 and 10 have been cancelled. Claims 7, 9, and 11-13 are subject to examination and have been examined. Response to Arguments Applicant's arguments with respect to the claims have been considered but are moot in view of the new grounds of rejection. 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 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. Claims 7, 9, and 11-13 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Khoshnevisan et.al. (US Patent Application Publication, 20210235455, hereinafter, “Khoshnevisan ‘455”). Regarding claim 7, Khoshnevisan ‘455 teaches: A terminal comprising (Khoshnevisan ‘455: UE 104. Figs. 1, 3, 6): a receiver (Khoshnevisan ‘455: [0070] ... The UE 104 may include the SFN receiver component 140 ... Figs. 1, 3, 6) that receives downlink control information (DCI) indicating a transmission configuration indication (TCI) state applicable to multiple types of signals including a physical downlink shared channel (PDSCH) (Khoshnevisan ‘455: [0075] In an aspect, a DCI 622 indicating two or more TCI states may be transmitted [to UE 104] as an SFN transmission in which two or more TCI states apply to a PDCCH DMRS port and a transmission layer across all resource blocks and symbols of the DCI. In an aspect, the DCI 622 may be transmitted as an SFN transmission on the PDCCH candidate(s) configured for scheduling an SFN transmission. In an aspect, when the DCI 622 is transmitted as an SFN transmission, the DCI 622 may not explicitly indicate the two or more TCI states for the PDSCH. Instead, the two or more TCI states for the PDCCH may also apply to the PDSCH. That is, the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH may be the same as the two or more TCI states that apply to the PDCCH DMRS port and the transmission layer across all resource blocks and symbols of the DCI. Alternatively, the DCI 622 may indicate two or more TCI states that are different than the TCI states for the DCI and are applicable to the PDSCH. That is, the DCI 622 may include a TCI field that indicates the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH. Figs. 1, 3, 6) and receives a radio resource control (RRC) parameter indicating whether one TCI state of two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6); and a processor (Khoshnevisan ‘455: [0060] … RX processor 356 … controller/processor 359 ... Figs. 1, 3, 6) that, when the two TCI states are indicated by the DCI, determines, based on the RRC parameter, whether a first TCI state of the two TCI states indicated is applied to the PDSCH, a second TCI state of the two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630. The configuration controller 640 may transmit the RRC message 610 prior to transmitting the DCI 622. Accordingly, when the UE 104 receives the DCI 622, the UE 104 may interpret the two or more TCI states based on the RRC message 610. Figs. 1, 3, 6). Regarding claim 9, Khoshnevisan ‘455 discloses on the features with respect to claim 7 as outlined above Khoshnevisan ‘455 further teaches: wherein a configuration by the RRC parameter includes a configuration of a single frequency network (SFN) PDSCH scheme (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6). Regarding claim 11, Khoshnevisan ‘455 teaches: A radio communication method for a terminal, comprising (Khoshnevisan ‘455: UE 104. Figs. 1, 3, 6): receiving downlink control information (DCI) indicating a transmission configuration indication (TCI) state applicable to multiple types of signals including a physical downlink shared channel (PDSCH) (Khoshnevisan ‘455: [0075] In an aspect, a DCI 622 indicating two or more TCI states may be transmitted [to UE 104] as an SFN transmission in which two or more TCI states apply to a PDCCH DMRS port and a transmission layer across all resource blocks and symbols of the DCI. In an aspect, the DCI 622 may be transmitted as an SFN transmission on the PDCCH candidate(s) configured for scheduling an SFN transmission. In an aspect, when the DCI 622 is transmitted as an SFN transmission, the DCI 622 may not explicitly indicate the two or more TCI states for the PDSCH. Instead, the two or more TCI states for the PDCCH may also apply to the PDSCH. That is, the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH may be the same as the two or more TCI states that apply to the PDCCH DMRS port and the transmission layer across all resource blocks and symbols of the DCI. Alternatively, the DCI 622 may indicate two or more TCI states that are different than the TCI states for the DCI and are applicable to the PDSCH. That is, the DCI 622 may include a TCI field that indicates the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH. Figs. 1, 3, 6); receiving a radio resource control (RRC) parameter indicating whether one TCI state of two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6); and when the two TCI states are indicated by the DCI, determining, based on the RRC parameter, whether a first TCI state of the two TCI states indicated is applied to the PDSCH, a second TCI state of the two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630. The configuration controller 640 may transmit the RRC message 610 prior to transmitting the DCI 622. Accordingly, when the UE 104 receives the DCI 622, the UE 104 may interpret the two or more TCI states based on the RRC message 610. Figs. 1, 3, 6). Regarding claim 12, Khoshnevisan ‘455 teaches: A base station comprising (Khoshnevisan ‘455: base station 102. Figs. 1, 3, 6): a transmitter (Khoshnevisan ‘455: [0070] ... The base station 102 may include the SFN transmitter component 198 ... Figs. 1, 3, 6) that transmits downlink control information (DCI) indicating a transmission configuration indication (TCI) state applicable to multiple types of signals including a physical downlink shared channel (PDSCH) (Khoshnevisan ‘455: [0075] In an aspect, a DCI 622 indicating two or more TCI states may be transmitted [to UE 104] as an SFN transmission in which two or more TCI states apply to a PDCCH DMRS port and a transmission layer across all resource blocks and symbols of the DCI. In an aspect, the DCI 622 may be transmitted as an SFN transmission on the PDCCH candidate(s) configured for scheduling an SFN transmission. In an aspect, when the DCI 622 is transmitted as an SFN transmission, the DCI 622 may not explicitly indicate the two or more TCI states for the PDSCH. Instead, the two or more TCI states for the PDCCH may also apply to the PDSCH. That is, the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH may be the same as the two or more TCI states that apply to the PDCCH DMRS port and the transmission layer across all resource blocks and symbols of the DCI. Alternatively, the DCI 622 may indicate two or more TCI states that are different than the TCI states for the DCI and are applicable to the PDSCH. That is, the DCI 622 may include a TCI field that indicates the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH. Figs. 1, 3, 6) and transmits a radio resource control (RRC) parameter indicating whether one TCI state of two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6); and a processor that (Khoshnevisan ‘455: [0067] At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 ... Figs. 1, 3, 6), when indicating the two TCI states by the DCI, determines, using the RRC parameter, whether a first TCI state of the two TCI states indicated is applied to the PDSCH, a second TCI state of the two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6). Regarding claim 13, Khoshnevisan ‘455 teaches: A system comprising a terminal and a base station (Khoshnevisan ‘455: [0070] FIG. 6 is a diagram 600 illustrating example communications and components of a base station 102 and a UE 104. The UE 104 may include the SFN receiver component 140. The base station 102 may include the SFN transmitter component 198 ... Figs. 1, 3, 6), wherein the terminal comprises: a receiver (Khoshnevisan ‘455: [0070] ... The UE 104 may include the SFN receiver component 140... Figs. 1, 3, 6) that receives downlink control information (DCI) indicating a transmission configuration indication (TCI) state applicable to multiple types of signals including a physical downlink shared channel (PDSCH) (Khoshnevisan ‘455: [0075] In an aspect, a DCI 622 indicating two or more TCI states may be transmitted [to UE 104] as an SFN transmission in which two or more TCI states apply to a PDCCH DMRS port and a transmission layer across all resource blocks and symbols of the DCI. In an aspect, the DCI 622 may be transmitted as an SFN transmission on the PDCCH candidate(s) configured for scheduling an SFN transmission. In an aspect, when the DCI 622 is transmitted as an SFN transmission, the DCI 622 may not explicitly indicate the two or more TCI states for the PDSCH. Instead, the two or more TCI states for the PDCCH may also apply to the PDSCH. That is, the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH may be the same as the two or more TCI states that apply to the PDCCH DMRS port and the transmission layer across all resource blocks and symbols of the DCI. Alternatively, the DCI 622 may indicate two or more TCI states that are different than the TCI states for the DCI and are applicable to the PDSCH. That is, the DCI 622 may include a TCI field that indicates the two or more TCI states that apply to all DMRS ports and all transmission layers across all resource blocks and symbols for the PDSCH. Figs. 1, 3, 6) and receives a radio resource control (RRC) parameter indicating whether one TCI state of two TCI states indicated is applied to the PD SCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6); and a processor (Khoshnevisan ‘455: [0060] … RX processor 356 … controller/processor 359 ... Figs. 1, 3, 6) that, when the two TCI states are indicated by the DCI, determines, based on the RRC parameter, whether a first TCI state of the two TCI states indicated is applied to the PDSCH, a second TCI state of the two TCI states indicated is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630. The configuration controller 640 may transmit the RRC message 610 prior to transmitting the DCI 622. Accordingly, when the UE 104 receives the DCI 622, the UE 104 may interpret the two or more TCI states based on the RRC message 610. Figs. 1, 3, 6), and the base station comprises: a transmitter (Khoshnevisan ‘455: [0070] ... The base station 102 may include the SFN transmitter component 198 ... Figs. 1, 3, 6) that transmits the DCI and the RRC parameter (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6); and a processor that (Khoshnevisan ‘455: [0067] At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 ... Figs. 1, 3, 6), when indicating the two TCI states, determines, using the RRC parameter, whether the first TCI state is applied to the PDSCH, the second TCI state is applied to the PDSCH or the two TCI states indicated are applied to the PDSCH (Khoshnevisan ‘455: [0071] ... For example, the configuration controller 640 may transmit an RRC message 610 that indicates that two or more TCI states indicated by a DCI are for an SFN transmission. That is, the RRC message 610 may indicate that two or more TCI states (e.g., TCI states 624, 626) indicated by the DCI 622 apply to all DMRS ports or all transmission layers across all resource blocks and symbols of a PDSCH 630 ... Figs. 1, 3, 6). Conclusion Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to LIEM H NGUYEN whose telephone number is (408) 918-7636. The examiner can normally be reached on Monday-Friday, 8:00AM-4:30PM PT. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Noel Beharry can be reached on (571) 270-5630. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /LIEM H. NGUYEN/Primary Examiner, Art Unit 2416
Read full office action

Prosecution Timeline

Apr 18, 2024
Application Filed
Apr 10, 2026
Non-Final Rejection mailed — §102
Jul 10, 2026
Response Filed
Sep 28, 2026
Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12772095
ADAPTIVE PERFORMANCE MONITORING
2y 2m to grant Granted Oct 20, 2026
Patent 12750722
TRANSMISSION RELIABILITY TRANSMISSION FOR WIRELESS TIME SENSITIVE NETWORKS
4y 3m to grant Granted Sep 29, 2026
Patent 12750689
DYNAMIC EXTENSION OF A COMMUNICATIONS NETWORK
3y 8m to grant Granted Sep 29, 2026
Patent 12745232
SENSING DESIGN FOR USER EQUIPMENT (UE)
3y 2m to grant Granted Sep 22, 2026
Patent 12727041
CROSS-LINK INTERFERENCE (CLI) MEASUREMENT BASED SIDELINK ESTABLISHMENT
3y 8m to grant Granted Sep 01, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

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

Prosecution Projections

3-4
Expected OA Rounds
73%
Grant Probability
97%
With Interview (+23.4%)
2y 10m (~4m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 248 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