Prosecution Insights
Last updated: May 29, 2026
Application No. 18/133,092

DATA RECEPTION METHOD, DATA TRANSMISSION METHOD AND APPARATUSES THEREOF

Final Rejection §103§112
Filed
Apr 11, 2023
Priority
Oct 14, 2020 — continuation of PCTCN2020120904
Examiner
VOGEL, JAY L.
Art Unit
2478
Tech Center
2400 — Computer Networks
Assignee
Fujitsu Limited
OA Round
2 (Final)
80%
Grant Probability
Favorable
3-4
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 80% — above average
80%
Career Allowance Rate
355 granted / 446 resolved
+21.6% vs TC avg
Strong +24% interview lift
Without
With
+24.5%
Interview Lift
resolved cases with interview
Typical timeline
2y 6m
Avg Prosecution
27 currently pending
Career history
487
Total Applications
across all art units

Statute-Specific Performance

§101
0.3%
-39.7% vs TC avg
§103
95.9%
+55.9% vs TC avg
§102
1.8%
-38.2% vs TC avg
§112
0.7%
-39.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 446 resolved cases

Office Action

§103 §112
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 . Response to Arguments Rejections under 35 USC 112(b): Applicant canceled claim 20 which was rejected under 35 USC 112(b) and thus these rejections are withdrawn. Rejections under 35 USC 102 Applicant’s Argument: Applicant argues in Argument 1 that Futaki teaches a second BWP including the CORESET but not one that “cover a control resource set of the reduced capability terminal equipment.” Examiner’s Response: Applicant's arguments filed have been fully considered but they are not persuasive. Examiner finds no distinction between a second BWP that “includes” CORESET as admitted by Applicant, and a second BWP that “coves” the control resource set. As cited below, the second BWP is configured for reduced capability devices. If this BWP includes the CORESET, then it effectively “covers” the CORESET under broadest reasonable interpretation. Applicant’s Argument: Applicant argues in Argument 2 in Argument 1 that Futaki fails to teach monitoring messages in the BWP after receiving RRC messages including RRCSetup. Examiner’s Response: Applicant’s arguments with respect to claim(s) 1 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument. Examiner notes that Futaki teaches RRC messages configure the second BWP as he very first step in Figure 2, step 201, “via an RRC message.” Examiner has cited a new reference, Kim US 20200244410 A1 (see below), to teach the RRC message can be RRC setup as the cited paragraph shows RRCSetup is used to configure the BWP followed by data transfer, see Figure 2F where RRCSetup is sent followed by data transfer. 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 nonobviousness. Claim(s) 11-14, 17-19 is/are rejected under 35 U.S.C. 103 as being unpatentable over Futaki et al. (“Futaki”) (US 20220287102 A1, effective filing date of foreign application JP 2020-022376 filed Feb. 13, 2020) in view of Kim et al. (“Kim”) (US 20200244410 A1). Regarding claim 11, Futaki teaches: An apparatus, applicable to a reduced capability terminal equipment [Figure 3, 301, ¶0061, second initial BWP configuration (fifth indication) in SIB1, ¶0049 includes cell-specific parameters to second initial BWP, ¶0051 includes “indicating the frequency-domain position and bandwidth of the second initial DL BWP” and reduced capability fields, wherein ¶0072 second configuration supports reduced capability], the apparatus comprising: a memory; and processor circuitry coupled to the memory and configured [Figure 3, UE 2] to: receive fourth indication information and fifth indication information transmitted by a network device [Figure 3, step 301, ¶0061 information in SIB1 includes first initial BWP configuration (fourth indication) and second initial BWP configuration (fifth indication)], the fourth indication information being used to indicate first related information of a first initial bandwidth part (BWP) [¶0061, SIB1 include first initial BWP configuration, ¶0048 includes parameters of first initial BWP], and the fifth indication information being used to indicate second related information of a second initial bandwidth part (BWP) [¶0061, SIB1 include second initial BWP configuration, ¶0049 includes parameters of second initial BWP], wherein the second initial bandwidth part (BWP) covers a control resource set of the reduced capability terminal equipment [¶0053 configure PDCCH with DCI to be transmitted within BWP thus covers a CORESET]; and receive a downlink channel and/or signal in the second initial bandwidth part indicated by the fifth indication information [¶0065, UE monitors PDCCH in second initial BWP to receive DCI for PDSCH and Msg2, thus based on fifth indication information with second initial BWP configuration, ¶0069 PDSCH on second initial bandwidth part] after receiving a Radio Resource Control (RRC) message [¶0056, RRC message for configuring the second BWP which happens in first step of Figure 2, thus messages received after configuration including PDCCH received after RRC message]. Futaki teaches RRC message but not the type of message. Kim teaches the RRC message including RRCSetup message, RRCResume message or RRCReestablishment message [¶0564 RRC setup message configuring BWP]. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to specify the RRC message is RRC setup. Futaki teaches RRC message for configuring BWP and it would have been a simple substitution of parts to replace the unspecified RRC message with the setup message of Kim without altering the intended outcome of the invention to configure BWP as in ¶0564 of Kim. Regarding claim 12, Futaki-Kim teaches: The apparatus according to claim 11, wherein the fourth indication information is contained in a system information block to indicate a location and bandwidth of the first initial bandwidth part (BWP) [Futaki Figure 3, 301, ¶0061, fourth indication in SIB1, first initial BWP configuration (fourth indication), ¶0048 includes cell-specific parameters to first initial BWP, ¶0050 includes “indicating the frequency-domain position and bandwidth of the first initial DL BWP” ]. Regarding claim 13, Futaki-Kim teaches: The apparatus according to claim 11, wherein the fifth indication information is contained in a system information block to indicate second related information of a second initial bandwidth part (BWP) of a reduced capability terminal equipment, the second related information comprising a location and/or a bandwidth [Futaki Figure 3, 301, ¶0061, second initial BWP configuration (fifth indication) in SIB1, ¶0049 includes cell-specific parameters to second initial BWP, ¶0051 includes “indicating the frequency-domain position and bandwidth of the second initial DL BWP” and reduced capability fields, wherein ¶0072 second configuration supports reduced capability]. Regarding claim 14, Futaki-Kim teaches: The apparatus according to claim 11, wherein the fifth indication information is contained in a radio resource control related message [Futaki ¶0056, “In step 202, the gNB 1 broadcasts the second initial BWP configuration via the system information (e.g., SIB1), or transmits the second initial BWP configuration via UE dedicated signaling (e.g., via an RRC message).” Wherein second initial BWP configuration is fifth indication as above]. Regarding claim 17, Futaki teaches: An apparatus, applicable to a network device, the apparatus comprising: a memory; and a processor circuitry coupled to the memory and configured to [Figure 3, gNB, ¶0160-162]: transmit fourth indication information and fifth indication information to a reduced capability terminal equipment [Figure 3, step 301, ¶0061 gNB transmits information in SIB1 includes first initial BWP configuration (fourth indication) and second initial BWP configuration (fifth indication), wherein ¶0072 second configuration supports reduced capability], the fourth indication information being used to indicate first related information of a first initial bandwidth part (BWP) [¶0061, SIB1 include first initial BWP configuration, ¶0048 includes parameters of first initial BWP], and the fifth indication information being used to indicate second related information of a second initial bandwidth part (BWP) [¶0061, SIB1 include second initial BWP configuration, ¶0049 includes parameters of second initial BWP], wherein the second initial bandwidth part (BWP) covers a control resource set of the reduced capability terminal equipment [¶0053 configure PDCCH with DCI to be transmitted within BWP thus covers a CORESET]; and transmit a downlink channel and/or signal in the second initial bandwidth part indicated by the fifth indication information [¶0065, UE monitors PDCCH in second initial BWP to receive DCI for PDSCH and Msg2 (sent by gNB), thus based on fifth indication information with second initial BWP configuration], after transmitting a Radio Resource Control (RRC) message [¶0056, RRC message for configuring the second BWP, thus messages received after configuration including PDCCH sent i.e. after RRC message]. Futaki teaches RRC message but not the type of message. Kim teaches the RRC message including RRCSetup message, RRCResume message or RRCReestablishment message [¶0564 RRC setup message]. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to specify the RRC message is RRC setup. Futaki teaches RRC message for configuring BWP and it would have been a simple substitution of parts to replace the unspecified RRC message with the setup message of Kim without altering the intended outcome of the invention to configure BWP as in ¶0564 of Kim. Regarding claim 18, Futaki-Kim teaches: The apparatus according to claim 17, wherein the fourth indication information is contained in a system information block to indicate a location and bandwidth of the first initial bandwidth part (BWP) [Futaki Figure 3, 301, ¶0061, fourth indication in SIB1, first initial BWP configuration (fourth indication), ¶0048 includes cell-specific parameters to first initial BWP, ¶0050 includes “indicating the frequency-domain position and bandwidth of the first initial DL BWP” ]. Regarding claim 19, Futaki-Kim teaches: The apparatus according to claim 17, wherein the fifth indication information is contained in a system information block to indicate second related information of a second initial bandwidth part (BWP) of a reduced capability terminal equipment, the second related information comprising a location and/or a bandwidth [Futaki Figure 3, 301, ¶0061, fifth indication in SIB1, second initial BWP configuration (fifth indication), ¶0049 includes cell-specific parameters to second initial BWP, ¶0051 includes “indicating the frequency-domain position and bandwidth of the second initial DL BWP” and Conclusion Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to JAY L. VOGEL whose telephone number is (303)297-4322. The examiner can normally be reached on Monday-Friday 8AM-4:30 PM MT. 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, Joseph Avellino can be reached on 571-272-3905. 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 https://ppair-my.uspto.gov/pair/PrivatePair. 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. /JAY L VOGEL/Primary Examiner, Art Unit 2478
Read full office action

Prosecution Timeline

Apr 11, 2023
Application Filed
Nov 21, 2025
Non-Final Rejection mailed — §103, §112
Feb 12, 2026
Response Filed
Apr 21, 2026
Final Rejection mailed — §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12641601
TERMINAL, COMMUNICATION METHOD, AND SYSTEM
2y 1m to grant Granted May 26, 2026
Patent 12634769
SYSTEMS AND METHODS FOR TIME DISTRIBUTED PRB SCHEDULING PER NETWORK SLICE
3y 3m to grant Granted May 19, 2026
Patent 12634774
TIME-SENSITIVE NETWORK (TSN) DISTRIBUTION INFORMATION DURING HANDOVER
2y 10m to grant Granted May 19, 2026
Patent 12628171
METHOD AND DEVICE FOR TRANSMITTING MAC PDU
4y 2m to grant Granted May 12, 2026
Patent 12627433
ARTIFICIAL INTELLIGENCE MODEL DELIVERY VIA RADIO CONTROL PLANE
3y 1m to grant Granted May 12, 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
80%
Grant Probability
99%
With Interview (+24.5%)
2y 6m (~0m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 446 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